Re: Microsoft releases critical fix that breaks their own software!From: firstname.lastname@example.org
- Previous message: h1kari: "ToorCon 2002 Call For Papers"
- Maybe in reply to: Geoff Shively: "Microsoft releases critical fix that breaks their own software!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 13 Jun 2002 22:20:24 -0000 From: <email@example.com> To: firstname.lastname@example.org('binary' encoding is not supported, stored as-is) In-Reply-To: <054c01c212eb$7468b970$3701a8c0@stingray>
>Check the conditions pivx lists here:
>http://www.pivx.com/workaround_fail.html to make sure its being executed
>as we did.
>This has been reported by over 100 users, and duplicated by PivX lab
>monekys on Window2k 95 and 98.
Might I suggest that this is a misconfiguration by the folks at PivX? IE
6, and WMP 7.1, on a WinMe box has no problem with it. There is an option
to set a DEFAULT proxy. This would cause the behavior you described, as
would simply enabling the proxies, and setting a Gopher proxy (the
HTTP/FTP fields are automatically filled in with bogus addresses when
proxies are first enabled). It appears as though your find is your own
error, rather than any problem with the workaround. It is interesting,
though, MS appears to have simply ripped off the Online Solutions
workaround that's been floating around for a few weeks.