Installing XP -> using fat-32 (not NFTS) I'm using FAT-32, here's why
#1
Posted 31 March 2007 - 09:38 PM
1) Sure, NTFS has file permissions. That's nice in a corporate / lan setting, but for a single user home system, who needs that? Permissions? I don't need no stink'in permissions!
2) I don't care what you say, permissions take more resources to manage, and take a bite out of system performance. Take a look at some hard drive performance measurements - FAT32 always beats NTFS
3) NTFS is more "robust" or fault tolerant. I think that's an urban legend. I've seen lots of grief over messed up NTFS drives and there is no easy third-party solution because NTFS is proprietary to MS. On the other hand, I've never seen a FAT drive that Norton Disk Doctor couldn't fix. And if a FAT-32 is really pooched, then there's always chain reconstruction (Lost and Found, which I had to use - but only once).
4) NTFS is less fragment-prone. Again I say that's an urban legend. Ask any developer with win-2k on his desk just how fragged NTFS can get.
5) If I want low-level access to a FAT32 drive or the files (for any reason) if I boot a dos floppy I can get in and do stuff (replace files, rename or remove, run a dos-level virus scan, etc). Can't do that if the drive is NTFS.
6) 2K/XP can't format a FAT-32 drive larger than 32 gb. Yea, it's always mentioned. So what? What's that got to do with the "fat vs NTFS" argument?
7) FAT is not efficient because of large cluster size. Yea, so use a third-party partition tool and set the FAT-32 cluster size to what-ever you want.
What is the only real, tangible benefit NTFS has over fat-32? It's the max file-size for FAT32 - 4gb vs no practical limit for NTFS.
Well, now that I've vented, I am interested to see if anyone wants to challenge any of those points...
#2
Posted 31 March 2007 - 09:51 PM
* No compression. I avoid NTFS wherever possible.
However NTFSDOS and GetDataBack for NTFS seem to work quite well. Thanks to those NTFS is only a small pile of poo and not a large one.
Edit: NTFS is fine for a data drive but I don't want it for the boot drive.
This post has been edited by severach: 02 April 2007 - 11:46 AM
#3
Posted 31 March 2007 - 10:20 PM
I frequently have files over 4GB. I can use BartPE to run scans even if all partitions are NTFS. The file system doesn't make a difference if the files you attempt to rename or replace are locked by the OS, not file permissions.
I would never use any operating system from the DOS bloodline (DOS - WinME) outside of a virtual machine.
#4
Posted 01 April 2007 - 01:24 AM
4 GB is indeed a very pressing limitation. There is a standard that extends FAT32 by allowing a few more bits for file size. It's called FAT32+. But I have not heard of any practical implementations.
For now I could suggest that you create an NTFS partition for the large files you will be working with. This is what I have done: 3 HDDs, one of them in NTFS.
This post has been edited by j7n: 01 April 2007 - 01:27 AM
#5
Posted 01 April 2007 - 06:28 PM
j7n, on Apr 1 2007, 02:24 AM, said:
4 GB is indeed a very pressing limitation. There is a standard that extends FAT32 by allowing a few more bits for file size. It's called FAT32+. But I have not heard of any practical implementations.
For now I could suggest that you create an NTFS partition for the large files you will be working with. This is what I have done: 3 HDDs, one of them in NTFS.
Cute Kitty!
10-4 on one little partition for those huge files that like an NTFS partition.
I don't need one and don't have one.
For us old DOS addicts, XP was a real POC, that is till I figgered out that I could run XP on a FAT-32 partition and if anything it ran better than on an NTFS part. And the best part of all......with anyones old DOS boot disk, I can boot up my system and access any file on the HD, to get rid of problems, make repairs etc. I don't need no special PE disk or any of that new fangled junk.
I even run Ghost 2003/2005 from boot disks, in DOS mode. With a series of batch files on my boot disk, I can remove all of the junk files from my HD, delete the Pagefile (1.5gigs) and remove all the old Restore points. That saves me about 2 gigs of space in my Ghost Backup Image files. I can even Scandisk my HD from my boot disk.
It was a real kick in the keester when I discovered that Vista will not run on anything but an NTFS partition. So my new Vista machine will never be my main PC. Unless of course I install XP-Pro on it. Actually, I've already set that up on a second HD.
DOS Rules!
Andromeda43
#6
Posted 02 April 2007 - 06:20 AM
Quote
I've Googled up an article a while ago. It claimed that WinVista will refuse to install on a FAT32 partition, but would boot if copied to one manually. The article said you need MacOS and an USB harddisk, but basically you only needed another OS (such as WinXP) and be able to write the boot area. I haven't tested that myself due to lack of and need for a copy of Vista.
#7
Posted 02 April 2007 - 01:35 PM
- Permissions can help if you have to share your computer with friends or guests. This can help stop malware and other baddies from infecting and rendering your computer useless. It is also very useful should you expand to a home network.
- There is no degrading in performance or resources. None whatsoever. In actuality, your disks will read/write about 10 times (or more) faster.
- I have personally repaired drives that have gone bad and had NTFS on them. You can still make backups easily, including drive images. There are tons of tools (including freeware tools) that can help you fix and recover any NTFS errors you encounter. Even the XP cd can help you fix the issues.
- NTFS does not fragment easily at all. Yes, it still fragments. All drives will fragment regardless of what file system you have. FAT32 doesn't pay as much attention to the files and order as NTFS does. There are many benefits from running NTFS that will greatly speed up your computer.
- You can easily replace files in Safe Mode, there are even programs that will automate the process for you. You actually can do everything you want in safe mode. If you're running a boot disk doing a drive scan, use NTFSDOS Pro from Winternals. There's also NTFS4DOS which is freeware found here.
- I've never had a problem formatting a drive, though I always put NTFS on. If there was a customer running FAT on their XP machine, I'd convert it since they complained about how slow it was. Clocking boot time before was four to five minutes (from power on to usability). After was under two.
- FAT is inefficient due to cluster size, speed, lack of security, does not support Unicode, no support for long file names, low fault tolerance, no recoverability and much much more.
Microsoft
Microsoft Expert
NTFS.com
Learn more
#8
Posted 02 April 2007 - 01:42 PM
#9
Posted 04 April 2007 - 01:31 AM
http://www.msfn.org/board/index.php?showto...mp;#entry621042
#10
Posted 05 April 2007 - 03:52 PM
1. Which filesystem to choose for a disk depends on how you'll gonna be using that disk. Small cluster size, for example, would only slow down operations with the disk and provide no benefit, if you only store large multimedia files.
2. There is also no place for Unicode characters in filenames. You cannot possibly expect for every networking protocol or removable disk filesystem you're gonna be using (or software that operates with these disks) to support Unicode. Having special characters in filenames will probably render them inaccessible in future.
3. You might not need security permissions at all.
#11
Posted 08 April 2007 - 02:19 PM
For some further reading, these Wikipedia pages contiain a lot of information - NTFS and FAT32.
It's not just Microsoft that "wants you to believe" that NTFS is better than FAT32. It's the truth.
#12
Posted 08 April 2007 - 03:08 PM
#13
Posted 09 April 2007 - 11:54 AM
Probably the best FAT32 feature of them all is that you can convert from FAT32 to NTFS any time it becomes necessary. You can't go the other way without a reformat.
>FAT32 might be ever so slightly faster than NTFS, but over time, that quickly degrades
Performance degrades in NTFS too and it doesn't "quickly" degrade because of FAT32. I use plenty of full FAT32 drives and they have no performance problems.
>XP's performance with FAT32 should not be taken as indication of the quality of FAT32
XP does not perform any more poorly with FAT32 than with NTFS.
>if you only store large multimedia files
If you store large multimedia files or DVD disk images you'll be using NTFS. FAT32 with the 4GB limit is not even an option.
>There is also no place for Unicode characters in filenames.
I see the claim all over the web that FAT32 doesn't support Unicode but I know that FAT32 stores unicode just fine. I went to a Japanese website in Firefox, copied some text, and saved the web page as that file name and it looks just right. Perhaps you're thinking of the problem of storing non unicode characters then changing the system locale which lame-o NTFS solves by locking the file system to the locale it was originally formatted as. The problem is Windows 2000 and below with atrocious or non existent Unicode support and without an OS that has mostly functional unicode support software unicode support will be just as poor. I could save the web page but it wouldn't launch with a double click. That isn't the fault of FAT32.
>at least 5x faster than Fat32 partitions
More ridiculous claims. An average performance delta greater than 2% is suspect. It takes specially crafted cases to get any more 2% and in some cases FAT32 has the advantage.
>NTFS is better than FAT32. Period.
Speak for yourself. NTFS is not better for everyone.
>Permissions can help if you have to share your computer with friends or guests. This can help stop malware
All I ever see is that permissions have been set on the malware to make it harder to remove. You are living in a dream world if you think that users can run as anything other than Administrator. Maybe Vista will fix this.
>There is no degrading in performance or resources
Neither NTFS nor FAT32 degrades much as they get full until they get to 99%.
>Clocking boot time before was four to five minutes (from power on to usability). After was under two.
You'll need more examples to back up an improvement as large as 10x or more.
http://www.bbspot.com/News/2007/04/google-...ne-storage.html
>You can easily replace files in Safe Mode
Safe mode is nearly useless because there are many locked and secured files and safe mode won't run if the drive is damaged enough. Those limitations are a show stopper so I use DOS instead.
>You actually can do everything you want in safe mode
Can I read the SAM in safe mode? Can I delete any key I want from the registry? I have a problem with Bill Gates telling me what I can and cannot do. FAT32 is one of my secret weapons that says that I can do with my computer what I want and Bill Gates is powerless to stop me. I don't care to run NTFS where Bill Gates has far more control over what I do. FAT32 is like MP3 and NTFS is like WMA. Sooner or later you'll get bitten by WMA and NTFS and will decide that it's not so good any more.
>FAT is inefficient due to cluster size, speed, lack of security, does not support Unicode, no support for long file names, low fault tolerance, no recoverability
FAT32 is efficient due to lack of security.
FAT32 supports Unicode.
FAT32 supports long file names.
FAT32 was the original recoverability. A long time later good recovery tools showed up for NTFS, no thanks to the dimwits at Microsoft who keep the NTFS spec secret. I'll get more interested in NTFS when the specification is released to the public in a timely fashion.
#14
Posted 09 April 2007 - 02:04 PM
severach, on Apr 9 2007, 06:54 PM, said:
FAT32 supports Unicode.
FAT32 supports long file names.
FAT32 was the original recoverability. A long time later good recovery tools showed up for NTFS, no thanks to the dimwits at Microsoft who keep the NTFS spec secret. I'll get more interested in NTFS when the specification is released to the public in a timely fashion.
Excellent post! I agree with most (or all) of your point, and if you let me just add one more thing why FAT32 got badmouthed: The constant running of scandisk on Win9X after reboot, but it was Win9X that crashed, not the FAT itself. I rarely saw that one myself on a well 'cleaned' windows.
GL
#15
Posted 09 April 2007 - 06:00 PM
Quote
I meant files at least 20 MB of length, for example music files in lossless format. Files bigger than 4 GB may be stored split into several parts (like it is on Video DVD). I was trying to point out that not everyone needs small clusters.
#16
Posted 09 April 2007 - 07:45 PM
FAT32 is the same technology as FAT16. In turn, FAT16 is the same technology as FAT12. The only thing that's changed is that they've built on top of FAT12 and extended to support more features, bigger files and larger partitions. So in reality FAT32 is simply technology from 1977 that's been adjusted to fit more recent demands (as of 1996).
FAT32 simply cannot outdo NTFS. As a matter of fact, some of the easy to run into situations of modern computing today simply cannot be achieved with FAT32. Files over 4GB for example or a RAID array of more then 8TB (easily achieveable with modern disks, it would only take 10 x Hitachi 7K1000 in RAID 5).
Performance, reliability, stability and data recovery are all on NTFS's side as well. Simply dismissing those facts because you need special software to be able to do data recovery on NTFS partitions is ignoring the facts and simply pointing a finger at an unrelated issue.
NTFS is the only choice for modern day computing.
#17
Posted 10 April 2007 - 03:39 AM



Help

Back to top









