heh, hijz wel oud maar je zou hier wel tips uit kunnen halen denk ik
Initial Power-Up Typically, if you get the machine to boot, count its memory, and give you a close or correct megahertz indicator for your CPU, you're on your way to success. (Note: The new core speed, expressed in megahertz (MHz), often will not be correctly indicated in the boot-up screen if it's a nonstandard number, such as 372 MHz.) If the machine refuses to boot up at all, there are two possible problems: there isn't enough voltage going to your CPU, or your CPU has simply failed to run at the speed you've set it to run.
When you increase the megahertz level request, the CPU sometimes needs to draw more power to achieve that new setting. If your motherboard supports it increase the voltage in small units.
So, for instance, you might want to run a 300-MHz Pentium II at 3.0v, rather than the default 2.8v, when overclocked to 350 MHz. However, you'll need to experiment a lot, as 3.0v may be more or less than you need, depending upon your specific CPU. Fortunately, the latest motherboards will not let you go too far on a "more power" binge--when it comes to voltage settings, you can do only a little tweaking either way. Increasing the voltage going to your CPU is quite dangerous and should only be attempted with extreme caution.
If you have changed the only Bus speed in Bios and delightfully saved the changes and exited to get blank screen without showing any sign of life. Wait !! Don’t Panic !! Put the power off and then on. Still no signs of booting. Now it’s time to get screw driver. Open your cabinet. On the motherboard you will find a small battery (bigger in size compared to what used in clocks). Take the battery out from it’s place. Wait for ten or twenty minutes or short circuit both the circuits holding the batttery with your screw driver. BUT JUST FOR ONCE. This will clear the CMOS. Place the battery in it’s place. Screw up the cabinet. Now boot up. Relax. You have done it. (My first overclocking experience. I tried on my friend’s Computer. HI HI HI !! Actually what I did in hurry was I set FSB spped of P-II@266 MHZ directly to 83 MHz. )
Windows Boot-Up Several problems can occur during the loading of Windows 95 or 98. Remember Windows 95/98 is much more picky about overclocking. Therefore it might be that you can't run Windows 95 properly with your overclocked CPU though it was working just fine with DOS and Windows 3.11. You'll either have to improve the cooling or you'll have to forget about overclocking your CPU with Windows 95. This is also where the problem of overheating comes into play. If your machine has booted up, displays the correct or near-correct megahertz level for your overclocked CPU, and then proceeds into the Windows load screen only to freeze, you can try two corrective measures.
First, go into the system BIOS and lower the hard drive's PIO level one notch below its previous setting. (This is only for people using a higher-than-100-MHz FSB speed in their overclocking efforts.)
Second, reduce the CPU's heat by taking the cover off the case and removing all nonessential PCI components.
These two steps might not seem like much, but aside from increasing the voltage of the CPU, they're most likely all you've got left. In many cases, it's possible to realize as much as a 15-degree Fahrenheit reduction in internal system temperature simply by taking the cover off the case. For maximum stability, many die-hard overclockers run their machines full-time with no cover on the case. As long as you take time each month to clean the system of dust, you should have no problem running your machine topless. However, be aware that some cases are designed to take advantage of the airflow created by a closed case.
After taking these steps, if the machine still refuses to boot into Windows, it's more than likely that you've set your CPU to a speed beyond its limits. Cooling usually solves some of the problems, but if you are able to boot into Windows only to suffer from crashing and system instability, you've clocked your CPU too high. Either try a more conservative overclocked setting, or return to your CPU's default settings.
One other instance where the machine boots properly into Windows but then proceeds to develop strange errors could be caused by the quality of the SDRAM in the machine. If you're clocking your FSB to 100 MHz or 112 MHz, make sure you are using 100-MHz SDRAM. Even in the PC-100 SDRAM subcategory, however, you must choose between a maximum CAS latency timing of "3" or "2". Memory that supports a CAS latency timing of 2 can sustain the 133-MHz FSB overclocking option of the Intel 440BX chipset. CAS 3 SDRAM, however, can't handle any bus speed beyond 112 MHz
[
Voor 3% gewijzigd door
Verwijderd op 12-02-2004 00:09
]