#Crashing question
3 messages in this thread
Kevin,
I agree with you; I think the hard disk vs. 3DS is suspect. Here's more info,
if in case you have a hint what's going on.
A few months ago I bought a 1.2 gB Maxtor drive with a CSC Fastcache 64
controller. It seems alot of demanding users like the drive and controller,
which on their systems – and otherwise mine – works reliably. I have 4 mB on
the controller and 32 mB of RAM on my Micronics motherboard. I run alot of
programs such using Windows and animation software such as TOPAS, Crystal,
Animator Pro, QFX, etc. I don't have any problems with any other programs. (I
review software for about a dozen magazines) So, Maxtor and everyone else
logically point to 3DS as the culprit. I've futzed with as many dip switches on
the controller, changed addresses, removed other boards, booted without
autoexec.bat and config.sys, made major changes to both, modified QEMM
settings, and still no change.
With this info 3DS tech support are at a loss, and in the meantime I'm
crippled. Got any ideas?
Thanks. -Gregory MacNicol
Gregory,
I'd swap the controller for one without a cache. If you're using TOPAS
4.x, that uses the PharLap DOS Extender, but a different version than 3D
Studio. There's always some possibility of other motherboard BIOS settings
that can affect you, as well as other conflicts. Obviously, I wouldn't be able
to get far without the equipment in front of me.
Kevin Krell – Computer Support Associates
PMJI, but did you try disabling shadow RAM in your BIOS setup?
I don't even know what your problem is (I just picked this thread
by accident) but from what you iterated trying I got the impression
you had a similar problem to what I had first experienced with
3DS — I tried everything as well, but as soon as I disabled the
shadowing of all RAM (video as well) my system worked fine.
Just a thought…