At the command prompt, the unit of capacity is the Gigabyte. In Explorer it is the Gibibyte. Sometimes Gigabyte is used interchangeably for both units. In such cases the context determines the meaning.
You are wrong and need to refresh your math calculation.
The WD Data Lifeguard Diagnostic tool seems to have misled you with wrong info and conceptual formula.> The Windows command prompt is reporting 459 GB free space, not 493 GB.
There is no difference whether you check it from command line, computer management or Windows explorer.> The command line never recognizes 493 GB.
The command line reports 493,439,340,544 bytes free (which is 459 GB)> 493,439,340,544 bytes is 459 GB, not 493 GB> 493,439,340,544 bytes free = 493,439,340,544 / (1024*1024*1024) GB free = 459.55 GB> * * *
wd123 wrote:
Command line CLEARY RECOGNIZES that there are 493 GB of FREE SPACE !!!
Does that mean if i copy files using command prompt, i can use up the full capacity?
Here’s the different capacity report
Local Disk Properties
Capacity: 500.11 GB Free Space: 493.45 GB
But it is “rounded up” to
Capacity: 465 GB Free Space: 459 GB
Computer Management
Capacity 465.76 GB Free Space: 459.55 GB
Western Digital Data Lifeguard Diagnostic
Capacity: 500.11 GB Free Space: 493.45 GB
Bios info
Capacity: 500 GB
Command Prompt
Capacity: 500 GB Free Space: 493 GB
Clearly Windows XP is able to see the correct capacity under command prompt.
But for some reason, it reports the wrong capacity under windows explorer.