Your right, you shouldn't hijack the thread. I thought initially that this
was the OP responding again.

You will probably have to either delete the partition and repartition the
drive to get the full size of the drive or partition the remainder of the
space and create another logical drive. (If you have Partition Magic or
similar program you can stretch the original partition to the full size of
the drive.)

Right click MyComputer then Left click Manage|Disk Management and find the
drive in the right bottom window. See if it shows unpartitioned space. If
so you have found the remainder of the drive space.



"Lokki2" <Lokki2@discussions.microsoft.com> wrote in message
news:AB766033-B99E-43B3-BF1E-2D83B7F49E34@microsoft.com...
> Sorry, but I'm really lost!
>
> I've been reading all the posts and still don't know what to do.
>
> I recently installed at WD 250 GB hard drive. The BIOS regognizes it as
> 232gb on the startup, and it's connected to a Promise card. But windows
> only
> shows 128gb
>
> I also have another hard drive that has been attached to that Promise card
> for 2 years, and that drive shows over 137 GB. But for some reason the
> new
> one only registers 128GB in the Disk Manager.
>
> I am running XP SP2.
>
> I've tried using WD's "Data lifeguard tools" and that didnt work......any
> ideas?
>
> sorry to highjack the thread, but this is really bugging me.
>
> "PK" wrote:
>
>> I have PC runnong XP Pro SP2. I have an older externalfirewire HD
>> enclosure
>> that I used as a backup HD. Recently I bought a new HD that is bigger
>> than
>> 137 Gb and for some reason I am unable to get it to work.
>> I formatted it on IDE channel (NTFS) using MaxBlast4 utility. Then I
>> removed
>> it and put it inside the enclosure. Now, "disc management" shows 189 GB
>> of
>> unformatted spave. I am able to change the drive letter, but when I try
>> to
>> format it the process hangs.
>> Also, when I try partition magic(PM) it shows 131 GB of "BADMBR". if I
>> try
>> to run PM while disk manager is running, pm just hangs. My primary HD is
>> 250
>> GB, my atapi.sys file is version 28xx and I am running SP2 so I should
>> not
>> have this problem. CompUsa website informs me that this enclosure does
>> not
>> need any drivers as xp offers native support for IEEE 1394.
>> I am confused what do I do wrong?
>

UPDATE THE CONTROLER CARD!!!

I manually searched out my controler card on-line, downloaded the newest
driver set from Promise and whalla I know have 232 GB of Storage!!!!!!

PK, you were right...the July 7, 2001 driver date was the indication that it
was just the generic windows....it works now!!!! I didn't think it was going
to be this difficult...good luck finding the answer to your problem.

"Lokki2" wrote:

> Sorry, but I'm really lost!
>
> I've been reading all the posts and still don't know what to do.
>
> I recently installed at WD 250 GB hard drive. The BIOS regognizes it as
> 232gb on the startup, and it's connected to a Promise card. But windows only
> shows 128gb
>
> I also have another hard drive that has been attached to that Promise card
> for 2 years, and that drive shows over 137 GB. But for some reason the new
> one only registers 128GB in the Disk Manager.
>
> I am running XP SP2.
>
> I've tried using WD's "Data lifeguard tools" and that didnt work......any
> ideas?
>
> sorry to highjack the thread, but this is really bugging me.
>
> "PK" wrote:
>
> > I have PC runnong XP Pro SP2. I have an older externalfirewire HD enclosure
> > that I used as a backup HD. Recently I bought a new HD that is bigger than
> > 137 Gb and for some reason I am unable to get it to work.
> > I formatted it on IDE channel (NTFS) using MaxBlast4 utility. Then I removed
> > it and put it inside the enclosure. Now, "disc management" shows 189 GB of
> > unformatted spave. I am able to change the drive letter, but when I try to
> > format it the process hangs.
> > Also, when I try partition magic(PM) it shows 131 GB of "BADMBR". if I try
> > to run PM while disk manager is running, pm just hangs. My primary HD is 250
> > GB, my atapi.sys file is version 28xx and I am running SP2 so I should not
> > have this problem. CompUsa website informs me that this enclosure does not
> > need any drivers as xp offers native support for IEEE 1394.
> > I am confused what do I do wrong?