NTFS on 8.3gig hd?

  • Thread starter Thread starter craig
  • Start date Start date
C

craig

Should I convert FAT32 files to NTFS fileson a hard drive with 8.3 gig
memory?

Anything wrong with keeping FAT32 on 8.3gig?

Thanks for ANY & ALL help!!!!!!!!!!!!!
 
NTFS stores data more efficently that FAT or FAT32. This will give
you more storage space on your drive as you put more and more files
onto the system. Further, NTFS allows for more security options than
FAT or FAT32 such as encryption.

If you are comfortable with FAT32 then you don't necessarily have to
change.

Regards,

Clinton R. Fitch III
Partner
C3 Technology
http://www.c3-technology.com


Should I convert FAT32 files to NTFS fileson a hard drive with 8.3 gig
memory?

Anything wrong with keeping FAT32 on 8.3gig?

Thanks for ANY & ALL help!!!!!!!!!!!!!

Clinton Fitch
Editor/Reviews Lead
HPC:Factor & Clinton Fitch (Dot) Com!

http://www.hpcfactor.com
http://www.clintonfitch.com
 
I would recommend changing to NTFS. It performs alot better. You will be able to store more files on your harddrive with NTFS then you can with FAT32.
 
NTFS stores data more efficently that FAT or FAT32. This will give
you more storage space on your drive as you put more and more files
onto the system. Further, NTFS allows for more security options than
FAT or FAT32 such as encryption.

If you are comfortable with FAT32 then you don't necessarily have to
change.

Regards,

Clinton R. Fitch III
Partner
C3 Technology
http://www.c3-technology.com

NTFS gives you the option to turn on compression. You can compress
existing data, and if you set the compression property on a directory
anything you put there will be compressed. Compression is utterly
transparent to your applications. Compress/decompress is done at the
file system level. YMMV as to how must space compression gets
you. I've seen 20:1 compression for ascii numeric data. OTOH TIF image
files compress very little.

I've compressed the entire C drive (C:\ and everything under it) many
times on systems that needed space. This was when we had 2GB disks.
I've never seen NTFS compression screw up.

There is no downside to compression that I can see, except I wouldn't
put a serious database there becuse a record insertion would require
the decompression/recompression of the entire file. The CPU cycles
needed to compress or decompress are offset by the reduction in the
number of blocks that need to be moved from the disk.
 
craig said:
Should I convert FAT32 files to NTFS fileson a hard drive with 8.3 gig
memory?

Why not?
Anything wrong with keeping FAT32 on 8.3gig?

NTFS doesn't force you to run CHKDSK every time you fail shut to XP down
properly, like FAT32 does.
Thanks for ANY & ALL help!!!!!!!!!!!!!

I remember running NTFS on a 200 megabyte drive...
 
Arny Krueger said:
Why not?


NTFS doesn't force you to run CHKDSK every time you fail shut to XP down
properly, like FAT32 does.

Incorrect. CHKDSK can be called to run at system restart on an NTFS volume,
but generally you're in some deep kimchi if that happens.
I remember running NTFS on a 200 megabyte drive...



--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
 
With 8.3G partition, leave it as is unless you need the security features of
NTFS. Doing a conversion to NTFS may result in performance degradation if
the cluster size post conversion is 512B instead of the current 4KB.

--
Walter Clayton - MS MVP(WinXP)
Associate Expert
http://www.microsoft.com/windowsxp/expertzone
Any technology distinguishable from magic is insufficiently advanced.
http://www.dts-l.org
 
Back
Top