1 2 Previous Next 16 Replies Latest reply: Jul 17, 2013 12:07 PM by Christopher Murphy Go to original post
  • 15. Re: Inaccessible bootcamp partition for startup disk
    MattP94 Level 1 Level 1 (0 points)

    Yeah, realized it was that old, just figure if it's really hard-coded with apple, they're probably not too concerned about changing it. That said, I'll see what Tuxera has to say about it now.

     

    Here's the mount results.

     

    Matts-iMac:~ mattp$ mount

    /dev/disk0s2 on / (hfs, local, journaled)

    devfs on /dev (devfs, local, nobrowse)

    map -hosts on /net (autofs, nosuid, automounted, nobrowse)

    map auto_home on /home (autofs, automounted, nobrowse)

    /dev/disk0s4 on /Volumes/BOOTCAMP (fusefs_txantfs, local, synchronous)

  • 16. Re: Inaccessible bootcamp partition for startup disk
    Christopher Murphy Level 3 Level 3 (525 points)

    /dev/disk0s4 on /Volumes/BOOTCAMP (fusefs_txantfs, local, synchronous)

     

    The problem is the fs type in mount info is fusefs_txantfs instead of ntfs as it is when Apple's fs kext is being used. I'm curious how Paragon's results compare. Apple lists msdos, ntfs, and udf as valid options. Since fusefs_txantfs isn't on the list, it's not seen as a valid file system.

     

    I don't know that it's possible for Tuxera to do anything about this because they do in fact implement NTFS via FUSE. Whereas Apple could list any *ntfs file system as bootable. But I suspect they'd just say "works as designed".

     

    You could hack the prefpane in a hexeditor and find the two instances of ntfs and substitute fusefs_txantfs intead. And yeah I would consider it somewhat catestraphic because a.) it's a regression over default behavior and b.) it obviates setting Windows for default booting. The present behavior means you have to use option at boot every time you want to boot windows.

1 2 Previous Next