🚀 go-pugleaf

>>The best way to speed up an intel 80486-100DX4 is to find the clock
>>DOUBLING pin, shorting this high/low causes the CPU to either
>>clock triple or clock double the incomming clock.
>
>Finally - someone who knows what they are talking about.
>According to my reference, tying that pin to another signal (cannot remember
>which one) switches the chip into 2.5x mode [not sure what that would be useful
>for].

my understanding is that only the Intel chip can run at 2.5 the clock.  
On my motherboard the AMD clock can be selected to run at 2X or 3X.

If i had an Intel chip i would use a 2.5X clock with the base clock at 
50Mhz.  This *should* work.  I got my dx4 to run at 120Mhz, but not at 
150Mhz, but i am running only at dx2/100 (i.e. 50Mhz base clock).

>
>The disadvantage is that (for my motherboard at least) is that going from 25/33
>to 40/50 MHz I need to increase all the wait states by one. I am not sure if
>the slow down this causes would outweigh the speed up of 33->50 MHz local bus
>speed.

I had to add a couple of wait states here and there, but they made a 
*very* small impact on the overall speed.  For example 3dbench runs much 
faster at dx2/100 than at dx3/100.  And there is *no* benchmark 
difference at dx2/100 with more wait states.

>
>>Also if you're buying a DX4 CPU think hard about paying the extra for
>>the intel part as it has 16K of on chip cache where the others only
>>have 8K.
>
>It also has a faster integer multiply (than the DX or DX2 parts).

considering you can get the AMD for $165 and the Intel for about $320 
(maybe more like $300 now) i wouldn't bother with the intel for twice as 
much for a lot less than twice the perfomance.

.t

*******************************************************
      " Where you should be Today - OS/2 Warp"

Tate Needham    - u933692@student.canberra.edu.au
                -    spud@acslink.net.au
*******************************************************