Abnormal termination
9 messages in this thread
Hi,
I have come across this problem with 3dsR3. If I try to do a boolean
operation, even if it is with two simple square blocks, I get the message;
Abnormal Program Termination: Stack Fault
CS:EIP = 000Fh:000B25F9h
then I'm back at the DOS prompt.
I even reinstalled 3DS thinking it might be a corrupted file, but it made no
difference. Otherwise 3DS runs fine.
Any ideas?
thanks,
Allie
It sounds like you either have something wrong with your computer or you've hit
a very bizarre case. If you'd like to zip up the source project file with
instructions on how to reproduce it and send it to Jonas, he could at least
confirm whether or not it's your hardware.
– G
Thanks Gary,
Unfortunately it happens even if you make two simple ovelapping squares and try
to subtract one from the other.
I booted with a stripped Config.sys and Autoexec.bat file, leaving only QEMM,
Targa+ driver and the mouse driver active, and the 3DS still terminated.
I have a Western Digital 540 meg HD using their Drive .BIN file to basically
patch the system to let me access the full 540 meg. This in turn does not let
QEMM use Steath to swap drivers in himem since the .BIN program intercepts all
hardware calls to the hard drive. Could this be a possible source of conflict?
My system is a 486DX-33, with 16meg RAM, with a Western Digital VLB
Ports-O-Call VGA-HD/FD-I/O combo card, Mitsumi CD-ROM, and a Targa+ 64.
Thanks,
Al
Sounds like hardware trouble to me. Maybe Jonas can give you some ideas re
where to start.
– G
Allie,
<< I booted with a stripped Config.sys and Autoexec.bat file, leaving only
QEMM, Targa+ driver and the mouse driver active, and the 3DS still terminated.
>>
Strip it down to files=# and buffers=# only in your config.sys. Path and mouse
statement only on autoexec.bat. Now try it on 3ds and note its behaviour. If
3DS works in this configuration, there is a conflict with your other programs
and drivers. When you add one line back into your config.sys, reboot and try
3ds. If it works, add another line back in until it fails. This is the
recommended troubleshooting procedure for identifying conflicts. It takes
patience but you will identify the culprit.
jonas[adesk]
OK, I'll Give it a try
Al
Hi Jonas,
Well, I did what you suggested and it still terminated (aaarrrgghhh!!!!) 🙁
I ran AMIDIAG 4.0 on my system using the complete battery of tests. It says
everything is OK.
The only time this happens is with the boolean operation, either in version 3.0
or 3.0a.
Got any other suggestions?
thanks,
Al
Allie,
<< Got any other suggestions? >>
You can put the project file on the Autodesk BBS 1-415-507-5921 with everything
ready for the boolean operation. I'll try it here to see if it's the operation
or your environment. E-mail me when you've placed the *.prj on the BBS.
jonas[adesk]
>> I have a Western Digital 540 meg HD using their Drive .BIN file to basically
patch the system to let me access the full 540 meg. <<
I think that this probably your problem here. If this is a IDE drive and your
machine has a modern day bios you can choose a user defined drive type to use
the full cap of your drive without patching your OS. Oh ya, you must also run
DOS 4 or greater to access more than 32 w/out patching the OS. If it is a SCSI
drive it should be automatic although you still must have a current version on
dos.
I've seen this to be the problem on more than once.
Good luck.