View Full Version : Cel 566 on Asus P2B-B
rincewind
01-17-01, 06:54 PM
I got a Asus P2B-B Rev 1.01 MB. I want to buy a new cpu but I don't know if a cel566 or cel600 would run on this board. Has anyone experience with these cpu's on a P2B-B Rev 1.01?
Criminal
01-17-01, 07:17 PM
You can check out this site:
http://www.ctechnet.com/hardware/asus.htm
They list ASUS P2B-XX mobos that have successfully used coppermine cpus.
rincewind
01-17-01, 07:43 PM
I know this table, but it doensn't help me very much. So what I know is that my BIOS supports Coppermine-CPU's, but what I read from this table is, that my MB-Revision does not support Cu-CPU's officially, because the VCore does not go down to 1.7V. Now what I want to know is:
Does anyone know what's the minimum VCore my Board supports and if I use the minimum VCore, will I be able to run a Cel566 or Cel600 on my board (e.G. at 1.8V, if supported, or even at 2.0V)?
soda911
01-17-01, 08:40 PM
hey whats up, i have an asus p2b which is older then yours, just get the newest bios revision and an asus slotket and change the voltage on the slotket to 1.8 and everything will run smooth.
rincewind
01-17-01, 08:46 PM
Do you use a P2B or P2B-B? Or is there no difference between them except for the form-factor?
soda911
01-17-01, 10:54 PM
P2b
kunsunoke
01-18-01, 11:38 AM
rincewind (Jan 17, 2001 06:54 p.m.):
I got a Asus P2B-B Rev 1.01 MB. I want to buy a new cpu but I don't know if a cel566 or cel600 would run on this board. Has anyone experience with these cpu's on a P2B-B Rev 1.01?
You're gonna overclock this thing - right?
If so, you'll need the voltage up around 1.8 or higher anyway. A good Slocket adapter (ex. Asus) should get you workin'.
This all assumes that the P2B-B can deal with the C-II microcode. Keep in touch with this thread & we'll help all we can.
rincewind
01-18-01, 08:19 PM
I don't exactly know if my board can deal with the microcode. I know that my BIOS can. Does this only depend on my BIOS? And, yes, I want to get it to 850 Mhz.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.