🚀 go-pugleaf

>> >> > Was patitioning 160gbmaxtordisk throughmaxtorutility. NTFS
>> >> > formating was getting allowed only when dial reached 34gb mark.
>>
>> >> > Then same size disk was partitioned with size of primary set at 20gb
>> >> > while installing OS.
>>
>> >> > But in the second instance lost something like 10gb disk space.
>>
>> >> > So wonder if for NTFS format of primarypartitiona certain percetage
>> >> > of total size must be alloted in order not to lose any space on the
>> >> > disk.
>>
>> >> I don't exactly follow what you are saying here. An NTFSpartitioncan 
>> >> be
>> >> any size (max = 2^64 = about 18.5 Million TeraBytes). Perhaps 
>> >> themaxtor
>> >> utility has a false minimum limit. What does it suggest to use for 
>> >> 33GB
>> >> as
>> >> Fat32 is (falsly by windows) limited to 32GB, so if NTFS isn't allowed
>> >> until
>> >> you reach 34GB, then 33GB is in "no man's land"!
>>
>> > Untill over 33gb is reached the dial does stays in FAT32 zone only
>> > after that it allows NTFS option.
>>
>> > I am sorry that I could not come back to my queryy earlier.
>>
>> >> The reason you are 'losing' over 10GB is this:
>>
>> >> There is a problem with the term GB - it can be interpreted in 2 ways 
>> >> by
>> >> people with different backgrounds/outlooks. Some follow the 
>> >> mathematical
>> >> definition that Giga means 10^9 (1,000,000,000) and others follow the
>> >> other
>> >> meaning (not sure what the dicipline is called) of Giga which is 2^30
>> >> (1073741824). This second term is sometimes refered to as Gibi (GIga 
>> >> in
>> >> BInary).
>>
>> >> The marketing people atmaxtor(and other drives), use the mathematical
>> >> definition to describe their drive capacities. So your 160GB drive 
>> >> holds
>> >> 160,000,000,000 Bytes (mathematically accurate). Windows reports drive
>> >> sizes
>> >> using the other definition, so to windows your drive holds 160 / 2^30 
>> >> =
>> >> 149GB.
>>
>> >> Strange but true - the only industry or dicipline in the world where
>> >> 160GB =
>> >> 149GB! But this is probably where you are 'losing' over 10GB of space.
>> >> The
>> >> answer is that you aren't losing the space, its just windows reporting
>> >> the
>> >> size wrongly.
>>
>> > On the disk that was partitioned throughmaxtorutility sizes showing
>> > are 32.8gb vs 116gb
>>
>> So that is 0.2gB short of 149gB. So you have not lost any space, its just
>> being reported using the 'other' measuring scale.
>
> I lost some where partition was done not through Maxtor Utility but
> while doing fresh installation of win2kpro. There it was opted 20gb
> and rest. 20gb shows 19.5gb but rest is showing 108gb.

Sounds like a drive size limit with that version of windows. I can't comment 
on Win2000, but the 2 sizes you quote there add up to 127gB, so probably a 
software issue regarding accessing drivers over that size. You should be 
able to use the rest of the drive when you do the disk management in WinXP 
and possible even use a utility to resize the 108gB partition.