DJW wrote:
> How can I find out the bios setting for a computer that someone
> basically home built? I can’t even install windows 98SE without
> getting blue error screens during installation. I think the problem
> might be that the CPU speed is set wrong. Is there any way in DOS to
> read the type of Pentium III that it is and how to set speed caches
> and multiplier factors? Are there any setting that should work being
> can a fast CPU run OK set slower than it can handle? There is a heat
> sink and fan over the CPU chip. If I went to the trouble of
> disconnecting an removing some stuff in order to get to the top of the
> CPU chip would I find information that would tell me or let me track
> down its speed and in conjunction with the BE6 motherboard find what
> ALL the BIOS setting should be?
You might still be able to find a copy of the motherboard
manual floating around on the 'net. I'd try one of the
remaining Abit sites, but my batting average there hasn't
been too good.
http://www.motherboards.org/mobot/manuals/Abit/BE6/
http://www.motherboards.org/files/manuals/2/be6.pdf
"Press <Del> to enter setup"
The BE6 is a 440BX chipset motherboard. And according to the
manual, it doesn't use multiplier and FSB dip switches. (On
the 440BX based board I've still got, it has DIP switches
to play with.) The manual claims full control is available
via the BIOS screens. Normally, the processor "BSEL" pins,
communicate the desired clock, from the CPU to the motherboard.
Many motherboards have options to bypass that sensing (like
the DIP switches), so you can overclock. With my original
cacheless Celery 300, I could manually dial in 100MHz, to
get a 450MHz processor for free. On the BE6, you can do that
from a BIOS menu.
The canonical clock frequencies are 66, 100, 133, and the
reason those are preferred values, is the PCI bus runs at
33MHz when you use those values.
On 440BX, you have another setting, which sets the ratio
between the CPU clock and the AGP slot. If left at 1:1 for
example, it can result in the AGP slot clock being too high.
Options are 1/1 and 2/3. 100MHz times 2/3 = 66MHz would be a proper
AGP input frequency. If the processor actually ran at 133MHz,
then 133 * 2/3 = 89MHz, which can be met by at least some
video cards but not all. My motherboard couldn't go over
112MHz, so my AGP never got stressed at all. Some AGP video
cards were quite picky about input clock and would stop at
75MHz (perhaps a PLL issue of some sort). The older video cards,
may be able to go much higher, to as much as AGP 100MHz
(FSB 150MHz times 2/3).
The CPU multiplier option is usually bogus - on all the processors
I've had in my 440BX (about four of them), they were all locked,
and the multiplier setting did nothing. So that leaves CPU
input clock, and AGP slot ratio.
In the case of "bugged" CPU choices, with an old BIOS
that can't handle an 11x CPU, setting the FSB to 66MHz
is a workaround. That may get the system running long
enough, to do other kinds of testing, without taking
it all apart. With my Asus board, Asus released a final
BIOS, that supported the "bugged" choices, so even those
would run without trickery. And by doing a microcode
update, with CTMC, I was even able to avoid a microcode
error at startup. The last time I tested the machine
(within the last month), it still worked. I'd put a
new CMOS battery in it a couple years ago, which is why
it still works and boots immediately. The last time
the battery went flat, it took me a half hour to figure
out what some of the BIOS options did.
Intel makes utilities for identifying the processor.
For modern processors, there is a floppy version of
Intel PIU. But your processor is one of the older
ones, not handled by PIU. So you'd want the PFID
utility on the right.
http://www.intel.com/support/process.../cs-015472.htm
This one is self booting. I expect this writes over a blank
floppy, to prepare it with FreeDOS boot files and the like,
so you'd run this utility on another computer, and have it
prepare a blank floppy for you.
http://downloadcenter.intel.com/Deta...eng&iid=dc_rss
There is no guarantee the Intel utility will get the right
answer. For example, within a virtual machine, the Intel utilities
don't work right. And in cases where a Xeon is installed
in a desktop, the answer might not come out right. And
you aren't likely to get an "SLxxx" code from the tool.
It might report the frequencies currently in use, but
won't completely remove doubts from your mind. Which means,
running the above, won't tell you everything you might
want to know. I run stuff like that, more for fun than
anything else (like if I need to know, what an OS
thinks about my processor - if an OS is having trouble
identifying a processor, then the Intel utility may
report a similar issue).
HTH,
Paul