Re: Seagate 400GB drive reduced to 128GB after WinXP reinstall




"Danny" <Danny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C1A614DA-9663-4DED-BF03-A3D53942A569@xxxxxxxxxxxxxxxx
I installed a 400GB drive as a secondary drive on a WinXP SP2 system as a
single 372GB NTFS partition that I used as backup storage. I later
reinstalled XP, but did not disconnect the 400GB drive before the new
installation. XP recognized the 400GB drive as a single 128GB partition.
Even after installing SP2, I could not get the full capacity of the drive
back.

Since that time I have read this discussion group and have tried all of
the
things that I have read but still have the problem. If everyone will bear
with me, I would like to go through everything again to make sure I am not
missing anything.

Here are things that I have done. I have slipstreamed a disk with SP2 and
my XP original disk, installing this on a newly NTFS partitioned 80GB
drive,
then installed the 400GB drive as a second storage drive, used Seagate
DiscWizard for Windows to partition the drive with one NTFS partition
(also
tried multiple NTFS partitions). XP still said the drive was 128 GB. I
have
a ASUA A7V133 motherboard with upgrade BIOS 1010B. The motherboard has
Primary IDE, Secondary IDE, Primary ATA100, Secondary ATA100 connectors.
I
have a CD ROM connected to the Primary IDE channel, nothing connected to
the
Secondary IDE channel, Western Digital 80GB drive on the Primary ATA100
channel, and on the Secondary ATA100 channel a Maxtor 27GB drive was the
master and the Seagate 400GB drive was the slave drive (I have also tried
changing the positions of the drives to no avail). I had XP SP2 installed
on
the 80GB and 27GB drives and could boot from either one (this
configuration
worked fine until the reinstallation of XP).

When I boot the 80GB, 27GB, 400GB system, during the BIOS screens, I see
D0
as 80GB, D1 is blank, D2 is 27GB, D3 is 372GB.
Seagate DiscWizard for Windows sees the full size of the drive and all
NTFS
partitions.
I do not have the 400GB drive jumpered for 128GB operation.
I have deleted the IDE drivers and reinstalled as mentioned in one thread.
I have deleted the motherboard Promise IDE controller driver and
reinstalled.
I have tried using XP Disk Management to reformat the drive as mentioned
also.
I have erased the 400 GB drive using a DiscWizard boot floppy, then
connected the 400GB drive to a XP SP2 system, drive doesn't appear in
Explorer, gone to Disk Management, Initialized disk, formated disk, disk
is
still shown to be 128GB.

I have now started from square one. I installed XP from my original disk
onto the 400GB drive attached to the Primary ATA100 channel. The BIOS
screens show the drive on D0 as 372GB. Partitioned drive as 128GB NTFS
partition - only choice I had with original XP installation disk. I have
installed all of the recommended updates, including SP2, from the Windows
Update website. I still only see a 128GB partition in the Disk Management
window even though one thread said that after installing SP2, I should be
able to right click on the available space on the drive and make new
partitions.

Does anyone know where I can look in WinXP SP2, I can look to see what is
going on? I have looked in the registry for the EnableBigLba value.
There
is no HKEY_LOCAL_MACHINE entry for it, but I believe that somewhere in the
discussions I have read that it is not necessary in SP2. I appreciate
anyone's help.


Danny:
I assume you know that there are two - and only two - requirements for the
XP OS to recognize the full capacity of large-capacity disks, i.e., disks >
137 GB (approx 128 GB binary)...
1. The motherboard's BIOS must support large-capacity disks; and
2. The XP installation CD must contain SP1 and/or SP2 at the time the OS is
installed and the large-capacity disk is present in the system.

That's it. Those two requirements.

From what you've indicated it appears your ASUS motherboard does support
large-capacity disks.

You say you installed XP from your "original disk" when that 400 GB HDD was
connected. It appears from your description of events that the XP
installation CD you used at that time did *not* include either SP1 or SP2.
Is that right? If so, that would account for the fact that only 128 GB of
that disk was originally recognized. When you later installed SP2
(presumably) the full capacity of that HDD (approx 372 GB) would be
recognized, however, the disk space above the 128 GB originally detected
would (or should) be reflected as "unallocated space" in Disk Management;
disk space that you can partition & format.

Are you indicating that Disk Management does not show that "unallocated
space"? Should that be the case - you're sure of that - what I would suggest
is to use Disk Management to delete the present 128 GB partition, reboot the
machine and using DM (that hopefully now reflects the full capacity of that
disk) partition & format the 400 GB HDD as you please. All this presupposes
that there's either no data on that 400 GB HDD or if so, any data that you
need. And again, it assumes your BIOS supports large-capacity disks and your
XP OS contains SP1 and/or SP2.
Anna


.



Relevant Pages

  • Re: Dual Boot Instructions
    ... the PHYSICAL DISK number, ... Partition and Boot Volume as well as other things. ... You should, at any one time, see ONE System Partition and ONE Boot Volume - ... for the typical two floppy drives and assigning Drive C: ...
    (microsoft.public.windows.vista.hardware_devices)
  • Re: Boot Problem
    ... Right mouse click the dest disk> Advanced> Edit ... but it should eventually boot to Windows. ... I see a lot of posts in here about the ability of Acronis to clone drives. ... I have managed to successfully copy by DELETING partition, ...
    (microsoft.public.windowsxp.hardware)
  • Re: Dual Boot Instructions
    ... OS on a separate partition. ... the PHYSICAL DISK number, ... You should, at any one time, see ONE System Partition and ONE Boot ... The name stuck when we added hard disk drives, ...
    (microsoft.public.windows.vista.hardware_devices)
  • Re: A Dual-boot question; I thought C was always the partition with the running OS
    ... The Server 2003 will then call its partion "C:" Local Disk. ... When Server 2003 starts up, it will call itself "C:" and it will call the WinXP partition "E:", but again, who cares? ... The OS then assigns drive letters to the first primary partition recognized on each successive hard disk. ... Because they're on separate hard drives, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Dual Boot Instructions
    ... If "drive" means a single partition or logical drive, then the negatives you've heard are very true. ... But if "drive" means a physical hard disk drive, then I'm in big trouble because I have SIX versions of Windows installed on my 1 TB Disk 1, my second HDD! ... The name stuck when we added hard disk drives, ...
    (microsoft.public.windows.vista.hardware_devices)