crashing Microsoft Browsers thier way

[George Hester]

Easily. Go to this page:

http://support.microsoft.com/default.aspx?scid=kb;en-us;224979

And then use their second example the clientcap.htm and clientcap.asp section. Then fire up clientcap.asp and watch the Microsoft Internet Explorer browsers crash.

 

[Aaron Bertrand - MVP]

win2000.general? A little aggressive with the crosspost, no?



Easily. Go to this page:

http://support.microsoft.com/default.aspx?scid=kb;en-us;224979

And then use their second example the clientcap.htm and clientcap.asp
section. Then fire up clientcap.asp and watch the Microsoft Internet
Explorer browsers crash.

 

[George Hester]

Stay tuned

 

[Tom Pepper Willett]

Same with frontpage extensions.

--
-----
Tom Pepper Willett
Microsoft MVP - FrontPage
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
http://msdn.microsoft.com/office/understanding/frontpage/
----
| win2000.general? A little aggressive with the crosspost, no?
|
|
|
| | Easily. Go to this page:
|
| http://support.microsoft.com/default.aspx?scid=kb;en-us;224979
|
| And then use their second example the clientcap.htm and clientcap.asp
| section. Then fire up clientcap.asp and watch the Microsoft Internet
| Explorer browsers crash.
|
| --
| George Hester
| __________________________________
|
|

 

[Aaron Bertrand [MVP]]

Oh great, so there's more coming?

George, if you think you have found a bug in the browser, a more effective
thing to do than cross-post your amazing discovery to a bunch of irrelevant
newsgroups, is to provide product feedback to MIcrosoft. If you want it
fixed, that is, because they're going to fix it, not us. However, if you
just want to complain about it, let me know so I can put you on my filter.



Stay tuned

 

[George Hester]

I don't know if it is a bug. I may be specific to one browser. It may not. It may be specific to the browser in one operating system. It may not. If we called Microsoft to ask them to look into it they would likely ask what operating system is running and what version of Internet Explorer does this occur in. Since I have no idea if that is important to this issue I asked in many places and yes I messed up one went to FPSE group. I also messed up because the multitude of posts has caused anger on the part of some readers which has diverted attention from the issue.

When I reply to a post that has multitude postings I usually address the post in this way. First I give it the ole college try. And then I might comment that the cross-posting was unnecessary. The reason for that is because I have already determined to give the post some attention and then only notice that it was posted to a multitude of newsgroups. I usually don't even notice that until I post as my answer has already been determined by the time I am ready to post.

 

[Aaron Bertrand [MVP]]

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.

 

[Colon Terminus]

Doesn't crash here ... IE 5.01 SP3.

Easily. Go to this page:

http://support.microsoft.com/default.aspx?scid=kb;en-us;224979

And then use their second example the clientcap.htm and clientcap.asp
section. Then fire up clientcap.asp and watch the Microsoft Internet
Explorer browsers crash.

 

[Tom Pepper Willett]

That's why so many people have killfiled him for the constant whining and
crossposting over the years. ;-)

Tom
| >> 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.
|
|

 

[Blair Bonnett]

Something I found (can't remember where now, it was ages ago) is to put
<input type crash> into a form (note the lack of an = sign). It just
happens to crash IE browsers - well, at least 5.01 and 5.5, thats what I've
tested it on.

Blair

 

[George Hester]

Thanks Colin.

 

[George Hester]

Hmm interesting. Years ago there used to be posts (not here) that when you clicked on the link it would crash Windows 2000. In fact any Microsoft Windows product. At that time I didn't know enough to pull the page up in a FTP client so never did figure out how they did it.

 

[George Hester]

I thought browscap's issue was performance. I didn't realize it was also incompatibility. Who knows though? One person had tried the example and told me the version of IE he was using. I assume he was saying Windows 2000 SP3 which with IE 5.01 that means SP4 for that browser. Also that article was specific to IE 5.01. Furthermore do you know where that article came from? It came from WROX. So it's not all that weird. Microsoft fixed it up some but it looks to still be dangerous in Windows 2000 SP3 IE 5.5 SP2. In fact I think the browser will crash even if there is no call to browscap.dll. It's the format of the <!-- ... type="cookie" ... ->

 

[Aaron Bertrand [MVP]]

That's all nice and everything, but you're still avoiding the issue and
you're still cross-posting to irrelevant groups. Use the feedback link on
the KB article!




I thought browscap's issue was performance. I didn't realize it was also
incompatibility. Who knows though? One person had tried the example and
told me the version of IE he was using. I assume he was saying Windows 2000
SP3 which with IE 5.01 that means SP4 for that browser. Also that article
was specific to IE 5.01. Furthermore do you know where that article came
from? It came from WROX. So it's not all that weird. Microsoft fixed it
up some but it looks to still be dangerous in Windows 2000 SP3 IE 5.5 SP2.
In fact I think the browser will crash even if there is no call to
browscap.dll. It's the format of the <!-- ... type="cookie" ... ->

 

[David Baxter]

As several other people have noted, this has little or nothing to do
with FrontPage extensions - next time you reply, do you think you could
just delete irrelevant newsgroups from the "To" line?

Hmm interesting. Years ago there used to be posts (not here) that when
you clicked on the link it would crash Windows 2000. In fact any
Microsoft Windows product. At that time I didn't know enough to pull
the page up in a FTP client so never did figure out how they did it.

 

[Colon Terminus]

Here's the info from the "Help | About" dialog box:

Version: 5.00.3502.1000
Cipher Strength: 128-bit (Update Information) <--- Underlined
Product ID:5007-416-2878127-04893
Update
Versions:;SP3;Q328389;Q323759;Q328970;Q810847


Thanks Colin.

 

[George Hester]

Thanks Colon (right this time). I have almost your exact same set up in another Windows 2000 installation. I am going to try in that and see if I can replicate your success with the article.