There are absolutely no reasons to use FAT32 when you are using a modern OS.
Originally posted by: Netopia
There are absolutely no reasons to use FAT32 when you are using a modern OS.
Actually, I struggle with this one. I prefer NTFS because it is a more stable and robust FS than FAT. OTOH, I've got some servers that I built with a 2 GB Fat16 Boot/System drive and over the last couple of years, on occasion I would install a driver or piece of software (InCD in one case) that the system didn't like and it would simply blue sceen and not let me boot. Because it was FAT, I was able to boot from a floppy and simply remove the offending file. Upon reboot, the OS complained that the file was missing but booted fine, which gave me the oportunity to uninstall the program and get back to a normal stability.
Contrary to that, I've had occasion where something was misbehaved and the boot/system partition was NTFS. In that case (only happen once) I was SOL since I couldn't get at anything. I was able to restore from a ghost and then restore the more recent files from backup, but had it been a workstation instead of a server (no backups), I would have been totally SOL.
Just my thoughts...
Joe
While I doubt that your server(s) were crashing because you were using FAT n0cmonkey is right in that you would really want to use NTFS for ALL modern windows based systems including servers. Why on earth you would want to run your server on a FS that doesnt support ACLs is beyond me.Originally posted by: Netopia
There are absolutely no reasons to use FAT32 when you are using a modern OS.
Actually, I struggle with this one. I prefer NTFS because it is a more stable and robust FS than FAT. OTOH, I've got some servers that I built with a 2 GB Fat16 Boot/System drive and over the last couple of years, on occasion I would install a driver or piece of software (InCD in one case) that the system didn't like and it would simply blue sceen and not let me boot. Because it was FAT, I was able to boot from a floppy and simply remove the offending file. Upon reboot, the OS complained that the file was missing but booted fine, which gave me the oportunity to uninstall the program and get back to a normal stability.
Contrary to that, I've had occasion where something was misbehaved and the boot/system partition was NTFS. In that case (only happen once) I was SOL since I couldn't get at anything. I was able to restore from a ghost and then restore the more recent files from backup, but had it been a workstation instead of a server (no backups), I would have been totally SOL.
Just my thoughts...
Joe
If I understand your statement, I guess my answer would be because there is enough physical security around the boxes in question that I don't have to worry about it. Couple that with the fact that we are talking about servers that have virtually no sensitive data of any kind on them....Why on earth you would want to run your server on a FS that doesnt support ACLs is beyond me.
You know... I looked at that product a couple of years ago... and promptly forgot that it was out there! I would say that doing a FAT->NTFS conversion and buying NTFS4DOS is probably the direction I'll go.NTFS4DOS, there's a write version that doesn't cost too much.
Good deal, than I guess in your case it doesnt really make too much of a differance...The shares themselves are all on NTFS partitions.
Yeah, that's how I saw it. But, as a couple of you have pointed out, NTFS is still better and with the write ability of NTFS4DOS, my only detractor is removed!....I guess in your case it doesnt really make too much of a differance...
I am sure NTFS is a more secure format but I find FAT32 does work quite well on a 40 gig drive.
Yes, it has smaller byte sized spaces for saving info on
That is why you have so much less available space for installing programs and saving data on.
Originally posted by: prosaic
Not knocking the NTFS for DOS utility (Those guys at Sysinternals REALLY know what they're doing.), but it really isn't needed with Windows 2000 and Windows XP if you've got your ducks lined up. When the appropriate policy is applied the recovery console can get you access to anything than NTFSDOS can get for you. Why would people insist on using a DOS recovery diskette when much more powerful tools for recovery are shipped with the OS?
- prosaic
Originally posted by: johnlog
>It's not even that it's more secure, it's more effecient, stable and less fragile. FAT is deprecated, even MS wants you to move on. <<<
Yes, it has smaller byte sized spaces for saving info on. Has less slack space lost. NTFS is more secure in that it puts up a mirror image of the NTFS so if a failure happens it can use the mirror image so you get a feeling of security. That is why you have so much less available space for installing programs and saving data on.
Because they do not know any better. Because they are lazy and do not want to learn something a little newer. Because technology scares them. Because they think they know the best way to do these things, even when the manufacturer tells them differently.
Originally posted by: Netopia
Because they do not know any better. Because they are lazy and do not want to learn something a little newer. Because technology scares them. Because they think they know the best way to do these things, even when the manufacturer tells them differently.
I'm all ears. I'm ready to learn and to move forward! Point me in the direction of where you guys think I should read. BTW... I hope none of you have simply made the ASSumption that I'm using 2000/XP. All of these servers in question are NT4/SP6a and the company isn't in a financial situation to upgrade.... so.... I don't want to be too lazy or stupid, so how do I do the things you speak of with my current setup?
Joe