Don Phillipson wrote:
> "Terry Pinnell" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>> Recently my PC (Quad Core Q9450 2.66 GHz, 4 GB, XP Pro SP2) has been
>> suddenly locking up. I often get a message
>> "The application or DLL
>> C:\WINDOWS\AppPatch\AcGenral.dll is not a valid Windows image. Please
>> check against your installation diskette."
>> BTW, the last sentence seems to date the message as written decades ago!
>>
>> Can anyone shed any light on this please? And what I should do about it?
>>
>> FWIW, I found another copy of AcGenral.dll and it was identical.
>>
>> Also, I usually get another message when trying to display the Task
>> Manager, so that I can re-boot:
>> "Taskmgr.exe - Application Error
>> The application failed to initiate properly (0xc000012d)"
>>
>> Not sure if this is a related or consequential issue, but it forces me to
>> power down or use the reset button.
>
> Problem #2 might be cured by installing SP3. My TASKMGR.EXE
> is 135,680 bytes, dated 4/14/2008.
>
> Problem #1 may be that ACGENRAL antedates WinXP by "decades."
> This is what WinXP "Compatibility" arrangements are for. Start / Help
> presents the basic information. These old apps can be configured
> to run as if under Win95 or Win98 (and perhaps Win3.1). One of
> these configurations may make the app run as you want.
>
> But it would be prudent first to instal SP3.
>
A critical detail missing from Terry's description, is whether at
the time of the Acgenral error, an attempt was being made to launch a
brand new executable.
If some executable was being corrupted when read off disk, and Windows
responded by believing that the application needed compatibility
support, perhaps at that point, it tries to load Acgenral from disk.
And if Acgenral suffered the same kind of header corruption, then the
error results. (Pretty strange, if it happened that way.)
If no new programs are being launched, at that point in time when
the error is being reported, that would be more suspicious.
There is an article here, with a list of files near the bottom, that
shows what files handle application compatibility. Whether they stay
loaded in RAM, or are loaded on demand, would be a good question.
http://support.microsoft.com/kb/319580
It's still very suspicious, and could either be some kind of
malware, or something like bad RAM or a bad disk or bad SATA cable.
Plenty of testing, remains to go.
Version 25.11 of Prime95 is available here, for both Windows
and Linux. If you boot a Linux LiveCD and run the Prime95 stress
test, and it passes, while running the Windows version is failing,
it could be more than a hardware problem. A clean Linux run, tells
you the hardware is fine. Prime95 is like running a memory test,
only with more stressful test conditions. It can only test memory
which the OS isn't currently using.
http://www.mersenne.org/freesoft/
And an offline virus scanner is available here. As long as a DHCP
capable networking solution is available when this CD boots, then it
can get up to date virus definitions to run a scan with. The
"drive letters" shown in the control panel of this application,
don't correspond to Windows drive letters. And then, you need to
use the Terminal application from the menu, navigate to the
individual disks, and sort out which partition is which in there.
Or, tick all the partitions as needing scanning, and head off to
bed while it completes. It takes about 2 hours to scan 40GB
of files on C:.
http://devbuilds.kaspersky-labs.com/.../RescueDisk10/
That tool is built on top of a Gentoo Linux distro.
On the jewel box my RescueDisk10 is in, I've written...
At boot
1) Press "e"
2) Wait for "configfile" line to appear. Don't change
anything. Press control-x to allow the boot process to continue.
3) Press "e" again.
4) The Linux boot command will be exposed.
Remove "quiet" from the end of the line.
Add "docache" to the end of the line.
Press control-x to continue the boot process, with the modified line.
5) The OS will now read the 200MB CDROM image into RAM.
The CD can then be unmounted from a Terminal window.
And only at that point, can the CD be popped out of the tray.
*Quickly* remove the CD, because the OS will close the tray
automatically in a matter of seconds, once the tray is open.
(I haven't pinched the CD yet, but it's bound to happen
one of these days.) The tray closing interval is variable.
The above procedure, is so the Kaspersky scanner can be run,
without leaving the CD spinning in the drive for hours on end.
"Docache" means the entire CD is stored in RAM.
The Kaspersky tool has the following side effects. It plays
with the pagefile (uses it for its own pagefile). This isn't
an issue. It's still a good idea to shutdown Windows completely,
before running a scan. The Kaspersky tool may also choose to store
the virus definitions on some partition on the computer as well,
which may help reduce the download time for virus definitions
at some future date. For some reason, it chose to store them on
my G: partition.
G:\Kaspersky Rescue Disk 10.0
5477 files, 51 folders, 129,077,914 bytes
HTH,
Paul