M
max
Hi Wes,
I sent this as an email, but in case you don't get this, I'm also posting it
here.
Thanks for your help. I know that the "winsock2.2.exe" was removed from my
fiends computer because Norton said it was a worm. The problem he has with
this is that his computer calls for it on every startup. The worm was
suposed to be removed by Norton. Do you have any thoughts on how to stop
the computer from calling for it at startup?
Also, I have a problem with this being a worm because I have found it in
the registry of both my laptop and desktop computers. And my desktop just
had XP installed two weeks ago, I'm sure it had Service Pack 1 and 2 and all
recent updates. Plus I have run Norton, Stinger, Spybot, and Adaware twice
in the last two weeks, so how could it have gotten on the computer so
quickly and not be caught? Are you sure that the winsock2.2.exe is
associated with the worm directly or does the worm just attach to it?
Any light you can shed on the above would be greatly appreciated.
Max
I sent this as an email, but in case you don't get this, I'm also posting it
here.
Thanks for your help. I know that the "winsock2.2.exe" was removed from my
fiends computer because Norton said it was a worm. The problem he has with
this is that his computer calls for it on every startup. The worm was
suposed to be removed by Norton. Do you have any thoughts on how to stop
the computer from calling for it at startup?
Also, I have a problem with this being a worm because I have found it in
the registry of both my laptop and desktop computers. And my desktop just
had XP installed two weeks ago, I'm sure it had Service Pack 1 and 2 and all
recent updates. Plus I have run Norton, Stinger, Spybot, and Adaware twice
in the last two weeks, so how could it have gotten on the computer so
quickly and not be caught? Are you sure that the winsock2.2.exe is
associated with the worm directly or does the worm just attach to it?
Any light you can shed on the above would be greatly appreciated.
Max