CompuServe Thread

3DS4 LOCKUP

3 messages in this thread
#164500From: Paul BoydApr 13, 1995 1:32 AM
I am running into a problem, for some reasone when I pull a *.tif file into the material editor and run a render in the view window – it gets maybe half way thru and locks up???? I ran a Virus scan and I'm clean, any help??? Thanks Paul Boyd
#164587From: Brian Rudolph [Adesk]Apr 13, 1995 12:03 PM
Paul, Lock ups are often the sysmptom of a memory conflict. Does this hapen in a stripped environment? I have included some instructions to help diagnose your problem. -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.
#164622From: Paul BoydApr 13, 1995 3:39 PM
I am currently running under a stripped boot to maximize memory, This just started happening last night, I have never had this happen before. I know I've done these procedures before it just started hanging up, – it seemed to hang up after doing a test render using the flame ipas from within Video Post. I'll try this out without the test render to see if it fixes the problem, I will let you know if I can re-create the problem – Thanks Paul Boyd