http://www.ntfs.com/quest3.htm
Seems the most popular solution, though I've always used Partition Magic.
Printable View
http://www.ntfs.com/quest3.htm
Seems the most popular solution, though I've always used Partition Magic.
wow lol that faq was perfect, it exactly answered my question good look man
Go to the Command Prompt by going to run and typing in CMD
There you type in convert followed by the usage listed below:
CONVERT volume /FS:NTFS [/V] [/CvtArea:filename] [/NoSecurity] [/X]
volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
/FS:NTFS Specifies that the volume is to be converted to NTFS.
/V Specifies that Convert should be run in verbose mode.
/CvtArea:filename
Specifies a contiguous file in the root directory to be
the place holder for NTFS system files.
/NoSecurity Specifies the converted files and directories security
settings to be accessible by everyone.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid.
I.E. if you were converting C drive to NTFS you would type this in:
convert c: /FS:NTFS
Then it will tell you it will run at next reboot, so you exit that then reboot, the rest is automated.
Convert is all vey well for this but ...Quote:
Originally Posted by CrashNBurn79
from hereQuote:
If you use the Convert utility to convert a volume from FAT to NTFS, Windows always uses a 512-byte cluster size. FAT structures are aligned on 512-byte boundaries; a larger cluster size does not allow conversion. Note also that in Microsoft Windows NT 4.0 and earlier, when a partition is formatted under Windows Setup, the partition is first formatted as FAT and then converted to NTFS. Therefore the cluster size is always 512 bytes when a partition is formatted in Setup.
& usually formatting with NTFS results in a cluster size of 4k which is better 'generally', but you have to understand all about, 'slack' & how MFT style fetches work as opposed to FAT sytle ones to get 'why' - the decision over file systems 'bestness' being way beyond most users thoughts or abilities ;) - but believe me when I tell you - doing a clean format instead of using convert will produce much better results ! else all those iddy biddy sectors are gonna give you piss poor performance generally ;)
Also, could any one tell me if there would be stability issues if for instance, I have a 40 gig hard drive with Windows XP Home Edition and am using Fat32. The above posts seem to think that it is not possible and yet this is what I have.
And if you were to convert as the threads above indicate what are the possibilities and risks of loosing all your data?
it's entirely possible. you just can't format a disk from within windows computer management and have a partition over 32GB. it's quite possible using either the manufactures disk or something like partition magic.Quote:
Originally Posted by Martin009
Its worth knowing btw that the MFT in NTFS will use approx 1/8th of your disk space for the 'MFT reserve zone' & if this gets fragmented (as its like all things in NFTS a file itself) you are gonna get poor performance !
To defragment an MFT you need a third party utility or to do a full backup & restore to rebuild a fresh MFT, which with NTFS is advisable periodically as there is no mechanism for the MFT to shrink within xp/2000 (well any NTFS based o/s) & this is definately a weakness (think about your average home users installing & de-installing - I found an MFT yesterday with 300,000+ entries in it using 35% of the disk !) & MS need to fix up defrag so it can defrag this important file & rebuild it as a maintenance operation, without the poor old user having to pay for it !
ATM I use Diskeeper and it defrags the MFT as well as resizes it based on required space.
There's other things (besides diskeeper) that can defragment the MFT itself or use different sizes of MFT reserve zone (there's a registry tweak that you can set anyway) , BUT NOTHING can make your MFT shrink in files used terms (look at the defrag report carefully & you'll see it tells you how many files are present & then compare that to the number of files present on your machine & over time the disparity gets greater & greater ;)) The only practical way I know to sort this out (you want this list as short as possible as its what it has to read every time it wants a file) is to do a full backup & restore - & in 'operating system terms' this is just plain pooh ! :eek2:Quote:
Originally Posted by TechZ
NTFS requires 'management' whatever Billy has to say about matters, & its why I stick with the line of NTFS for anyone who cares about permissions 'really' (i.e. business) & FAT for those that don't (home users) ;)
Well, it's about time you popped in to defend your long time stance.https://forums.windrivers.com/images.../2005/03/1.gifQuote:
Originally Posted by confus-ed
Welcome back -ed. https://forums.windrivers.com/images.../2006/04/1.gif