 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I came across a fix in a CST troubleshooting guide. MP.5 and SP occasionally
lockup my system.They are not the only two programs that do that, so I went
looking for a fix. I have tried this for over two weeks now, with great
success.
First, I am running a Compaq Presario w/ AMD K6-2 500/100, 128Megs, etc...
The fix is to run MSCONFIG.exe. (Start, Run, in the "Open" window enter
"msconfig" and hit OK. Under the "General" tab select "Advanced" and then
make sure "Enable Pentium F0 (Lock CmpXchg) workaround" is marked. Hit "OK"
and "OK" again, then reboot.
I haven't had a system lockup since.
I hope that helps someone.
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 8 Aug 2000 01:51:47 -0500, GrimDude wrote:
>The fix is to run MSCONFIG.exe. (Start, Run, in the "Open" window enter
>"msconfig" and hit OK. Under the "General" tab select "Advanced" and then
>make sure "Enable Pentium F0 (Lock CmpXchg) workaround" is marked. Hit "OK"
>and "OK" again, then reboot.
That seems odd. The F00F bug shouldn't manifest itself arbitrarily; it should
only happen as a deliberate effort on the part of one of the users of the
machine, or as a result of some malicious code.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker <ron### [at] povray org> wrote...
> On Tue, 8 Aug 2000 01:51:47 -0500, GrimDude wrote:
> >The fix is to run MSCONFIG.exe. (Start, Run, in the "Open" window enter
> >"msconfig" and hit OK. Under the "General" tab select "Advanced" and then
> >make sure "Enable Pentium F0 (Lock CmpXchg) workaround" is marked. Hit
"OK"
> >and "OK" again, then reboot.
>
> That seems odd. The F00F bug shouldn't manifest itself arbitrarily; it
should
> only happen as a deliberate effort on the part of one of the users of the
> machine, or as a result of some malicious code.
So.... what exactly are you trying to imply? ;-)
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
No malicious use here! :)
I was just reporting my results. There may be something going on behind the
scenes with Compaq computers, or the AMD chip on same. I bought the system
with 64Megs installed, but Win98 reported 56Megs available. I installed a
second 64Meg module and the system reported 128Megs available. Hmmm....
Anyway, the problem with lockups continued after the upgrade, so I went
looking for a fix. This is the one thing I tried, and so far no lockups.
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 8 Aug 2000 13:56:08 -0500, GrimDude wrote:
>No malicious use here! :)
>I was just reporting my results. There may be something going on behind the
>scenes with Compaq computers, or the AMD chip on same. I bought the system
That's even stranger... the F00F bug never existed on AMD's chips.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
That's what my documents stated, but I tried it anyway. :)
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
With 120 MB RAM (128 ram with 8 used as Video ram) I have NEVER had a
lockup with Megapov and that is with a AMD K-6 II 450 MHz CPU. could
it have something to do with the brand of motherboard or the brand of
chip u installed?
GrimDude wrote:
> That's what my documents stated, but I tried it anyway. :)
>
> Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
More likely some other registered program, or something silly, but you never
know. The last time this happened I was tracing a 320 frame animation with
full radiosity and low-low alias/high ray count, with 10.8Megs of source
files and a one hour parse time. It got to frame 49, locked up, and then on
reboot/restart/continue_trace it finished normally.
Should it happen again I'll ask you to retrace my steps. :D I can hear your
answer now (I don't think so!). Well, anyway. I haven't seen it crash in
three weeks now (I think).
I will say that using MP0.5 on a Win95 machine is a big mistake. There is
some difference between 98 and 95 that should have gotten more praise. I
don't know what it is, but there seems to be a problem in recovering
resources?
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
GrimDude wrote in message <399a40db@news.povray.org>...
>I will say that using MP0.5 on a Win95 machine is a big mistake. There is
>some difference between 98 and 95 that should have gotten more praise. I
>don't know what it is, but there seems to be a problem in recovering
>resources?
I've been using Mega since it came out (and super before that) on a Win95
OEM 2 and I've never had pov freezing. Haven't had a bluescreen since
the last reinstall (touch wood). (Last install due to HD crash)
My win98 machine at work however is a different story, crashes all the
time and generally has to be rebooted every 4-5 hours
Gail
********************************************************************
* gsh### [at] monotixcoza * Reality.dat not found *
* http://www.rucus.ru.ac.za/~gail/ * Attempting to reboot universe *
********************************************************************
* The best way to accelerate Windows NT is at 9.8 m/s^2 *
********************************************************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, I shouldn't make such bold statements, then. :)
Regardless, I am so sold on MegaPatch, that I never even start the other
builds anymore. I am hoping that the overall incorporation into the official
build goes smoothly.
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
