M
Mike Matheny
I discovered this after receiving many fake MS emails supposedly containing
a "patch". My antivirus had been catching these and deleting them, but then
I started getting some that got through. I thought this was a new variant,
and to test it I saved the file to the desktop. I then right clicked on the
file to scan it with NAV - the cursor changed to the hourglass and NEVER
quit. After some more looking, I realized the .exe file was only 76 bytes
long, and after viewing it with a DOS program, saw that it was completely
empty. To test my theory about XP locking up in the above manner, I created
a new, empty text file on my desktop, and renamed it to test.exe. Then I
right clicked on it - well, after about 10 minutes of absolutely NO response
from the OS I pressed the reset button. I have tried this on 2 different
PC's so far with the same result. This is extremely bad error handling. Can
or does anyone want to confirm this?
Thanx,
a "patch". My antivirus had been catching these and deleting them, but then
I started getting some that got through. I thought this was a new variant,
and to test it I saved the file to the desktop. I then right clicked on the
file to scan it with NAV - the cursor changed to the hourglass and NEVER
quit. After some more looking, I realized the .exe file was only 76 bytes
long, and after viewing it with a DOS program, saw that it was completely
empty. To test my theory about XP locking up in the above manner, I created
a new, empty text file on my desktop, and renamed it to test.exe. Then I
right clicked on it - well, after about 10 minutes of absolutely NO response
from the OS I pressed the reset button. I have tried this on 2 different
PC's so far with the same result. This is extremely bad error handling. Can
or does anyone want to confirm this?
Thanx,