cpu overclocking

i have a PII cpu and its says 350mhz on another motherboard and only 333 on mine im running a ABIT BH6 motherboard and what are the settings in cmos to change it ,if possable thank you,bigfoot

1. RE: cpu overclocking
lbyard Nov-20-01 05:14 PM
In response to message 0

I do not overclock CPUs and do not recommend it. There are very good reasons for this and good reasons for manufacturer’s specifications. This question belongs in the Computer Performance Forum. Larry

2. RE: cpu overclocking
Bigfoot Nov-20-01 05:18 PM
In response to message 1

ok,i wasnt sure where it went but i got it figured out,i was looking at the turbo speed and the cpu speed being "disabled" for both the cpu and the turbo speed and not just the turbo speed,now my cpu is running at 450mhz very smooth i might ad,thank you for your time.

3. RE: cpu overclocking
lbyard Nov-20-01 05:33 PM
In response to message 2

Wait until you discover that you have some corrupted files on your hard disk and you might change your tone some. Larry

4. RE: cpu overclocking
Aehs Nov-28-01 02:32 AM
In response to message 3

Have you checked out the Amdmb.com Forums Larry? Like 75% of the people who post have overclocked systems, I've got the Epox 8KHA+ with tons of overclocking features but i'm not "pushing the limit" with my overclocking.. fooled around with the FSB and have it clocked at 1540mhz, 1466 being default. Had it running smooth for weeks and could probebly go higher.

7. RE: cpu overclocking
lbyard Nov-28-01 06:26 PM
In response to message 4

I read a lot of stuff on a lot of web sites nearly everyday, including amdmb.com once and a while. Just because many people are overclocking their CPUs and some motherboard manufactures are even catering to that crowd, does not make it a good practice. It might be fine to play with things like that as a hobby when all you have to lose is the time to reinstall a hard disk drive or game that has been corrupted, but it is not OK, for an extreme example, when one is running an accounting program used to print pay checks every Friday. Or, when a person like myself builds computers for home or business users and has to stand by them and support them. Etc. There are sound engineering reasons for not exceeding manufacturers’ specifications and recommendations. Overclocking is a poor practice. It can produce unpredictable results that may not be immediately apparent. It can corrupt files without the end user being aware of it until extensive damage has already been done, even if the computer appears stable at first. An overclocked computer can operate OK for some time and then suddenly go awry when environmental conditions change or components age. There is nothing new about overclocking. Against my best judgment, I did it a long time ago and got severely burned for doing so. I no longer do it and do not recommend it. Others have every right to do what they want with their computers, including being lemmings. Larry

8. RE: cpu overclocking
rabnud Nov-30-01 06:56 PM
In response to message 0

I also investigated overclocking, and found that I had no apparent problems when I tried it on my FIC mobo... operative word is "had" (no, not "apparent"). I decided that the whole system is more reliable when it is tested at the factory by the people who designed it. Having been a career EE design technician - over 25 years - let me say that you have already heard me state why I'm not doing it any more... I'll repeat it, so you can be certain: the factory wants reliability. Their test equipment (costing millions of dollars) is far more accurate at determining what is a marginal device, when compared to "run it and see what happens".
I then decided to reset everything the setup to factory speeds, because I have no more money to throw at reparing whatever fails.
Remember: if Intel or AMD or Cyrix could have sold the processor as a 50 bazillion gigahertz processor, you can bet it would have - they get much more money for the higher clock rate silicon - that is one reason why overclockers do what they do. Overclockers also serve to keep the chipmakers honest, by discovering and openly announcing which silicon is simply too close to being unreliable (it can't be overclocked if it is just too close).
Oh, and did anyone mention to you anything about voided warranties? Overclocking will void your warranty, when it is proven that you did overclock.
The choice to overclock comes down to: must the hardware and data survive - family records, corporate work at home, unique music compositions, etc., etc., or is your system a toy - gaming, etc? The concept is very similar to hotrodding a car: if you supercharge your only car, what will you drive when the engine fails due to the added stresses from the supercharger?? Not *if* it blows, but *when* it blows, because something will become unreliable eventually. Thus, if the system isn't mission critical, and you have no intention of sending a blown overclocked system in for what would be thus be fraudulent warranty claims, have a ball; just remember do not whine to *anyone* when it clocks its last byte. And from what I'm hearing, keep a fire extinguisher handy!
Aside from that, have fun, and use your head - there are quite a few hokey looking tricks out there....