#Soundblaster crashes
6 messages in this thread
Has anyone tried configuring 3DS with a Targa+ and a Soundblaster card? I
know, I know, I really don't want to get into the relative merits of a
Soundblaster. There really are probably much better cards. When trying to
install the new Targa drivers for 3DS and Animator Pro I noticed in the
documentation the new protected mode ADI driver was supposed to fix the
problem of 3DS crashing when attempting to render to the rdpadi driver
while a Soundblaster is installed. On page 3 of the Readme.doc, it says
"If you have any problems using this driver, please contact Autodesk." Is
there a phone number to call, or does this fall into the $3000 extra for
tech support area?
To be more specific, yes I did move my Targa Board to I/O 230 and left the
Soundblaster at 220. Can this be accomplished or does 3DS just not work
with a Soundblaster Card? I had no problem running TIPS!
Roger D.
Roger, I've just got one word of advice for you…
QEMM386
You need it. When you get it, try using the NVR (no vidram) command to
move your displays out of low RAM.
– G
Gary,
I've been a longtime user of QEMM, from the first day I opened the package
and tried to install 3DS on a computer that had Windows. Before your
suggestion I had never tried NVR. No luck though, 3DS still locks up
tighter than a drum. The thing I can't understand, if TIPS can operate
with both boards installed, why 3DS won't. But I guess that's too logical
for the computer industry <g>.
Roger D.
I'm sorry that NVR didn't work for you. The problem sounds like it's a
conflict between Pharlap at D000-E000 and the Soundblaster.
Hardware conflicts on the PC are one of the worst nightmares I've ever been
through. I've got a lot of sympathy for you.
– G
Roger,
You seem to be having more than your fair share of hardware/software
conflicts! When I tried to install Soundblaster in my 486/33 the
motherboard blew up! There is a QEMM386 command I used which seemed to
solve some of my conflicts: EXCLUDE=C000-DFFF
I think this prevents any software from using that memory area. Have you
noticed how many threads are software/hardware conflicts, lately? It's
almost reaching epidemic level and the frightening thing is, there's no
easy answer! I've personally spent many unproductive, frustrating days
trying to solve conflicts, usually whenever I install some new software or
hardware. Such is the life of a desktop video hack!
Martin,
Yeah, Martin, love those conflicts. I solved mine. I sold the board. The
part I loved though, is the part at the bottom of the readme.doc of the new
Truevision drivers that said that if they didn't work call Autodesk. BTW,
we did try that exclusion, but it didn't seem to work. Thanks.
Roger D.