#Rebooting problems
4 messages in this thread
Phil:
Just today I had Everex replace my 486-33DX computer because it was
rebooting on a regular basis while running 3D Studio. Then, I joined the
forum tonight, and note that the problem may be in 3D Studio, not my
computer! Several times, I have had it reboot while I was not even at the
computer, and other times it reboots while I am working on a project. Are
there any answers yet? I feel bad for Everex – the machine was under
warranty.
Also, I can't get AUTOSIG to work at all. I get into the program, but
then it won't let me type in anything from the keyboard – like GO ASOFT
from the GO menu. Thanks for your help.
Dale:
Well…. you're gonna hafta print out the AutoSig manual… there's no
other way to figure out how to use the program… but, since it's free,
that shouldn't be something to complain about. I had to read the sucker
three or four times to get my use of ATO up to speed…
There are numerous reasons why 3DS can fail… primarily because it is a
DOS extender program. I don't know what message you are discussing (since
I'm jumping in, here) but I don't know that I would blame the problem on
3DS just yet. Running out of disk space when you're paging to disk will
probably muck things up pretty good for starters, and 3DS uses lots o'
memory and lots o' disk space <grin>.
C#
If the computer was rebooting while you weren't even there (I assume that
means while it wasn't doing anything — just sitting there), that might
indeed be a hardware problem. It is not at all usual for 3DS to
spontaneously reboot. Such occurances, when they happen, usually mean that
Studio and the computer's memory, TSRs, memory mangers, etc are in
contention for memory resources. Or, put another way, something's not set
up correctly. The most usual thing is that a memory manager and a video
card are fighting it out with each other. For example, if you are using
QEMM you might need to exclude certain portions of upper ram from QEMM's
use (the QEMM manual has much more to say on this topic). It could also be
caused, on some machines, from the computer's own memory caching or shadow
ram; check the computer's setup to see if there is any of this you could
experimentally turn off.
~The only other thing is some very scattered reports of reboots occuring
with certain meshes. We are not sure what this is, as we can't reliably
duplicate the condition. It might be related to some corruption within the
.3DS file itself. This is extremely rare overall.
ATO is meant to be run automatically. If you set up the forum options with
the proper GO commands, etc, then it should work for you. You may have to
log on manually, GO ASOFT, OPTIONS and change some of your default forum
options before it will correctly thread messages for you. These settings
should be covered in the ATO documentation. If this doesn't help, you can
try over in the IBM forum (I think it is); that's where the primary support
for ATO lives.
it's not in your computer. i am running 6 different computers… 486/50's
to to 386/40 amd's and i don't have a problem in the world .. as long as my
CONFIGURATION is right.
sherwood