Memory protection fault
2 messages in this thread
Dear "Sysop",
A friend of mine (he doesn't have an account in CompuServe !!!)
has juste changed his PC and he seems to have some problem
with configurate 3D Studio V.4…
When he want to launch 3D Studio, an error occurs each time:
"Abnormal program termination : Memory protection fault.
CS:EIP=000Fh:001A0A0Ah"
He tries to use "-lfu -vscan 4000" settings of cfig386, but
the error occrus again. He and me are not very good at this
kind of memoryt problems. Can someone help me !?
Here is his configuration:
486 DX2 50MHZ, 16 MB RAM, a MAXTOR SCSI hard drive, a BusLogic SCSI (VLB) card
and a Cirrus Logic screen card (he has the drivers for it).
Perhaps his problem come from a bad configuration of EMM386, or
Pharlap options, or because he is using Stacker v.4 ?
Regards,
Paul.
Abnormal program terminations are almost always the result of a memory
conflict. Here is some information to help you diagnose the problem:
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is rebooted
without terminate and stay resident (TSR) programs nor device drivers that are
not absolutely necessary for the operation of the operating system and
computer. The Autodesk program should also be configured for VGA display if
possible, to rule out display driver conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy for this
trouble-shooting exercise and place these simplified system files on the
diskette. Or, you may edit the existing CONFIG.SYS and AUTOEXEC.BAT files
currently on the hard disk (make back-up copies first). Make sure you have a
bootable DOS floppy on hand, just in case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track down memory
conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.