m
Hello, June.
I think a little more information is needed. Since you've stripped your
AUTOEXEC and CONFIG, you've completed the first step in solving this.
I'm wondering, does this error occur with AAPro in Vanilla <320×200> mode?
Or are you loading a VESA driver via some other batch file to execute
AAPro?
I have seen some VESA drivers produce a memory protection fault.
Other considerations in your hardware set-up may be active caches or
shadowbios that are initialized when you boot the system. These would be
in your C/MOS setting for the hardware, not through AUTOEXEC or CONFIG, and
sometimes machines have these utilities active when you pull the computer
out of the box. Checking and , if active, disabling them may help.
Get me some more information, and we'll go from there.