That's why so many people have killfiled him for the constant whining and
crossposting over the years. ;-)
Tom
"Aaron Bertrand [MVP]" <aa***@TRASHaspfaq.com> wrote in message
news:O3**************@TK2MSFTNGP12.phx.gbl...
| >> I don't know if it is a bug. I may be specific to one browser. It may
| not.
|
| How is posting to win2000.general supposed to help you resolve that?
|
| Look, George, you're an MVP, and you know the basic etiquette rules in
place
| in all of these groups. You, of all people, should know better than to
| cross-post this whining to all of these irrelevant groups. In fact, if
you
| try to reply to your initial post using Outlook Express, your enthusiasm
in
| including so many newsgroups comes to the forefront very quickly:
|
| ---------------------------
| Outlook Express
| ---------------------------
| The newsgroup 'microsoft.public.wind' could not be resolved
| ---------------------------
| OK
| ---------------------------
|
| Once again. If you think it's a bug, send product feedback!
|
| If you have an issue implementing sample code from the knowledge base, a
| FrontPage newsgroup isn't the place to announce it! That article was last
| reviewed in November of 2002. Did you consider, even for a second,
hitting
| the "Provide us with feedback on this article" link? Or posting to the
| private knowledgebase.discussion newsgroup?
|
| I'm going to suggest to the leads that we once again review the
appropriate
| venues for providing feedback / bitching about this product or that, or
some
| KB articles, or the MSDN web site.
|
| Telling a bunch of irrelevant newsgroups how to reproduce it isn't exactly
a
| productive way of getting the problem fixed! This also worked for a
while:
|
| <input type=crash>
|
| But I didn't see that cross-posted to just about every newsgroup under the
| sun.
|
| Never mind that Browscap is awful and should have been deprecated ages
ago.
|
|
