In Don Schmidt <
[email protected]> typed:
Not that I know of, Don, but perhaps someone else has a
suggestion.
You could try using something like BING (
www.bootitng.com) to first
image off the volume for safety, then nudge the size and/or position
and see if that converts the cluster size.
I'm not yet a fan of NTFS for use ouside of such excellent backup
management that the "live" HD contents can be considered disposable,
as the maintenance tools still suck. So I'm still using FATxx
instead... and I had to laugh, when good old F-Prot for DOS caught a
rootkit on a Win2000-on-FATxx system in the first minute of formal
scanning. I wonder how much fun we'd have had on NTFS ;-)
However, if I were to use NTFS for C:, I'd rather install the OS onto
NTFS, than install onto FATxx and then convert to NTFS. This isn't
just because of the 512-byte cluster trap - more on that later - but
because the installation of the OS can't assign appropriate
permissions to files and dirs if the initial file system is FATxx. So
when you convert to NTFS, you get "flat" open permissions right across
the installation, as you had with FATxx.
I use BING to create partitions and logical volumes, because one of
the things it lets you do is create FATxx volumes that are aligned in
such a way that should you later convert to NTFS, you won't get the
512-byte cluster problem. So although I still build with FATxx
instead of NTFS, the volumes I create are "NTFS-ready"
BTW: How big a deal is the "flat permissions" thing. when XP is
installed on FATxx and then converted to NTFS? Does doing a repair
install assert the proper permissions? If so, is the benefit worth
the risks of falling back to unpatched status, etc.? Is there some
other way to assign the correct permissions?
-------------------- ----- ---- --- -- - - - -
Tip Of The Day:
To disable the 'Tip of the Day' feature...
