#3D studio locks up
6 messages in this thread
I am running the educational (hardware locked) version of 3D studio V.4,
recently upgraded from V. 3. Hardware: Comtrade Pentium 90, 32MB ram, Diamond
Stealth video card, Summagraphics 12×12 "FX" tablet, DPS PAR board & TBC IV
video capture board.
Problem: In 3D studio, at irregular intervals and for no apparent reason, the
system suddenly hangs up, and will not accept any input – forcing me to reboot
and lose any work that was not saved. This does not seem to have anything to do
with what I am doing in 3D Studio – if I simply go into the program and let it
sit for a few minutes, it will almost invariably hang.
This also was a problem with version 3, although it only affected input from
the digitizer, whereas now it affects the keyboard as well. It does not occur
in any other software – including a locked version of Autocad 13 (running in
Windows).
I would appreciate any suggestions as to how to correct this problem.
thanks
I know that someone will give you that nominal "virus attack" on your system
(especially fr. ADesk reps). That I don't think here in this case.
Perhaps your parallel port speed is set too high. Try setting it normal to see
it if locks up. Other than that, it's quite an unusual problem.
Try to get a totally new partition or any extra SCSI-2 hd and make a new boot
disk w/ only needed items. This will help better to track down the culprit.
Hi Caleb,
<< ..hangs.. >>
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.
I have narrowed the problem down to the EMM386 memory manager. With it rem-ed
out of the config.sys,
3DS does not lock up anymore. In the 3DS instalation guide, it gives a
suggestion for how to configure
the EMM386 so that it will work with 3DS – the line recomended is
"DEVICE=EMM386.EXE xxxx RAM ON".
xxxx is the amount of extended memory minus 1024 kb. The DOS 6.22 manual says
this can be a maximum of 32768.
This system has 48 MB of ram, so I cannot follow this exactly. With EMM386
configured with the maximum allowed
value of xxxx (32768), it still locked up.
The config.sys file reads:
DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:ON /V
(DEVICE=C:\DOS\EMM386.EXE 32768 RAM ON)
DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER
DOS=HIGH,UMB
STACKS=9,256
BUFFERS=15,0
FILES=40
LASTDRIVE=Z
FCBS=4,0
SHELL=C:\COMMAND.COM /E:1024 /P
DEVICEHIGH /L:1,4560 =C:\WINDOWS\IFSHLP.SYS
[a number of device drivers ]
[(CD, soundcard, scanner) ]
[loaded with the DEVICEHIGH command – ]
[memory locations set using "MEMMAKER" ]
Question – how to configure the EMM386 to work with 3DS – or is it ok to not
load it up at all?
We are also running Autocad 13 under Windows for Workgroups 3.11 – what are its
requirements
for memory management? (Is EMM386 necessary for Windows in Enhanced mode?)
How will we have to reconfigure the various drivers? – can the "DEVICEHIGH"
command to load drivers into
upper memory be used without the EMM386?
Thanks.
Caleb
I've had good luck with the line:
"device=c:\dos\emm386.exe 384 noems"
Also you might want to take out all of the "L:/" switches. Those have been a
source of problems for other programs as well as 3ds.
…Earl
Thanks, Earl.
Caleb