#Rebooting
16 messages in this thread
Gary- Help. The Reboot gremlin has struck one of my machines. Whenever
I'm in the materials editor and select A for automatic reflection map and
then click on the word AUTOMATIC, my machine either locks up or reboots.
Any ideas what could be causing this? To my knowledge, I havn't changed
anything in my system lately.
-Mark
Mark, it's hard for me to help you without knowing exactly what your system
environment is like. Are you using an RCPADI driver in the materials
editor? If so, turn it off and see if it still happens. The next thing
I'd do is re-install the executable… something may have corrupted it on
your hard disk. Try that and let me know if the problem persists.
– G
Gary,
I also have the reboot problem.
I have a Zeos 486/50 with Diamond Stealth VRAM and Sony 1604 monitor.
I use the RCPVESA driver. Everything was fine until my motherboard went
bad. I swapped it for a new one and my problems started. In my case the
system reboots when I try to render to VGA using RCPADI, right after the
rendering is finished and the system gets rady to swap screens between the
standard 3DS display and the rendered image.
Any Ideas?
Jorge
Jorge, it sounds like you've got a completely different problem. Mark was
able to re-install his software and it went away, so it was obviously
caused by something that had gotten munged in his environment.
In your case, it sounds like you may have a motherboard problem, since
everything was fine till you swapped it. If I were you, I'd get a copy of
Vibrant or Panacea's ADI driver for 3DSr2 and try that out on your system.
If that doesn't work, I'd call up Zeos and get them to swap you out again.
Just a thought, first… are you using QEMM as your memory manager? If not,
try that before you do anything else.
– G
When you swapped out your motherboard, did you keep the same math
co-processor (or was it a 486 with no Weitek?). Occasional reboots are
sometimes caused by a faulty math-co, or one that needs reseating.
I had rebooting problems for a long time on a 386 running AutoCAD
and it turned out to be an old version of the BIOS chipset. After changing
the chips the problem went away.
TedB
<<turned out to be an old version of the BIOS chipset>>
Thanks for the tip. It's always something, eh?
Phil,
It's a 486 with no coprocessor. I'm also using Qemm v-6.0. It doesn't
happen on my 486/33. Only on the 486/50 (they have different video cards).
Do you think it might be a driver problem?
Jorge
You're in a vague realm. If you've booted from clean floppy, disabled
shadow ram and memory caching, and run the system that way, as stripped as
possible, and it still reboots at random moments, slowed the machine down
and it simply reboots more slowly, well, it may be time to start pulling
hair. Some one else's, preferably. You can try swapping video cards
between the two machines and see if that changes anything.
Mark, periodic rebooting, especially when it happens every time you do a
particular action, often indicates a faulty math co-processor, believe it
or not. Not always, but it's been known to be the answer more than 50% of
time.
Phil- Thanks for the hint on rebooting. In my case I'm not using an
external MathCo (486) but I think my .EXE on my hard drive must have gotten
corrupted somehow. I ended up reinstalling the .EXE and everything works
fine again. Thanks.
-Mark
I've been having a predictable problems like that, too. Whenever I load a
large .3ds file (such as in the ACAD or HIRES directories on the CD ROM)
I'll get a reboot.
It's on a 486/66, so I figure it has something to do with this test board.
Loading a large file and getting a reboot is ALWAYS due to either a memory,
environment (re: memory manager), or hard disk controller problem.
– G
Ok, I'm using QEMM and only have about 530K base memory, 32Megs of ram
installled and I'm loading from the CD Rom.
Any ideas?
Since you're using a 486/66, my guess is that there's something wacky going
on with its memory or hard disk controller. Not much I can help you with
regarding hardware, unfortunately.
– G
That's what I figured.
Has anyone else out here benchmarked a 486/66 against a 486/50?