• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Which is more stable?

Stiganator

Platinum Member
I have been using HFS on my hackintoshes for about a year now and I haven't had any problems. I recall occasionally getting orphaned files in NTFS. Most of the files I use are used for windows, but I store some pics and music on it too that only get used on the mac side. Right now, I've left my external drive as HFS and on windows when I need data off it, I used HFSExplorer. It would be more convenient to have it NTFS, but I'm more concerned with file system stability. I don't want files to vanish.
 
I would have to say HFS is more stable, but NTFS is pretty darn close. Plus there's always MacFuse/Paragon NTFS and HFSExplorer/MacDrive if you need to swap.
 
Keep in mind that some Mac files (.app, .dmg, .icns, old program resource files) sometimes get wiped when put into NTFS or FAT32. The files will still be there, but there will be no actual data.
 
Keep in mind that some Mac files (.app, .dmg, .icns, old program resource files) sometimes get wiped when put into NTFS or FAT32. The files will still be there, but there will be no actual data.

Um, you'll lose the resource forks if the app copying them doesn't have a way to save them but the files themselves should be fine. And I don't think Apple uses resource forks in anything recent so that shouldn't be an issue any more.
 
I just know from experience that sometimes .app, .dmg, and .icns don't work when tranferred from HFS+ to NTFS and back.
 
Then something else is wrong because there's nothing special at all about dmg images although I can't speak about app or icns files directly.
 
its probably the same.
orphaned files, perhaps a bad sector botched those files. it happens...so it could be a hardware thing. i trust the hardware less than the file system
 
Back
Top