I tried Ad-Ware 6.0 and it found Alexa, possible browser hijacking entries (3 of them) and many
tracking cookies.
Tried HiJackThis and it found an highly suspicious IP address multiple entries in the hosts
file,deleted them,
I installed the IE June 2003 security Patch for IE SP1 and it still locks up the same way.
IE is practically unusable now on this current XP-SP1 installation and I can't get rid of what's
causing this it seems....
I'll have to reinstall everything from scratch I think... no?

On Thu, 24 Jul 2003 16:59:23 GMT, <(E-Mail Removed)> wrote:

> IE is practically unusable now on this current XP-SP1 installation and I
> can't get rid of what's
> causing this it seems.... I'll have to reinstall everything from scratch
> I think... no?

You could check your proxy in IE and TCP/IP settings...

It could be they are mucked about causing your machine to need to do an IP
timeout before it does anything - which could appear to be a lockup.. (Note
the lots of "could"'s )

You may like to consider a "Route Print" to make sure everything is
pointing in the right directions... Dont post the results here... its a
little too much information to give away for free!!

TBQH This is a shot in the dark, but is probably worth checking as I have
seen machines freeze while they try to find a route out to the big wide
world... Usually happens when people change ISP's and the proxy / cache
server is no longer accessible.

Also, what did you delete from the hosts file...?

I assume you left the "127.0.0.1 localhost" in there...? This is a virgin
hosts file from XP Pro in case...

------------------ file starts the line after here -----------------

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost

------------------ file ends the line before here -----------------

\/\/

http://support.microsoft.com/default...b;EN-US;281679

This seems to be the issue I was experiencing. So it wasn't a virus, although some web pages might
contain code exploiting this bug anyway.
It repeated itself after a full system reinstall.
Probably some program has installed some IE plugin which deregistered some Dlls or corrupted
registry keys.

Re-registering urlmon.dll as explaing on MS KB article seems to have solved the issue.

Also, one program I installed in my system had installed MS XML Parser and I suspect it was the
culprit. Installing latest MS XML 3.0 SP4 and MS XML 4.0 SP2 didn't solve the issue but didn't make
IE 6.0 SP1 + June2003 security patch (and DX 9.0b with security fixes) crash anymore when opening
new windows. The new windows were just not working and remained blank without loading anything,
while they were crashing everything before.

I hope IE 6.0 SP2 is going to sort this serious bug out, I can't believe that with XP SP1 and all
the automated fixing features it's still possible for an application to destroy IE functionality so
easily.


On Thu, 24 Jul 2003 22:42:44 +0100, Wrangler <(E-Mail Removed)> wrote:

>On Thu, 24 Jul 2003 16:59:23 GMT, <(E-Mail Removed)> wrote:
>
>> IE is practically unusable now on this current XP-SP1 installation and I
>> can't get rid of what's
>> causing this it seems.... I'll have to reinstall everything from scratch
>> I think... no?
>
>You could check your proxy in IE and TCP/IP settings...
>
>It could be they are mucked about causing your machine to need to do an IP
>timeout before it does anything - which could appear to be a lockup.. (Note
>the lots of "could"'s )
>
>You may like to consider a "Route Print" to make sure everything is
>pointing in the right directions... Dont post the results here... its a
>little too much information to give away for free!!
>
>TBQH This is a shot in the dark, but is probably worth checking as I have
>seen machines freeze while they try to find a route out to the big wide
>world... Usually happens when people change ISP's and the proxy / cache
>server is no longer accessible.
>
>Also, what did you delete from the hosts file...?
>
>I assume you left the "127.0.0.1 localhost" in there...? This is a virgin
>hosts file from XP Pro in case...
>
>------------------ file starts the line after here -----------------
>
># Copyright (c) 1993-1999 Microsoft Corp.
>#
># This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
>#
># This file contains the mappings of IP addresses to host names. Each
># entry should be kept on an individual line. The IP address should
># be placed in the first column followed by the corresponding host name.
># The IP address and the host name should be separated by at least one
># space.
>#
># Additionally, comments (such as these) may be inserted on individual
># lines or following the machine name denoted by a '#' symbol.
>#
># For example:
>#
># 102.54.94.97 rhino.acme.com # source server
># 38.25.63.10 x.acme.com # x client host
>
>127.0.0.1 localhost
>
>------------------ file ends the line before here -----------------
>
>\/\/

I have been suffering the same effects and I am not running XP, still on
W98, IE 6, no additional packs etc, and after a few hours of netting, I get
freeze-ups, including windows explorer, so I give the browser the flick and
stay on the news groups, wierd stuff, though I did stop the Alexa toolbar
with Spybot S & D 1.2 , may be a clue??? or may be on drugz!!!

Gus



--
**--------------------------------------------------------------------**

http://support.microsoft.com/default...b;EN-US;281679

Re-register urlmon.dll library as documented.
If it doesn't work re-register all other dll libraries.

Reregistering just urlmon.dll fixed the issue completely for me.
Upgrading XML Parser to 3.0 SP2 and 4.0 SP4 just solved the freezing but every new window remained
blank without loading links.


On 26 Jul 2003 11:28:03 GMT, Gus <Gus@Sick_of_Spam.au> wrote:

>I have been suffering the same effects and I am not running XP, still on
>W98, IE 6, no additional packs etc, and after a few hours of netting, I get
>freeze-ups, including windows explorer, so I give the browser the flick and
>stay on the news groups, wierd stuff, though I did stop the Alexa toolbar
>with Spybot S & D 1.2 , may be a clue??? or may be on drugz!!!
>
>Gus

Thanks I have saved the page until I get off line,
cheers
Gus




--
**--------------------------------------------------------------------**

(E-Mail Removed) wrote in news(E-Mail Removed):

> http://support.microsoft.com/default...b;EN-US;281679
>
> Re-register urlmon.dll library as documented.
> If it doesn't work re-register all other dll libraries.
>
> Reregistering just urlmon.dll fixed the issue completely for me.
> Upgrading XML Parser to 3.0 SP2 and 4.0 SP4 just solved the freezing but
every new window remained
> blank without loading links.
>
>
> On 26 Jul 2003 11:28:03 GMT, Gus <Gus@Sick_of_Spam.au> wrote:
>
>>I have been suffering the same effects and I am not running XP, still on
>>W98, IE 6, no additional packs etc, and after a few hours of netting, I get
>>freeze-ups, including windows explorer, so I give the browser the flick and
>>stay on the news groups, wierd stuff, though I did stop the Alexa toolbar
>>with Spybot S & D 1.2 , may be a clue??? or may be on drugz!!!
>>
>>Gus
>
>

All systems are go again, I wonder what caused the problem.
Thanks,
Gus




--
**--------------------------------------------------------------------**