OT hard drive fails above 150FSB, but Seti flies!

[cakin]

Working out the wrinkles on my new rig.

Epox 8KHA+, XP1800, OCZ PC3000, WD80Gig@7200
with fast timings at 1725Ghz, 150 FSB Sandra shows memory at 2263/2089 and cpu 4770/2389
I haven't unlocked the CPU yet! I will wait a few weeks for that.

The memory has been tested good to 183FSB.

The problem is everything works fine at 150 FSB, at 155 it doesn't recognize the hard drive.
Anyone know of a hard drive that handles overclocking? Or how do I get the current one to work at that speed

last two WU's
.486 AR in 3:18
.427 AR in 3:22,

I would like to at least get 166 FSB out of this thing.

Using the new Thermaltake Volcano 7 since its quiet, highest temp so far is 114F under load when the heat kicked on in the house this morning.

 

[bot2600]

Is there an option to change your PCI/AGP multiplier in the BIOS?

Bot

 

[serialb]

I am running my 1800+/8KHA+ with a pair of Quantum AS drives in RAID 0 on a Promise FT66 card. Windows loads fine under 150 FSB but stability drops.

 

[cakin]

I'm wondering what would happen if I turned off UDMA access to the drive and used a lower PIO mode?

The 80G actually belongs in my server as a backup drive for my other machines.
I just have found another cheap drive yet.

 

[IsOs]

I usually find Maxtor drives to overclock farther than Western Digital.

But perhaps it's the onboard IDE interface. Is there any option to change PCI divider?

 

[Factor5]

I also have my wu time down in the 3:20-3:30 range... i using a 151 FSB right now on a Maxtor Drive.... works fine for me... my sound card gets unstable at about 155

 

[cakin]

switched over to maxtor 40G same thing happens. boot drive unavailable when over 151 fsb

 

[Ken g6]

If you can't run SETI with a hard drive, you could try it without one!

From my post of Jan. 14:

<< First, I wanted to let you know about the scripts I am using to run S@H on KLinux. I've uploaded them to my other web server. You put these, a static S@H for Linux binary, and your user_info.sah file on one floppy, KLinux on another. Boot KLinux, login, and type:

mount /mnt/floppy
/mnt/floppy/i
/seti

and it should run. >>

Note, however, that this uses the slower Linux client, so it might be a toss-up which runs faster.

 

[JWMiddleton]

I would turn off UDMA at a working speed. Then reboot to the higher speed. Then turn on DMA and reboot. It should test the system as it is booting to see how it should be set. Having DMA and a stable HD is much better than not having it work with UDMA.