| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 50395 | 2004-10-19 08:55:00 | 137GB limit in WinXP | Lizard (2409) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 282668 | 2004-10-19 08:55:00 | How does the 137GB HDD limit affect a new computer assembly? For instance, I'm assembling a new computer: put all the various parts together, including shiny new 160GB SATA HDD, fresh copy of WinXP Pro... Does the 137GB limit mean the HDD won't work, or just won't work properly? Would the computer: (a) not recognise the HDD at all? (b) not recognise the extra space above 137GB? If (b), would patching XP with SP1 (and presumably SP2) fix the problem? Ultimately, I want to know if I can go ahead and install my 160GB SATA HDD in a new computer with an original WinXP, then later add SP1 to correct the HDD size issue? Cheers, Lizard |
Lizard (2409) | ||
| 282669 | 2004-10-19 09:35:00 | It's a Microsoft XP thing . Windows will not recognise anything over the 137Gig limit . This only applies to XP without any of the SP's . So if you install with XP (no SP) then you will only get to 137Gig as a partition . After that is ignored as non-existant . I dare say that Partition Magic could enlarge it after the SP2 is installed . If your installation disk is XP with SP1 , then I guess no problem . Haven't tried it with SATA yet myself, so would be great if you could keep us informed? :) |
Pheonix (280) | ||
| 282670 | 2004-10-19 10:04:00 | You can do XP + SP1 + Patch to get 160Gb or XP + SP2 to get 160Gb or XP SP2 slipstream to get 160Gb (recommended) If your motherboard is new it shouldn't need a BIOS update either. Plenty of details about this limit at the M$ site and your hard drive manufacturer. |
alphazulusixeightniner (185) | ||
| 282671 | 2004-10-20 19:34:00 | More information can be found here. (www.seagate.com) | tommy (2826) | ||
| 282672 | 2004-10-21 08:30:00 | I ran into the 137gb limit recently with a 2000 build using a 200gb SATA. I installed SP4 then had to write my own registry key as well to enable it (EnableBigLba). I had already partitioned successfully all the 137gig 2000 could initially see into 2 partitions. After the registry key reboot 2000s own disk manager allowed me to see the rest of the 200gig wipe out the second partition and recreate a bigger one using all available space. Was pretty painless in the end. I had however asked a freind who does mass storage for a living and basically Partitionmagic can handle the job quite nicely too. While finding the fix I came across a great microsoft help file dealing with the same issue on XP, however I cannot remember if you still have to write your own EnableBigLba as well as install SP1-2. You would think though the logical thing would be the SP1-2 would write the registry key in itself. So you should be able to install the 160gb and just make a 10gig Windows partition only then add SPwhatever to XP and get XP to sort the rest out through its own diskmanager. |
John Grieve (367) | ||
| 1 | |||||