CompuServe Thread

Jorge – Some of the Autodesk technical assistants check into the forum on their own time over the weekend and many members psot replies also. But it may be Monday before you get a formal answer to your question. Just wanted you to know that the request for help is on the forum to be answered. Anne

Jorge, Three possibilities I can see, 1) you've got a corrupted project file 2) you have a memory problem / conflict, 3) your 3DS.EXE file is corrupted. Try correcting the memory problem first but x= whatever segment might be causing the problem, display card, scsi controller etc. to solve 3) reload 3ds.. To solve 1) your guess is as good as mine… John

Jorge, Abnormal program terminations are usually the result of a memory conflict. I have included instructions to help diagnose memory conflicts at the bottom of this message. If you clean boot following the instructions below and it doesn't solve the problem, then it is possible that the problem lies in the hardware. Run scandisk or something to check for bad sectors and lost clusters on your hard drive. Perform a virus check. Reinstall 3D Studio from the master diskettes, without deleting the first copy (this guarantees they are on different locations fo the hard disk. -brian 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.