iMac's Mac OS X Snow Leopard supports ExFAT


Recommended Posts

You dont have the kext. Only the latest iMac's shipped with the kext. 10.6.5 will ship with the kext.

Oh, I see.

But that?s pretty strange that there?s two versions of 10.6.4 in the wild ... I thought Apple would be the type of company to say "let?s simply things, let?s just release it alone or along with 10.6.5 when it?s done or 10.6.5 right away".

I don?t think this format is going to change my world though, for now, but it?s good to see Apple rolling out the driver to support it.

It?d be nicer to see a new file system in the next iteration of OS X. Really small files are really killing my iMac :p I?m currently developing a website and last time I moved it into a new directory, it took like 2 minutes and it?s just 10MB lol.

Small files are automatically defragmented by Mac OS X.

Yes. You can format every drive as exFAT.

Yeah, forgot about the automatic defragmentation. I guess this explains it, but I’ve read back in the time of the upcoming of ZFS that HFS+ wasn’t good with smaller files.

Every drive? Even my main HD where OS X is stored? :p

I never really understood why Apple and Microsoft couldn't ally and make one unique File System to beat them all. Or maybe the International Standards Organization should make one and obligate people to use it, but I guess it doesn't work like that in real life.

This whole thing is bothering me because it's a pure technicality, it should be transparent to the user.

But I believe it’s not a good idea to install OS X in that... or the installation process will simply reformat it under HFS+...

You can't install Mac OS X on a non-HFS+ drive. That doesn't change the fact though that technically there's nothing preventing you from formatting your Macintosh HD or any other internal drive you might have as exFAT.

Recap: Disk Utility allows you to format any drive as exFAT. It isn't limited to SDHC cards only.

Yeah, forgot about the automatic defragmentation. I guess this explains it, but I?ve read back in the time of the upcoming of ZFS that HFS+ wasn?t good with smaller files.

ZFS main problem is that it requires at least a 64bit CPU along with minimum 4GB of memory or otherwise the whole experience is very painful to say the least.

I never really understood why Apple and Microsoft couldn't ally and make one unique File System to beat them all. Or maybe the International Standards Organization should make one and obligate people to use it, but I guess it doesn't work like that in real life. This whole thing is bothering me because it's a pure technicality, it should be transparent to the user.

I can understand having operating system specific file systems given the value added perspective of integration between the OS and the underlying file system in the internal hard disk but there is no reason why there can't be a patent and royalty free file system to make life easier when transferring files between different machines.

All of the major operating systems support installing pluggable file systems, so making up a brand new file system and having R/W support under Linux/Windows/OS X isn't very hard. Of course, it's never perfect, Windows only supports auto-mounting if the filesystem is a built in type, installed filesystems need to be manually mounted and given a drive letter.

I used to use EXT3 on my external hard drive when I was dual booting Linux and Windows. To do it properly I had to edit the file system header to report itself as NTFS so Windows would do something with it, while Linux just ignored the type and mounted it properly.

All of the major operating systems support installing pluggable file systems, so making up a brand new file system and having R/W support under Linux/Windows/OS X isn't very hard. Of course, it's never perfect, Windows only supports auto-mounting if the filesystem is a built in type, installed filesystems need to be manually mounted and given a drive letter.

I used to use EXT3 on my external hard drive when I was dual booting Linux and Windows. To do it properly I had to edit the file system header to report itself as NTFS so Windows would do something with it, while Linux just ignored the type and mounted it properly.

Would that kind of spoofing work for a scenario like plugging a USB flash drive into a PS3? It would be handy to get the PS3 to be able to read different file systems rather than just FAT32, so if I just tried to get it to tell the PS3 it's FAT32, would that be sufficient? I guess the real question is, when you report a EXT3 drive to Windows as an NTFS does it mount it and read/write to it as if it's NTFS? Because if the PS3 is incapable of reading/writing to anything but FAT32, then simply spoofing probably wouldn't be enough... :(

Would that kind of spoofing work for a scenario like plugging a USB flash drive into a PS3? It would be handy to get the PS3 to be able to read different file systems rather than just FAT32, so if I just tried to get it to tell the PS3 it's FAT32, would that be sufficient? I guess the real question is, when you report a EXT3 drive to Windows as an NTFS does it mount it and read/write to it as if it's NTFS? Because if the PS3 is incapable of reading/writing to anything but FAT32, then simply spoofing probably wouldn't be enough... :(

It wouldn't be enough. He merely spoofed Windows into thinking it was NTFS so the drive would auto-mount. He still had to install EXT3 extensions onto the system for Windows to be able to read the EXT3 filesystem.

Would that kind of spoofing work for a scenario like plugging a USB flash drive into a PS3? It would be handy to get the PS3 to be able to read different file systems rather than just FAT32, so if I just tried to get it to tell the PS3 it's FAT32, would that be sufficient? I guess the real question is, when you report a EXT3 drive to Windows as an NTFS does it mount it and read/write to it as if it's NTFS? Because if the PS3 is incapable of reading/writing to anything but FAT32, then simply spoofing probably wouldn't be enough... :(

Something like that only works because the actual extension for the EXT3 filesystem is there. So unless you would find a way to add exFAT (or whatever) support to the PS3's firmware it wouldn't work.

Edit Elliott beat me to it.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Windows 8 and Vista were far worse. Both of those got marginally better at the very end. Just look at their adoption rates and support life-span. If those versions had as much social media in their time they would have ripped apart unmercifully.
    • I must admit, this is probably the only game at the moment where I can see that $80 price point being ok. The issue will be when other developers think they can get away with it with half of the work.
    • Google Wallet expands TSA PreCheck Touchless ID access to more travellers by Fiza Ali Google has announced that Google Wallet is becoming the first digital wallet to integrate with TSA PreCheck Touchless ID. It is a programme that lets eligible travellers move through participating airport security checkpoints using facial recognition instead of showing a physical ID or boarding pass. While the TSA PreCheck Touchless ID programme has been available for some time, using it hasn't always been straightforward. The programme currently operates at 65 airports across the US, but participation has largely depended on flying with a limited number of airlines. Travellers also had to upload passport information separately through participating carriers. Now, the tech giant's new integration is designed to remove some of those extra steps. With the update rolling out in the coming weeks, travellers with TSA PreCheck membership will be able to enrol in Touchless ID through Google Wallet and use the service with any of the 100 airlines participating in the programme. Rather than repeatedly submitting identification details, users can store a digital ID in Google Wallet and use it to streamline future trips. Setting up the feature is relatively straightforward as well. The process starts with users creating a digital ID in Google Wallet using their passport information. After checking in for a flight and saving a boarding pass to the app, eligible travellers will see a "Get started" option that directs them to the TSA enrolment process. Once users choose to share their ID pass and boarding pass information with the TSA for a specific trip, the agency will verify the enrolment. If approved, a TSA PreCheck Touchless ID indicator will appear on the boarding pass stored in Google Wallet, signalling that the traveller can use designated express Touchless ID lanes at participating airports. As privacy and security are likely to be key considerations for many travellers, Google says users must explicitly opt in before any information is shared with the TSA, and authentication is required through a device PIN, pattern, or biometric verification. The company also notes that digital IDs stored in Google Wallet remain encrypted and are kept on the user's device. For frequent flyers who already use TSA PreCheck, the new integration could remove a few more steps from the airport security process, making travel slightly faster and a little less cumbersome.
    • Even though MS had to sunset the Windows Subsystem for Android, you can apparently use BlueStacks to run Android in Windows now. I haven't tested this yet, so if anyone has any feedback, I'd love to hear it.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      456
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!