I have the holes punched out of the casing. For the outtake fan, the fan
sits directly on the casing. The input fan at the front sits against a piece
of metal about an inch from punched holes, and is encased in a plastic
protector.
It sounds like your case is working against you. Sometimes it's
easier to just add an intake fan to the side-panel, since it just pops
off and doesn't require any system downtime to take all the bits out
of the whole case.
About an inch of space on either side on the edges. I suppose I ought to get
round ones. Are they interchangeable between IDE and RAID - I don't need
anything special? They have to be UDMA 133 ones?
RAID uses the same cables... ATA33 are 40 conductor and very rarely
round. ATA66/100/133 are all the same, 80 conductor cable. If you
didn't see specs just a picture of a round cable the odds are very
high that it's 80-conductor. Another clue can be that 80-conductor
cable are usually with colored connectors, blue to motherboard, grey
in the middle for slave and black on the other end for master.
How will I know when I need to raise the voltage?
The heatsink is rated for a XP3200.
It helps to have an idea of the average ceiling for your particular
model of CPU. There are several places to find that info but the
simplest in this forum would be to just go here and select the CPU
from the drop-dwon list:
http://www.cpudatabase.com/ . You can pretty
much ignore any results with water-cooling or even more exotic
measures like the Prometia. You can usually ignore the lowest scores
too for a variety of reasons like incompetence, no desire to push the
CPU, or bad power supply, motherboard, or just a "dud" CPU... you'll
have to assume for the time being that you don't have a dud CPU, and
hope for typical results.
Providing you get your case airflow improved you should be able to run
at least 1.7V with that heatsink, but you may not even be able to
choose >1.85V with your motherboard, and more-often-than-not the heat
resulting from voltages over 1.8V will limit overclocking... you might
be able to hit a higher speed at 1.8V than 1.9V with an air-cooler.
So anyway from that list you'll see most people are hitting the
2.2-2.3GHz range, so that's a good target. Write down your BIOS
settings since there's a pretty good chance you'll be clearing the
CMOS to get the system booting again after it's set too fast.
With the FSB left unchanged and manipulating the multiplier you'll be
isolating the CPU (if we can assume the motherboard is capable of
supplying enough power, which it should since there are 2.2GHz stock
speed CPUs supported by that board. You can either raise the
multiplier till it won't POST, then clear the CMOS (or check the
manual for a keyboard key to revert to CPU defaults at power-on), then
raise the voltage a notch till it runs stable, or go backwards- Raise
the voltage to the max you think is acceptible and then change the
multiplier, working backwards till the reduction in voltage introduces
instability... at some point you'll have to decide how much work you
want to put into it, just settling for an easy overclock or finding
the max or the best voltage to speed tradeoff... keeping track of the
voltage vs speed results may help you see a "curve", where each minor
increase in speed requries increasing the voltage more and more.
I suggest you try 1.7V and see how high it'll run stable, putting the
system through it's paces, and do a Google search for some CPU stress
tests. If it's stable then you decide to leave it there, decrease
voltage for testing same speed again, or raise speed with same
voltage. FOr a margin of error you might want to increase the voltage
0.025 over the lowest that tests stable in use.
After you get an idea of the voltage and total MHz speed for the CPU
then you can drop the multiplier to default again, leave the voltage
raised, and test the FSB, see how high that will go... you don't want
to change the voltage for that since you need a "constant", you know
the CPU can run higher than the resulting frequency at the voltage
used so the CPU is then removed from the equation and focus is then on
memory, PCI bus, AGP, etc. This part of the testing is a lot more
difficult, time-consuming... this being your first exercise, you might
consider leaving the FSB under 174MHz, being sure to test with
http://www.memtest86.com for several hours BEFORE loading and running
windows... we don't want the memory causing any data corruption. I
usually leave the memtest floopy in the system so if i accidentally
forget it'll boot to that instead of windows.
At this point I feel like I only skimmed the surface, didn't really
give a comprehensive overview at all... do a Google search for some
overclocking tutorials, 'tis better to be safe than sorry. Also be
sure to backup data on the hard drives prior to trying any FSB over
~174MHz, as higher resulting PCI bus speeds could corrupt the hard
drive(s). All overclocking is done at your own risk of course.
Dave