8 Krypton

why only 931.51GB but not 1000GB?

Hi ,

yesterday i bought a seagate harddisk that is labelled as 1000GB. Now I have just finished the physical

 

installation of the harddisk and set the BIOS "ON" for the related controller (it is SATA or II I am not sure)

 

, Now I am in the windows of "Disk Management" under "Computer Management"

, before any partition or format

 

but it shows that there is an initialized unknown harddisk that is 931.51GB instead of 1000GB...

 

oh my god... why 931.51GB?? where is that almost 70GB goes? it's too much.. Can I also use that

 

70GB?? or it will be everything alright after my partition and format???

 

By the way, what should I choose? NTFS or FAT or FAT 32?? my current OS (in another harddisk)

 

is NTFS, should I also choose NTFS? what is the difference?? which one is better? 

 

Many thansk!!

 

 

0 Kudos
5 Replies
8 Xenon

Re: why only 931.51GB but not 1000GB?

The 1000 gigs is decimal;  Windows counts in binary.  A binary gig is larger than a decimal gig:

 

1000 * (10^9/2^30) = 930 binary gigs.

 

Nothing is missing.

 

0 Kudos
8 Krypton

Re: why only 931.51GB but not 1000GB?

Here's another way of looking at it.

 

When the hard disk manufacturer sold you a 1000GB hard drive, they were selling you 1,000,000,000,000 bytes. Windows divides this number by what it considers a GB (1073741824) and reports the hard disk size as:

1000000000000 (bytes) / 1073741824 (bytes per GB) = 931 GB

Studio XPS 435T/9000 (His)
Inspiron 1720 (Hers)
Inspiron 530s (Server)

0 Kudos
8 Krypton

Re: why only 931.51GB but not 1000GB?

For a more detailed answer, check this post I made for someone else.

In your case (like keithg2 mentioned)
1,000,000,000,000 / 1,073,741,824 = ~931.3 GiB
Message Edited by Dev Mgr on 10-03-2008 10:53 AM

Member since 2003

0 Kudos
8 Krypton

Re: why only 931.51GB but not 1000GB?

You could open up the drive and check for missing pieces. 😄
0 Kudos
jepal357
1 Copper

RE: why only 931.51GB but not 1000GB?

The simplest answer is that windows uses gibibytes instead of gigabytes

0 Kudos