Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
NTFS on Tiger?
- Thread starter LastLine
- Start date
- Sort by reaction score
Tiger can only read NTFS volumes. If you need to use the hard drive on both Mac and Windows machines, I suggest you copy all the data off, reformat it as FAT32 and then copy all the data back onto it 
.
.
LastLine said:
Yes Microsoft chose to make NTFS a closed format, therefore windows XP is the only OS that can read it. This is Microsoft's fault not Apple's.
You could format it for HFS+ then use MacDrive to read it on Windows. MacDrive is not free, though.
Nah windows is my primary computer at the minute so it isn't worth it for that. I'm just pondering it now. I have an old 120gb drive I could use for the mac I guess.Nermal said:
Ah well screw it, it can wait till after the holidays now
LastLine said:
Yes, MacHFS+.... Which, sadly, is their format that *Microsoft* can't even read, let alone write.
If you want to be able to put very large files on it, you must serve the disk off of one computer in its native format, to the other computers. This circumvents the whole issue of filesystems, but you will be stuck with network speed. For instance, you could keep the disc NTFS and put it on a windows computer that serves it up to the Mac. It will be able to write to it in *this* configuration. Or, you can make it MacHFS+ and serve it to Windows off the Mac. The Windows computers will be able to write to it in *that* configuration. Does that make sense?
The only other option is that there might be third-party software that will let Windows manipulate a MacHFS+ partition. I'm not completely sure about that.
LastLine said:
There are lots of possible causes for this... it's an issue a handful of people seem to have seen on iPods. Mine will do this once in a blue moon, but only very rarely. If yours is doing this substantially, the sort of top two calls would be:
1) Make sure that you don't have disk problems: see the procedure here. If you do, you need to get Apple to fix that for you forthwith.
2) You can also try updating the firmware on the iPod or re-writing the current version of the firmware with the latest iPod Updater software, which may already be on your Mac in your Utilities folder. And maybe also try a hard reset.
It's nobodies fault, it's like it for a reason - security.ChrisFromCanada said:
Windows XP is not the only OS read/write it, all of the Windows NT OS's can (Win NT 1 - 5, 2000, XP, 2003...), and so can Linux (write can be a bit buggy, and also illegal).
What does this mean?
http://www.apple.com/support/downloads/macosxupdate1045.html
-using and mounting Windows formatted storage devices ?
NTFS Writing? Really? Can anyone confirm, or wha exactly does that sentence mean?
http://www.apple.com/support/downloads/macosxupdate1045.html
-using and mounting Windows formatted storage devices ?
NTFS Writing? Really? Can anyone confirm, or wha exactly does that sentence mean?
howesey said:
I think it's security too, but in the journal stability sense. I think NTFS makes it hard for non-native platforms to write basically in exactly the same way MacHFS+ does. They're modern disk systems, and they rely on things like journalling for stability, and these systems get very complicated if multiple computers are writing at the same time and nothing is "serving" the disk. For much the same reason that a database needs a server.