As I recall the person that had the problem awhile back I read that
the culprit was a file in the system directory that was mislabled.
So instead of it being an .exe it was a .dll or something like
that. The item has a fake file extension I guess. Good luck.
--
Stinson
I had an excellent tip from someone to look in Windows+system+sys32
dirs to see if I could spot a file with a creation date/time to
match the start of the problem - as I know almost for certain
exactly when it started - within 30 mins or so of 5pm on 30th May -
but I've just looked yet again to be sure and there's NOTHING.
Plenty that were new and created LATER than evening..those would
surely be what came from a variety of NEW progs I was then adding
from recommends, after running my own that were already
pre-logged...all others that day are around the 11pm slot , give or
take an hour or two...when I WAS using/adding new progs...but
NOTHING to pin down to that 5pm slot.
Pity the 'Search' on this Forums site is so poor - you just seem
unable to get anything that goes back as far as you ever seem to
want - and of course this Oly one moves like lightning .. anything
about a week old can be 15 or so pages back !!! so finding anything
a month or more ago is hopeless. Did a lot of Google searches in
other similar Forums on such trouble but again, no clue. They all
said CWShredder had cleared it , fine...it does NOTHING for me
except say I'm clean !!
--
EJN