The mentioned behavior is actually an avast! problem with the boot-time scanner, occuring under Windows 2000 or NT4. It will be fixed soon - sorry for the troubles.
Correction: I'm referring to brins post, i.e. to the c0000139 bluescreen error.
Will you be providing a solution for those of us who are locked out of our systems?
My system: fully patched W2K SP4
- avast! set to notify of updates but it didn't notify of the current
program update (turns out that notifications are staggered to balance server load).
- used Updating | Program Update to download/install the update.
- began getting notices that my definitions were out of date. Checking for
updates said I was up to date.
- downloaded the installer for the new version.
- uninstalled avast! (reboot)
- installed new version.
- upon reboot, I now get this message:
"STOP: c0000139 {Entry Point Not Found}
The procedure entry point _aulldvrm could not be located in the dynamic link library ntdll.dll ."
--
js