Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Work around a NTFS-3G/Boot Camp/Startup Disk issue System
I've recently discovered the NTFS-3G/MacFuse plugin that allows you to both read and write to NTFS disks. This was a great joy, as I was able to use it along with this hint to resize and restore a big windows partition.

However, as others have found, it is not possible to select your NTFS Windows partition as a startup disk. One workaround is to simply make the partition non-writable, as described in this hint, but that defeats the purpose.

Below is an AppleScript cobbled together from bits and pieces on the internet that works around the problem. Note that you have to change the first two lines to match your system.

The first item, Untitiled has to be the name of the NTFS disk as it appears on your desktop. The second item is the firmware address of the disk. To find this, open a terminal window and type diskutil list, then press Return. For me, this gives:
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *298.1 Gi   disk0
   1:                        EFI                         200.0 Mi   disk0s1
   2:                  Apple_HFS Macintosh HD            216.9 Gi   disk0s2
   3:       Microsoft Basic Data                         216.9 Gi   disk0s3
The bit I want is the NTFS volume, which for me is disk0s3. Here then is the script: Extra bonus! I like to use sudo so much that I set up my /etc/sudoers file so that I don't need to use a password. If you do this, then the script becomes simpler to use: [robg adds: I haven't tested this one...]
  • Currently 1.38 / 5
  You rated: 2 / 5 (8 votes cast)

Work around a NTFS-3G/Boot Camp/Startup Disk issue | 6 comments | Create New Account
Click here to return to the 'Work around a NTFS-3G/Boot Camp/Startup Disk issue' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Work around a NTFS-3G/Boot Camp/Startup Disk issue
Authored by: johnners on Jan 23, '08 11:11:22AM

I wouldn't normally mention a typo, but if people are copying and pasting they may not realise, Untitled is spelled wrong in the first paragraph.

This sounds like a very useful feature. Hopefully this will mean being able to write website changes to a folder on my windows partition. Just makes testing across browsers that little easier!



[ Reply to This | # ]
Work around a NTFS-3G/Boot Camp/Startup Disk issue
Authored by: johnners on Jan 23, '08 11:12:32AM

How ironic. I meant 4th paragraph...!

[ Reply to This | # ]
Work around a NTFS-3G/Boot Camp/Startup Disk issue
Authored by: soopahfly on Jan 23, '08 02:58:38PM
Easier Method: Use rEfit as boot manager, this will still allow you to simply select the NTFS Volume at boot time, no matter what. And more good stuff, but check it out yourself:


[ Reply to This | # ]

Here's my script...
Authored by: a1291762 on Jan 24, '08 04:09:36AM
Here's the script I've been using to boot Windows since shortly after I installed Boot Camp...


if [ "$(id -u)" != 0 ]; then
    # need root privs
    exec sudo $0 "$@"

# snip the bit where it cranks up the fans (because I use Windows for games and the machine gets hot without the fans cranked up)

# boot into Windows for the next boot only, completely bypassing rEFIt
bless --mount /Volumes/Windows --legacy --setBoot --nextonly

# clean reboot (equivalent to doing Apple -> Restart)
# doesn't kill apps like 'shutdown' does
osascript -e 'delay 1
tell application "System Events" to restart' &
It's just a .command file sitting on my desktop. I click it, enter my pasword, press enter twice (once for fans, once for reboot) then walk away while it reboots.

I have rEFIt installed but I prefer this because I hate waiting for the machine to get to the rEFIt prompt after hitting "Restart" and the Startup Disk pref is a permanent setting while I generally want to boot into Windows only once.

Granted I don't currently have NTFS-3G active but I do have it installed and I don't recall any problems with this method while it was activated. I'm also on 10.4 if that makes a difference.

[ Reply to This | # ]

Here's my script... (here's the fans part)
Authored by: a1291762 on Jan 24, '08 04:19:35AM
Ok... in case someone asks, here's how I crank my fans.

    killall FanControlDaemon
    sleep 1
    /usr/local/bin/smc -k F0Mn -w 5dc0
    /usr/local/bin/smc -k F1Mn -w 5dc0

FanControlDaemon is the process used by Fan Control. You need to stop it or it might change the fan speed before you restart.

smc lets you modify SMC values (it's literally the first version of the low-level tool that some awesome hacker released). The SMC tool (or code based on it's principles is what powers all of the fan control apps you can get now). There's 2 calls to smc because my MBP has 2 fans. They're set to 6000 RPM - the max for my machine.

This is something I setup before the fan control apps existed which is why it uses this low-level tool. I'm also on a MBP rev 1, newer machines may not like these values.

[ Reply to This | # ]

Work around a NTFS-3G/Boot Camp/Startup Disk issue
Authored by: mojo-ike on Jun 24, '10 06:40:49AM

i did lots of looking and found lots of discussions with no solutions. i had a problem with the bootcamp (and macos) not showing up in the startup disk control panel and bootcamp setup assistant yelling at me. sure, i could hold down the option key at startup and choose mac or windows, or use BootChamp ( to boot into windows. the problem was with the Partition Map Scheme for the entire disk. it needs to be "GUID Partition Table" rather than MBR (or Apple). i didnt want to reformat the entire drive to fix the problem and then restore the mac and windows data, so i used iPartition ( it converted the partition scheme and everything now works as it should.

[ Reply to This | # ]