OK, so I wasn't very happy w/ Avast! 5 at first but w/ help here I now know how to do a memory scan. I'm NOT particularly happy that it claims Spybot's Teatimer is infected w/ JS:ScriptSH-inf(Trj) and everyone seems to just "assume" it/they are false positives... but on with the show:
per the title EVERY TIME avast 5 does a boot scan it first puts me to sleep then puts this Compaq C7700US (laptop) to sleep. And then when I use the chinzy mouse-pad to wake-up the machine, I get a flash message too fast to read saying something to the effect "boot ... was not successful" followed by black-screen which not even Ctl-Alt-Del affects.
The only thing that does anything at all is to hold-down the power button for 1 minute or so which forces the machine off. Then when I power-up again I get the standard "Windows Did Not Shut Down Safely" complaint, my screen resolution is reset to minimum (I use an external screen and wireless keyboard+mouse) and my icons are TOTAL mishmash (as always happens when screen resolution is reset to minimum).
I don't doubt that windoz (Vista home premium) is at fault but please fix avast to not trigger that terrible behavior.
thanks
Don H
endend
Update(s):
0) The problem persists: Avast5 complains of "JS:ScriptSH-inf [Trj]" in 3 different memory locations associated with Spybot's Teatimer.
1) Memory Scan is not a normal Avast 5 option, as I think I mentioned in my first post.
I wonder if people insisting they have no teatimer problem, are simply not
doing memory scans?
2) I find no way to "repair" my Avast 5 installation, as was suggested.
If I activate Ctrl Panel "Uninstall or Change", "repair" is not listed there. Requesting "Update" tells me I am "already completely up-to-date."
Nor can I find any selection or option in Avast itself to "repair"
3) I just realized apparently Avast 5 cannot be unloaded or disabled. This makes me VERY uncomfortable. "1984 Big Brother"
software now?
What if I get a garbled update? Or is Big Brother supposedly watching that too??
Or suppose another program damages it. -I could write software to do that. And virus-writers are 1000 times better than me.
4) If I unload the resident portion of Spybot, the memory scan is clean.
If I scan the Spybot program files folder, that too is clean.
This tells me Spybot and Avast 5 are not communicating well: That Avast 5 is treating what should be considered "data" as "Executable."
5) How do I revert to Avast 4.8 ?
I
DON'T LIKE the big-brother concept. Nor do I like a program that treats data in another AV pgm as executable code.
6) re: other posts: I also have found some of the "sxe417.tmp" files. None of the scanners seem to care though, so why should I?
7) (And just to be picky:) The new Avast "Voice" is liable to get me in big trouble if my girlfriend is talking to me on the phone when it announces itself.
No one has addressed it and I have not done a boot-scan recently because it is such a pita to rearrange my 100+ desktop icons after Windoz crashes.
I guess I'll just have to try it to see if avast 5 boot-scan has been fixed, or still trashes Windows as part of the boot-scan.
-