To answer your question about your 160GB drive… You don’t have a problem w/ your drive or partitioning software my friend. See this is where drive mfg are not in sync w/ the computer industry… And they tend to screw us out of a few bytes b/c of their proprietary nomenclature and definition of the basic term ‘bytes’. The only problem is the larger the drive, the more space you ‘think’ you’ve lost or get cheated out of…
One KB to most of the computer industry is calculated as 1024 bytes. One MB therefore would then be 1,048,576 Bytes, right?
So 160GB would be 160 x 1024^3 (1073741824) or 171,798,691,840 bytes. Well most ALL drive mfg’s (Seagate, WD, Maxtor, and IBM) think of one KB as exactly 1000 bytes, 1 MB as exactly 1,000,000 bytes and 1GB as exactly 1,000,000,000 bytes. So 160GB is really 160 billion “bytes” by their definition of the word, or 160,000,000,000 bytes.
But all versions of Windows calculate all KB, MB and GB by dividing by 1024 instead of 1000. So if you take your 152.7GB reported to you by Windows and your partitioning software, multiplying it by 1024, you get 156364.8 MB. If you then multiply that by 1024 again, you will get 160117555.2 KB …once more by 1024 and you get 163960376524.8 bytes.
So you DO have a 160GB drive by their standards. But really, by normal computing standards you sorta get cheated out of 7838315315.2 bytes, or 7.3GB. But there’s nothing anyone can really do about it b/c the drive mfg’s have been doing this for many years…They are simply not on the same page as the rest of the computer industry. Oh well, Hope I didn’t bust your bubble either too much, but thats the way the ball bounces…
As for which drive is best, I myself generally prefer WD drives b/c of their warranties, support, and overall reliability, at least in my experience anyway. But Maxtors are good drives too and I own 2 of those…In fact I just bought a 120GB Maxtor just last weekend (well actually Windows reports 114GB)…but its performing flawlessly so far.
In conclusion, You don’t need any special software…Your drive is working perfectly under NTFS…Its just the drive mfg does not define a KB as 1024 bytes like the rest of the world. Hope this helps clear things up a bit… Good luck and happy computing! : )