#3ds conflicting w/ ASPI?
6 messages in this thread
A client of mine has a 486/50dx 48mb RAM, 2.1 gb of disk space on 2 SCSI
disks – a 500mb drive and a 1.6gb drive, a 500mb SCSI tape backup, a cd-rom
hooked to a Sound Blaster Pro card, an ATVista 4mb, Orchid F1280 svga card.
The SCSI controller is an Adaptec 154x series.
He has been experiencing repeated crashes while rendering in 3ds2. By a
process of elimination I was able to produce the following results:
1. by remarking out the CD-rom statements in the config and autoexec files
I was able to reduce the crash frequency from every time we rendered an
image to only 1 in 3 times.
2. by remarking out the aspi4dos.sys device statement and the aspidisk.sys
(or similar statement) I was able to cure the crashing completely. However,
now I don't get the benefit of using the cd-rom or the potential speed
improvement that may be achieved by using the aspi drivers – we have the
latest driver versions (2.1 or 2.2, I think).
My question is have you heard of any similar conflicts with aspi drivers
and do you know a fix? Any comments at all on this stable but less than
satisfactory situation?
Martin
Martin:
I believe that you have some sleuthing to do. There should be jumpers on
the SCSI controller that let you move the interrupt address of the
controller. QEMM's memory mapping capabilities will help you sort this out.
You need to find interrupt addresses that get along with the drivers and
graphics card that he is using. Also, if he is on a network, add that to
the pile.
C#
Craig,
Thanks for the pointers. However, wouldn't an interrupt conflict manifest
itself in all software? The crash only occur with 3ds and sometimes
Autocad, although 3ds is the main program used on that system. TIA.
Martin:
I think I would term PharLap as PC-abusive <grin>. I have often said that
if a system will run flawlessly with 3DS, AniPro, and R12 it is bug free…
I can't think of any software more demanding on a PC (not to say that there
isn't…).
C#
The ASPI drivers are constantly updated on the Adaptec BBS. Also it makes a
big difference whether or not your client is using the Adaptec Drivers for
each SCSI device. I am running a number of systems with similar
configurations, and after spending a number of hours trying to get the
boards to work finally updated to the 1740's. After all that's a lot of
work for a 1540. The aspi drivers shouldn't directly effect the cdrom if
it's connected properly and the correct cd drivers are in use. If you have
more exact descriptions of the equipment, driver revision numbers, etc.
I'll give our technical guru a call and see if we can't get your client
going.
Thanks Charley. I'll probably dig up the appropriate info (drivers
revisions etc.) tomorrow.