• Welcome to Valhalla Legends Archive.
 

XP on Fat32

Started by Bsd, December 26, 2003, 09:35 PM

Previous topic - Next topic

Bsd

Eh, long story short. Corrupted a Windows XP drive, had a Win 98 drive I upgraded to XP. Didn't change file system on install. I've heard that running XP on a Fat32 is just a crash and burn waiting to happen. Thoughts on this?

Thing

WTF are you doing running XP?  I am so ashamed of you BSD.
Nevertheless, you require POD Pro.  It a real pantie dropper.
That sucking sound you hear is my bandwidth.

Skywing

FAT32 doesn't have journalling or other similar crash-recovery systems like most modern filesystems (including NTFS) do.  No idea whether this contributed directly to your problem, however.

Stealth

#3
Both of my computers run XP on FAT32 -- one because it's a 4-year-old Dell box that originally had 98SE on it, and the other because I dual boot Red Hat 9 -- Linux NTFS drivers are read-only at this stage. They run fine, although the filesystem needs to be checked when the computers are shut down improperly, like the Scandisk of yore only with more of a pastelly-blue color to it. So, from my end, FAT32 hasn't caused any problems to date -- both PCs have been running that setup for a year plus now.
- Stealth
Author of StealthBot

Raven

My XP Pro runs on FAT32 as well and I can't recall ever having problems with it (I've had the occassional lockup on a certain application, but I attribute that mostly to possible memory leaks).

Skywing

#5
Quote from: Stealth on December 27, 2003, 04:37 AM
Both of my computers run XP on FAT32 -- one because it's a 4-year-old Dell box that originally had 98SE on it, and the other because I dual boot Red Hat 9 -- Linux NTFS drivers are read-only at this stage. They run fine, although the filesystem needs to be checked when the computers are shut down improperly, like the Scandisk of yore only with more of a pastelly-blue color to it. So, from my end, FAT32 hasn't caused any problems to date -- both PCs have been running that setup for a year plus now.
You're a bit out of date.  You can use Captive NTFS (based off of ReactOS) for full, stable read/write NTFS capability on Unix systems.

Bsd

Eeep, Skywing talking Unix.. Well I'll be...

Raven

Quote from: Bsd on December 27, 2003, 12:31 PM
Eeep, Skywing talking Unix.. Well I'll be...

What's so unusual about that?

Stealth

Quote from: Skywing on December 27, 2003, 12:05 PM
Quote from: Stealth on December 27, 2003, 04:37 AM
Both of my computers run XP on FAT32 -- one because it's a 4-year-old Dell box that originally had 98SE on it, and the other because I dual boot Red Hat 9 -- Linux NTFS drivers are read-only at this stage. They run fine, although the filesystem needs to be checked when the computers are shut down improperly, like the Scandisk of yore only with more of a pastelly-blue color to it. So, from my end, FAT32 hasn't caused any problems to date -- both PCs have been running that setup for a year plus now.
You're a bit out of date.  You can use Captive NTFS (based off of ReactOS) for full, stable read/write NTFS capability on Unix systems.

Impressive.. thank you, Skywing.
- Stealth
Author of StealthBot

vile

For Unix-like systems use ReiserFS or ext3...

Skywing

#10
Quote from: vile on December 28, 2003, 03:23 AM
For Unix-like systems use ReiserFS or ext3...
You probably wouldn't want to try and boot Windows from ReiserFS or ext3 (even if you could, the security models are incompatible, so it would be at the expense of file system security controls) - this is where NTFS support on Unix comes in handy.