Damn! First clock smashes in Practice mode with 1.1 tonight.
J. P. Hovercraft
Pentium 200 MMX clocked to 166
64 Meg RAM
200 meg free space on C, 450 on D (where gpl is)
Orchid Righteous 3D Voodoo 1, current 3dfx reference drivers
ATI Graphics Pro Turbo PCI
Yamaha OPL-SAx
D-Link DEC 21041 PCI Ethernet
DirectX 6.1
Changes from core.ini.sample (re-named to core.ini)
clock_adj_delay = 16
synch_method = 0
disable_modem = 1
These changes seriously reduced the number and severity of clock smashes
from the original 1.1 patch without the re-named core.ini.
Why the hell would you underclock your pc?
so instead of getting hot it freezes itself!!! doubles up as a handy beer
cooler
Uh...because the mobo -will- support Pentium 200 but -not- Pentium 200
MMX. It sees it as a 166 MMX in spite of the fact that I've got it
jumpered to 200. Contacted the manufacturer and this is the only
solution short of a new mobo. It has not caused any problems in any
games/applications. I traded for the 200 MMX so it didn't cost $ and the
MMX significantly increased performance in Unreal.
Got a Socket 7 mobo you don't need?....8^)
J. P. Hovercraft
----------
> >Pentium 200 MMX clocked to 166
> Why the hell would you underclock your pc?
This is really odd. I just checked this: the jumper settings for the
"classic" P200 and the P200MMX are identical. Therefore, if you can
set the mainboard to run a P200 at 3x66MHz, this should work with the
P200MMX as well. Maybe the board is just reporting a wrong speed (old
BIOS), but the processor is indeed running at 200 MHz?
Otherwise, it is possible that one of your jumper caps is broken. If
you have a "newer" iP200MMX, it will only recognize multipliers of 3
and 2.5. Now, if you try to set a different multiplier (say, 3.5 or
something), the chip will default to 2.5. If one of your jumper caps
is broken, the CPU might interpret the setting as an attempt to
overclock and default to the low setting. Try and replace your
multiplier jumpers and see what happens.
Only broken ones, unfortunately. :) However, if you have some small
change to spare, you might consider getting an FIC VA 503+ board. It's
for sale for as little as US$ 50.- these days. The board allows you to
keep using your old RAM and components while running at 100 MHz FSB. I
use one of those boards in conjunction with an iP166MMX, which I
overclocked to 250 MHz about one year ago. It is very stable. If your
processor is actually running at 166 MHz now, you should see a
performance gain of at least 50% for a very small sum. Makes one
think, doesn't it? :)
--
Wolfgang Preiss \ E-mail copies of replies to this posting are welcome.
>>Uh...because the mobo -will- support Pentium 200 but -not- Pentium 200
>>MMX. It sees it as a 166 MMX in spite of the fact that I've got it
>>jumpered to 200. Contacted the manufacturer and this is the only
>>solution short of a new mobo. It has not caused any problems in any
>>games/applications. I traded for the 200 MMX so it didn't cost $ and the
>>MMX significantly increased performance in Unreal.
The jumpers on his board could also modify the voltage levels,
too. MMX CPU's had dual voltage, non-MMX may or may NOT have dual
voltage. If he jumpered it as a 200 it wouldn't supply the correct
voltage to the CPU.
Gunner
> The jumpers on his board could also modify the voltage levels,
>too.
That would be extremely stupid - which is not to say that no
manufacturer could have implemented such a stupid system. :)
Not exactly: There were Pentium VRE, which had 3.5/3.5v (core, I/O)
and Pentium STD, which needed 3.3/3.3v. No split voltage, only
different overall voltage. The Pentium MMX required 2.8/3.3v.
If the board recognized the CPU as VRE or STD, it would supply a
voltage above the requirements of the MMX. It doesn't matter whether
it's jumpered at 2.5x or 3x (166 or 200).
--
Wolfgang Preiss \ E-mail copies of replies to this posting are welcome.
Thanx for the defense, Don! ... 8^)
Actually, the voltage jumpers are a seperate setting, as are the P54 (non-MMX)
and P55 (MMX) jumpers. The voltage jumpers are set for the dual voltage
required for the MMX chip. I had to visit the chip ID site to make sure of the
required settings. The clock jumpers are set for the 200 MHz clock, but the
system -still- sees the chip as a 166 MMX.
J. P. Hovercraft
-----------------
