160GB driver seen as 120GB in Windows 2000

  • Thread starter Thread starter V-man
  • Start date Start date
V

V-man

Hi,

I assembled a friend's system.
It is a P4 2.8GHz Northwood on a EPOX 4PDA5+, Intel 865PE chipset
(www.epox.com)

The HDD is a Maxtor IDE, ATA133, 160GB, 8MB cache

The BIOS recognizes everything. I was installing Win2000 and when it
asked me to partition and format the drive, it only made 133GB
available.

So I went ahead and paritioned and formatted with NTFS anyway.

When installation was finished, I looked a the drive manager, and
still, it could only see 133GB on the drive.

I installed SP4, still it only sees 133GB.

Does it need some special drivers, or maybe Win2000 has a limit with
it's NTFS system?

TIA
 
V-man said:
Hi,

I assembled a friend's system.
It is a P4 2.8GHz Northwood on a EPOX 4PDA5+, Intel 865PE chipset
(www.epox.com)

The HDD is a Maxtor IDE, ATA133, 160GB, 8MB cache

The BIOS recognizes everything. I was installing Win2000 and when it
asked me to partition and format the drive, it only made 133GB
available.

So I went ahead and paritioned and formatted with NTFS anyway.

When installation was finished, I looked a the drive manager, and
still, it could only see 133GB on the drive.

I installed SP4, still it only sees 133GB.

Does it need some special drivers, or maybe Win2000 has a limit with
it's NTFS system?

TIA
Click to expand...

I'm also installing a large maxtor disk currently and deal is that under XP
(not sure about win2000) you need at least SP1, and preferably the latest SP,
adn then you have to install maxtor large drive support:

http://www.maxtor.com/en/support/downloads/big_drive_enabler.htm

.... or else your drive will appear to work, but will corrupt data after
137gigs. (aargh I don't like the sound of that!)

I'm posting a question about this very thing, check out my other post....

alex
 
V-man said:
Hi,

I assembled a friend's system.
It is a P4 2.8GHz Northwood on a EPOX 4PDA5+, Intel 865PE chipset
(www.epox.com)

The HDD is a Maxtor IDE, ATA133, 160GB, 8MB cache

The BIOS recognizes everything. I was installing Win2000 and when it
asked me to partition and format the drive, it only made 133GB
available.

So I went ahead and paritioned and formatted with NTFS anyway.

When installation was finished, I looked a the drive manager, and
still, it could only see 133GB on the drive.

I installed SP4, still it only sees 133GB.

Does it need some special drivers, or maybe Win2000 has a limit with
it's NTFS system?

TIA
Click to expand...

p.s. also:
download the maxblast 3 software from the maxtor site. Get the iso, burn it to
a cd and boot from that cd. Go through the palava about setting up your disk
for windows xp. It's worth taking care to get this right!

alex
 
Hi,

I assembled a friend's system.
It is a P4 2.8GHz Northwood on a EPOX 4PDA5+, Intel 865PE chipset
(www.epox.com)

The HDD is a Maxtor IDE, ATA133, 160GB, 8MB cache

The BIOS recognizes everything. I was installing Win2000 and when it
asked me to partition and format the drive, it only made 133GB
available.

So I went ahead and paritioned and formatted with NTFS anyway.

When installation was finished, I looked a the drive manager, and
still, it could only see 133GB on the drive.

I installed SP4, still it only sees 133GB.
Click to expand...

That's because "it" is looking at the partition that you created.
Installing SP4 does NOT change the size of existing partitions. What
it does is allow the operating system to access drive space past the
137GB boundary. Run the Disk Management program and look at the drive
space. It should show the existing 133GB partition plus unallocated
drive space following the existing partition. The Disk Management
program allows you to create a partition and logical drive in this
unallocated drive space. However if you want the existing 133GB
partition to occupy the entire drive, you have to use third party
software such as Partition Magic to expand it.
 
That's because "it" is looking at the partition that you created.
Installing SP4 does NOT change the size of existing partitions. What
it does is allow the operating system to access drive space past the
137GB boundary. Run the Disk Management program and look at the drive
space. It should show the existing 133GB partition plus unallocated
drive space following the existing partition. The Disk Management
program allows you to create a partition and logical drive in this
unallocated drive space. However if you want the existing 133GB
partition to occupy the entire drive, you have to use third party
software such as Partition Magic to expand it.
Click to expand...

I realize that. I installed SP4 and then rebooted and took a second
look at Disk Management, but there was no new unallocated space.

Maybe I will try to delete the 100MB partition and see if the free
space magically apears bigger.

I made a 20GB, 10GB, 100GB partition on the drive.

I will check out Maxtor site as well.
 
I realize that. I installed SP4 and then rebooted and took a second
look at Disk Management, but there was no new unallocated space.

Maybe I will try to delete the 100MB partition and see if the free
space magically apears bigger.
Click to expand...

You have to remove the extended partition and recreate it.
 
I realize that. I installed SP4 and then rebooted and took a second
look at Disk Management, but there was no new unallocated space.
Click to expand...

Actually the problem is:

You must enable the support in the Windows registry by adding or
changing the EnableBigLba registry value to 1 in the following
registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters

See <http://support.microsoft.com/default.aspx?scid=kb;[LN];305098>.

If EnableBigLba is missing or set to 0, Disk Management will not show
disk space past 137GB.
 
Actually the problem is:
You must enable the support in the Windows registry by adding or
changing the EnableBigLba registry value to 1 in the following
registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters

See <http://support.microsoft.com/default.aspx?scid=kb;[LN];305098>.

If EnableBigLba is missing or set to 0, Disk Management will not show
disk space past 137GB.
Click to expand...

I'm assuming this is what MaxBlast does but thanks for that link since
it gives more info than the page for WinXP.

So previous LBA mode was 28 bit, but how does this translate to a
maximum of 137GB? How can I calculate it?

The new LBA 48 bit, but they don't mention the new barrier. How to
compute it?

PS: I will try all this this weekend when I go to my friends house. At
least he doesn't have anything important on his machine yet. I'll let
you know how it went.
 
Actually the problem is:

You must enable the support in the Windows registry by adding or
changing the EnableBigLba registry value to 1 in the following
registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters

See <http://support.microsoft.com/default.aspx?scid=kb;[LN];305098>.

If EnableBigLba is missing or set to 0, Disk Management will not show
disk space past 137GB.
Click to expand...

I'm assuming this is what MaxBlast does but thanks for that link since
it gives more info than the page for WinXP.

So previous LBA mode was 28 bit, but how does this translate to a
maximum of 137GB? How can I calculate it?
Click to expand...

It's 2^28 * 512 bytes per data block
 
Back
Top