CompuServe Thread

#3D Studio Configuration

2 messages in this thread
#183286From: Tony HasiukAug 2, 1995 7:27 PM
I am having difficulty getting 3DS working 'properly", so I'm trying to adjust the configuration. It would not load at all until I removed the NOEMS command in the EMM386 command in CONFIG.SYS. Once I got it to load, I then had problems with the tablet (Kurta 1218). I had to change the AUTOEXEC file to use the tablet in the Autodesk Icon startup for Autocad for DOS and Windows. This helped run DOS programs, but it would nor work for 3DS. I could operate 3DS, but it took a long time to load everything. With all of these changes, the software we primarily I to digitize maps wouldn't operate properly. Is there something I can do in a batch file to get things working? Any help would be appreciated!!
#183406From: Brian Rudolph [Adesk]Aug 3, 1995 11:09 AM
Tony, It sounds like you have a few conflicts on your system. I have included a paper to help you diagnose those problems. -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.