OT: windows 130GB disk limit

[edgley]

I found out the hard way that when you write more than 130GB of data to a disk on XP, it goes back to the start and over writes data.

As I see a lot of you have large disks I was wondering what you do to prevent this from happening.

s.

[zz5]

I've never had this happen.

[stanger89]

I've got a 200GB and 160GB in my HTPC w/o any problems. I had to install Intel Application Accellerator (845PE board) to get Windows to see the whole drive though.

[carlgar]

Originally posted by edgley
I found out the hard way that when you write more than 130GB of data to a disk on XP, it goes back to the start and over writes data.

As I see a lot of you have large disks I was wondering what you do to prevent this from happening.

s.

This sounds like the 137 GB barrier problem with some Operating Systems. You may not have all patches needed on your system. You should go into help and Support for your OS and search on "137 GB". The most useful article for me was "How to enable 48-bit Logical Block Addressing support for ATAPI disk drives in Windows XP", but I have no idea what OS you are using.

[mikejaner]

Make sure you have Windows XP service pack 1 or higher installed. That should open up the extra space on your hard drive.

You probably mean Sage is overwriting shows after it fills up the 130 gig partition.
After you install service pack 1, kill the partition and create a new one. You will then be able to create it larger than 137 GB. OF course you can't do this if it's installed as your boot drive. Let me know if you have any other questions.

[edgley]

I had SP1 installed when I had the problem.

It has taken a while to get all the data back, and I am approaching the 130GB mark again, and I am becoming quite nervous.

I am using XP Pro, with all updates. I need to read that artical about 48 bit me thinks.

I have had no problems setting up partitions of 130GB or greater, btw.

[Opus4]

This might save some search time: How to enable 48-bit Logical Block Addressing support for ATAPI disk drives in Windows XP

Among other things, pay particular attention to the version of Atapi.sys installed on your system. I certainly know about that one now...

Additional articles:

Maxtor

Western Digital

- Andy

[stanger89]

And if you have an Intel chipset, install Intel Application Accellerator.

Regardless of your chipset, make sure you have your IDE drivers (may be included in with the chipset/mb drivers) up to date.

[edgley]

I had read, probably on AVS that you shouldnt install IAA.

Some people had tested it and it turned out slow things down.

Will do and check the article.

Nice to have a personal search engine

[edgley]

right, my version of ataip is 5.1.2600.1164 when it should be 5.1.2600.1135.

So is it right that I have to go back to an older version??

Edit:

Have run the installer here, as the article said:

http://www.microsoft.com/downloads/d...DisplayLang=en

But when I checked my version of ataipi, it was still the newer one

[carlgar]

No, you have a newer version so you should be OK there.

[edgley]

Is there a way that I can confim that it is 48 bit?

My setup is the same as it was when I lost it last time, so how do I know please?

[Opus4]

Originally posted by edgley
my version of ataip is 5.1.2600.1164 when it should be 5.1.2600.1135.

You've already got a newer one mentioned in: Problems When Your Computer with Multiple ATA Drives Enters the S1 Power State.

Google finds lots of stuff...

Edit: in addition to what otehrs have said, above, be sure to run your drive manufacturer's diagnostic utilities. I've had more than 1 brand new drive that was DOA.

- Andy

[carlgar]

Originally posted by edgley
Is there a way that I can confim that it is 48 bit?

My setup is the same as it was when I lost it last time, so how do I know please?

It has been a while since I had any 137 GB related problems. I think you can try to defrag you disk and see if any files at the very end are moved.

Were you able to use to windows tools to create the disk partition?

[carlgar]

What brand of disk are you using? I got some WD drives that came with a free controller. However, the controller needed both card bios updates and driver updates before it worked properly beyond 137GB.

[Opus4]

Originally posted by carlgar
Were you able to use to windows tools to create the disk partition?

That brings up yet another point: make sure any 3rd party disk utilities have been updated to handle large drives.

- Andy

[kny3twalker]

the windows update was after SP1 because I download it every time when doing a new install

but it is a windows update that does it

my computer sees all my big drives as well

[mikejaner]

the windows update was after SP1 because I download it every time when doing a new install

It's definately in SP1 because I have an XP CD with SP1 integrated, and it has no problem seeing Disks larger than 137GB. He may be confused with repartitioning once he gets SP1 installed.

[SHS]

137 GB barrier problem with some Operating Systems and Motherboard Bios this has to do with 48 bit Logical Block Addressing (LBA).
1: Make sure you have latest motherboard bios update.
2: Slipstream your 2000/XP CD with latest service pack.
http://www.ntcompatible.com/thread21978-1.html
You may have reinstall the OS on clean format disk.
3: You need to del the partition and start over.
4: You can use build in FDISK on 2000/XP CD by booting up off CD and FDISK it ocen that done hit reset button or exit out of the install and boot back in to windows for there.
Other option Free FDISK http://www.23cc.com/free-fdisk/ or you need Partition Magic 8.

[kny3twalker]

mine may not have SP1 on the disk but I thought it did
the XP Pro I am sure does but my XP Home disk may not (not sure)