Discussion Locked

NT repair disks and large IDE Drives

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have recently started to recieve systems here with hard drives larger than 8.4GB that were normally supported by the NT repair disks. Whenever we try to recover an NT installation using the repair disk lately, we are greeted with a message stating that the drive installed is larger than 1024 cylinders and cannot be repaired. I've looked at a couple of MS Knowledge base posts about this, but they were no help at all. Whats the trick to building an NT repair disk to recover a damaged installation on something bigger than a 8.4 GB drive??

Thanks

mearsg@mdot.state.mi.us

10 replies

by plg6

My first suggestion would be to partition the disk, say 4 gig or so and make it the active partition, use that for the install of NT. Partition the rest of the disk as an extended partition and set up the logical drives accordingly.

by mdot_tech

Thanks for answering

While that would work, its not practical in our environment. We use a ghost image to roll out our machines (We have over 3000 users) With all the CAD and other software we use it would fill up the 4GB partition in a heartbeat. Also depending on the literacy of the user they get confused when software is installed anywhere except the C: drive. We're currently configuring these drives with one large partition and a small 500MB extended partition to hold the page file.

by steby

The Microsoft supplied generic IDE driver (Atapi.sys) may not be fully compatible with drives larger that 8 GB. This issue only affects IDE-based drives 8 GB and larger however Service Pack 4 includes an updated ATAPI.SYS allowing access to disks greater than 8GB.
There are tricks so follow this link carefully:

by mdot_tech

Thank you for answering

Yeah I read the Microsoft Knowledge base article containg that information. We are currently using service pack 6 and have created the three disk repair set using the very instructions you speak of replacing the old atapi.sys file. Still no go..........

Any other ideas???

This discussion is closed to new replies.