How big does a 200gig show in windows?

Bizkitkid2001 · January 2nd, 2004, 03:42 PM

I can't get my drive to format. This is pissing me off. It gets to 100%, then it sais "Unable to format"

Gettinbye · January 2nd, 2004, 03:48 PM

Thanks for clarifying, Jmichna. Goes to show you learn something new everyday

Biz-as far as being unable to format, perhaps the manufacturer has a utility that would prove useful...

Bizkitkid2001 · January 2nd, 2004, 03:57 PM

I ran the diagnostic tool from WD web site and got an errir when I ran it "Cable Test; Read sector error"

I have this drive hooke dup with a 40pin ide cable, because the 80pin that came with the drive broke. Maybe i need to get an 80 pin before i RMA this drive back.

Uncle Bob · January 2nd, 2004, 03:59 PM

Quote:

Originally posted by Bizkitkid2001
I can't get my drive to format. This is pissing me off. It gets to 100%, then it sais "Unable to format"

You think you have a problem? I have 4 WD 40gb hdds. I wanted to do a raid set up using 2 of the drives. No mater what combination I used I couldn't get them to format. Each drive will format and load Win2K indivually, but I can't get them to work in pairs.(hmmm 4 new paper weights/door stops)

jmichna · January 2nd, 2004, 04:08 PM

Quote:

Originally posted by Bizkitkid2001
I ran the diagnostic tool from WD web site and got an errir when I ran it "Cable Test; Read sector error"

I have this drive hooke dup with a 40pin ide cable, because the 80pin that came with the drive broke. Maybe i need to get an 80 pin before i RMA this drive back.

Although the 40-pin cable might not be the best way to troubleshoot this situation, it should still allow the drive to format, albeit run at ATA-33 speed.

Aside from the possibility there is some thing really wrong with the new HD, can you confirm your mobo BIOS supports "48-bit LBA addressing"? See http://www.seagate.com/support/kb/di...137/index.html and http://www.seagate.com/support/kb/di..._overview.html.

There seem to be a lot of issues regarding proper recognition of 200GB HDs.

Bizkitkid2001 · January 2nd, 2004, 04:10 PM

Whats strange is that windows shows the drive as 186gig, but the WD utility only showed the drive as 137gig.

jmichna · January 2nd, 2004, 04:12 PM

Quote:

Originally posted by Bizkitkid2001
Whats strange is that windows shows the drive as 186gig, but the WD utility only showed the drive as 137gig.

That seems to point toward the mobo BIOS not recognizing 48-bit LBA Addressing... hmmm.

Bizkitkid2001 · January 2nd, 2004, 04:24 PM

I updated the atapi.sys file from that microsoft artical. But i still get the secter error. I have an epox 8rda+ mobo, i thought this board could read 200gig drives.

jmichna · January 2nd, 2004, 04:34 PM

Quote:

Originally posted by Bizkitkid2001
I updated the atapi.sys file from that microsoft artical. But i still get the secter error. I have an epox 8rda+ mobo, i thought this board could read 200gig drives.

Does the the WD utility you got also "prepare" the drive (create partitions, etc.)?

If so, and knowing you have a newer mobo, I'd replace the cable with a proper ATA-100/ATA-133 cable before further attempting trouble shooting, then physically disconnect HD (unplug power and controller cables), set BIOS to default settings, reboot, shut down, than reconnect drive, and boot to the WD utility and use that to prepare your new drive.

You might also head over to some EPoX-focused forums such as AOA Forums and AMDMB Forums... both these forums have official EPoX reps as contributing members. (I own a few EPoX baords, but they are all KT333... I have no nForce mobo first-hand experience).

Bizkitkid2001 · January 2nd, 2004, 04:50 PM

I doownloaded data lifeguard, and its formatting/partitioning right now. I am going to see if that works.