#3DS on a P5-100 error
6 messages in this thread
I am trying to install 3D Studio on my new Gateway2000 P5-100 XL and receive
the following error while running the VIBCFG:
Abnormal program termination: Ilegal instruction
CS:EIP = 000Fh:0017789Ch
I am in desperate need of getting this up and running tonight, can anyone help
me?
Thanks in advance.
Denise
Hi Denise,
<< I am in desperate need of getting this up and running tonight, can anyone
help me? >>
What's the behavior when you simplify your config.sys to File=#value and
Buffers=#value and simplify your autoexec.bat to a PATH statement and a
load_your_mouse statement?
Also, please post your video card manufacturer and model.
jonas[adesk]
The config.sys is set at File=64 and buffers=24 and that's all that I currently
have there. The autoexec.bat file contains a path stmt and the mouse stmt.
My video card is an ATI Mach64
The same error occurs… Abnormal program termination: Illegal instruction
CS:EIP = 000Fh:00177789Ch.
What else can I try? Thanks for responding so quickly.
d 🙂
Hi Denise,
<< .. what else…>>
The usual symptom of the ATI Mach64 is slow bootup and not a crash. Note the
following.
File Info for ANTIVE.ZIP
Section: HWare/OpSys/Video Contributor: 70673,1605 Size: 2689
Submitted: 9/19/94 Type: Binary Accesses: 177
Title: The ATI Mach64 Antivesa driver.
Keys: GUS ATI VESA ETERNITY BUGSGALORE DONTBUGME
This is a simple minded TSR I wrote to work around a very anoying delay when
booting 3D Studio while using the ATI Mach64 (PCI). It simply disables VESA all
together (VESA no longer exists after you load it). Source is included and read
it and docs before using.
Use at your own risk.
………………………..
I'm about to crash for the night and I have not used that card. Maybe one of
the forum regulars who have this card can give you any card specific
suggestions. (sorry.. )
jonas[adesk]
thanks for trying, talk to you later
d
Hi Denise,
Here's a more detailed outline..
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.