Saturday, October 27, 2007

NTFS-3G 1.1004 with ublio patches

After a lot of testing and building I have now decided to release an experimental release of NTFS-3G for Mac OS X with caching support through the ublio user space caching layer. This will be especially relevant for people with USB2 external hard disks, where performance increases of about 1500% can be expected.

This package release can be labeled experimental, which means that it's not verified to be stable, and there may be issues remaining to be solved. If you want a stable release, fetch NTFS-3G 1.1004 Update 2.

Note that caching isn't enabled by default, but needs to be enabled by executing the script "Tools/Enable file system caching.command", which can be found in the disk image.

Before enabling caching, you have to be aware of a few things:
1. When using the caching layer, NOBODY SHOULD EVER REMOVE EXTERNAL DISKS IF NTFS-3G IS STILL RUNNING. You always have to eject the disk properly through the eject button in the Finder or through Disk Utility, or else you risk losing data. (This really applies to all cached file systems, so you should make this a common practice.)
2. Even though NTFS-3G is extremely well tested, the ublio patch is not included in this testing process. Thus you cannot expect the same quality, and even though I have tested the package and found no issues that can be effectively traced to ublio, you should be cautious in an environment with important data. The ublio patch is used frequently in FreeBSD with NTFS-3G.

Download NTFS-3G 1.1004 (Update 4, experimental) (package by catacombae)
Requirements: Mac OS X 10.4, a PowerPC or Intel computer, MacFUSE 0.4.0 installed (currently NOT WORKING with MacFUSE 1.0.0).

Summary of changes for NTFS-3G 1.1004 Update 3:
  • Dramatic performance enhancements by adding caching support through the ublio layer.
  • The ".ntfs-locale" trick should not be needed anymore for most people, as NTFS-3G now defaults to a reasonable locale (en_US.UTF-8).
  • Added scripts for disabling and enabling ublio caching and debug logging.

Summary of changes for NTFS-3G 1.1004 Update 4:
  • Disabled caching by default, so people can choose if they want it enabled or not.
  • Hopefully fixed a bug where some users got their mount points prepended by "-n".

Note: I really need your feedback for this version! If you install it and it doesn't work, don't hesitate to tell me about it by writing a comment or sending me an email (address can be found at my regular site). If it does work, I'd like to hear about that as well, especially if you're on a PowerPC Mac.

The ublio-patched source code for ntfs-3g 1.1004 is available here.
The source code for ntfsprogs 1.13.1 is available here.


VanillaIcee said...

Great work. Any chance a version can be compiled for Leopard (10.5) that puts ntfs-3g.fs under /Library/Filesystems instead of /System/Library/Filesystems?

Jae-wan said...

I have a problem with your package right now. I installed your package in a following way:

1. Installed MacFUSE (now 1.0)
2. Restart
3. Installed your NTFS-3G package (from this blog entry)
4. Restart

Then my USB 2.0 drive mounts correctly and I can see all my files. However, I am unable to copy any of the files to my own Mac hard drive. Also, I get permission denied when I try to copy any stuff to the external drive. How can I fix this?

Erik said...

I don't know what else is required for file systems in Leopard, but in the meantime you could just copy the directory to the right place. If that works, then congratulations (the uninstall package script won't find these new files, so make sure you clean them out yourself if you want to). :>

I was at an Apple reseller yesterday to get a feel of Leopard, and on the demo computers all internal file systems were located in /System/Library/Filesystems like before... So I don't know yet what the fuss is about. I think I'll need to investigate Leopard support on my own.

I will hopefully get Leopard on my computer soon, thanks to Szabolcs Szakacsits, and then I can start looking at all your Leopard-related issues.

Erik said...

This _may_ be a MacFUSE 1.0 related issue. I haven't even had time to install, let alone test the latest MacFUSE incarnation.
Would you please try to downgrade your MacFUSE install to 0.4.0 and check if the problem persists? You can find the old package here:

If the problem is still there, please contact me through my email, which can be found on my regular web site (bottom of the main page):
That way it will be easier to sort things out.

Anonymous said...

Erik wrote:
I was at an Apple reseller yesterday to get a feel of Leopard, and on the demo computers all internal file systems were located in /System/Library/Filesystems like before... So I don't know yet what the fuss is about.

Hi Erik,
I still haven't installed Leopard, but I just checked the BaseSystem.pkg with Pacifist v2.5 update that supports the new Leopard packages. Apple is indeed still using the /System/Library/Filesystems directory (as you saw).

The MacFuse v1.0 Leopard version as per its release note is installing into /Library/Filesystems (I also checked the package with Pacifist). Probably creating that directory as well. I didn't see any reason indicated for this change.

Not sure how this will play out using the standard installer packages. But I assume that both MacFuse and NTFS-3G need to reside in the same "Filesystems" directory be it /System/Library/Filesystems or /Library/Filesystems. So using v1.0 (baring any other problems) would require moving a package, no?

Oliver said...

Just wanted to download the new version but the link seems to be broken :(
Sourcecode download is still working fine.

VanillaIcee said...

Issue is that the location is hardcoded in ntfs-3g to connect to libraries in /System/Library/Filesystems, and I don't have developer tools so I can't run the utility to change the library references nor can I recompile.

thanks for help.

bugeyedmonster said...

Any update on the broken link? I'm busting to try this and see if it speeds up my external disk access. Keep up the good work!

Erik said...

Sorry about the broken link everybody, but I removed the file in panic after experiencing some file corruption on my NTFS volume when running VMWare Fusion VMs from there.

The release can still be downloaded here:

If you want to performance test it, or test it in other ways, please do. Reading should always be safe, writing should be safe mostly. I have stress tested the file system but I can't reproduce this particular issue yet.

I just don't want to make this release official with such a strong suspicion that it contains bugs.

Erik said...

For a more readable form:

VanillaIcee said...

Ok after some exploration: On Leopard filesystems now work from the /Library folder, so fusefs.fs is found in /Library/Filesystems like a good user installable program should be.

To make a compatible version it would have have to link to this version and ideally put in the same directory. Similarly putting links for mount_ntfs-3g and newfs_ntfs-3g in /sbin is not necessary, and it would be better to put those into /usr/local/sbin along with the rest of the command-line utilities.

Appreciate your hard work. Thanks.

Andrew said...

so i installed MacFuse .4 and the latest (update 3) of ntfs-3g .. when i turn on my external drive it sees it in leopard and mounts it but it never appears on the desktop and when i look inside disk utility it comes shows that its mounted but added a -n to the name of the drive (ie .. drive name is Klause .. disk utility shows it as -n Klause) any ideas why its doing that and not letting me access it either in terminal or from finder ??

i have another ntfs partition for my xp install on this comp it also comes up with the -n and not able to see it on desktop nor access it from terminal

Andrew said...

update 4 valid ??? confused why update 2 and 3 are around 1.6mb and then update 4 is only 284k

anyway .. doesn't want to mount the dmg image on my mac :(

i was hoping this version would fix my -n problem

Anonymous said...

Chance to include the detection of the OSX version in the installer?
/Library/Filesystems for OSX 10.5
/System/Library/Filesystems for OSX 10.4?
So you don't need to compile two ntfs-3g versions.

meepmeep said...

I'm using leopard, and i can't mount this file : NTFS-3G_1.1004-u4-experimental-catacombae.dmg, "reason unknow"..

Erik said...

Andrew & meepmeep:

Sorry about that, I ran out of space at my web hosting facility, so the entire file wasn't uploaded. Now it should be there.

Ricky said...

I have a PPC Mac and would like to test the software. I'm currently running Update 2 without any problems but was wondering exactly what issues you had with Update 3/4 that caused you to be a little more hesitant about it. Did it corrupt the entire destination drive or just the destination file? Was the source file damaged? I need to use this to back up some important files using my brother's NTFS formatted USB drive, so I don't want to take a chance. I don't want to "test" it if there is a risk that either the source file or destination drive could be corrupted. If only the destination file was corrupted, I wouldn't have any problems.

Ricky said...

Ok, so I'm pretty impatient. I went ahead and installed Update 4 and was able to transfer my files (huge iMovie bundles) to the USB External drive without any issues. It was about 10x faster than the previous version (Update 2). I was also able to open the files without issue. Thanks!

bugeyedmonster said...

Holy fsck, this thing is FAST.

You have my undying gratitude. Running 10.4.10 on a ppc 1.42G Mini with a Seagate 500G USB2 disk, and getting similar throughput -- with update 4 with caching enabled -- to what I get with HFS+ mounted USB2 disks (HFS+ is about 1.5x the speed, but that's a lot closer than it used to be).

Thank you, thank you, THANK YOU.

VanillaIcee said...

Ok I feel silly. mount_ntfs-3g, newfs_ntfs-3g, and ntfs-3g.util are all scripts. Changing all references to fusefs.fs to be in /Library/Filesystems works, along with changing any other references to /System/Library/Filesystems to the new location in Leopard.

This could probably be included into the scripts, picking /Library if on 10.4 or /Sysem/Library if on 10.5.

one thing I did notice is that PFX and ROOT in the ntfs-3g.util don't seem to be working for the like 205 and 233.

neptune2000 said...

Erik, I can confirm that Update 4 fixes the mount "-n" problem. Now the mount points are "Untitled", "Untitled 1", etc..

I could only load the experimental update 4 with Mac Fuse 0.4.0.

BTW, I noticed that the uninstall batch file leaves some crud around. here it is:

Stuff left in /System/Library/Filesystems:

marco-papas-powerbook58:Filesystems marcopapa$ ls -l ntfs*
total 0
drwxr-xr-x 3 root wheel 102 Oct 28 21:27 Contents

marco-papas-powerbook58:Filesystems marcopapa$ ls -l -r ntfs-3g.fs/Contents
total 0
drwxr-xr-x 3 root wheel 102 Oct 6 22:53 Resources
marco-papas-powerbook58:Filesystems marcopapa$

marco-papas-powerbook58:Filesystems marcopapa$ ls -l -r ntfs-3g.fs/Contents/Resources
total 0
drwxr-xr-x 2 root wheel 68 Oct 28 21:27 English.lproj

Andrew said...

okay .. update 4 i can confirm took out the -n issue and mounts my internal and external ntfs drives

quick question though .. on my leopard install it doesn't display the ntfs mounted drives under Devices in Finder nor on the Desktop .. anyone else have this issue ?

alphatester said...


I did this:

1. Installed MacFUSE (0.4)
2. Restart
3. Installed your NTFS-3G package (from this blog entry)
4. Restart

My volume (a 750 GB Seagate FreeAgent Pro) doesnt mount, but when I go into the Disk Utility I can see it as a folder of some sort which IS mounted (cant be unmounted), and in the list, it has a " 2" trailing the actual volume name given to it in Windows.

OS X automounts and can read the disk by default (i.e. when uninstalling ntfs-3g).

md said...

I have the exact same problem as alphatester.

i use NTFS-3G_1.1004-u4-experimental-catacombae

mount says this
/dev/disk1s1 on /Volumes/disk 3 (fusefs, synchronous)

i can create folders and so on from the terminal but the disk never appear at the desktop. Have i missed something?

Wesley Woo-Duk said...

md, open Finder, go to Preferences > General and check 'Connected servers'.

neptune2000 said...

I turned off debug and turned on caching. I tried a 250,000 files copy which lasted 4 hours between two NTFS disks. It went all the way to the end and then iit popped a "Copy" error with the message "The operation cannot be completed because one or more required items cannot be found. (Error code -43)". Any dea?

Nico said...

Nice .. Ntfs-3g with ublio works for me. I'm using leopard and a usb drive with catching.
I still get errno -36 on 60% of file.
With command line i saw :
cp: /Users/meepmeep/Documents/CV//.DS_Store: could not copy extended attributes to ./.DS_Store: Attribute not found

Any idea of how i can resolve this (without removing all my DS_store file ;) )

thank's for all !

Erik said...

To all Leopard users out there:

Please be a little bit patient. I'm going to the store to buy OS X 10.5 today.
I can't solve any problems that you have with Leopard until I get it running on my machine.

ccfoo said...

I'm having the same issue jae-wan had. I'll try to go back to 0.4 version of macFuse to see if this helps.

neptune2000 said...

>quick question though .. on my leopard install it doesn't display the ntfs mounted drives under Devices in Finder nor on the Desktop .. anyone else have this issue ?

Andrew, this is a "feature". :-) The MacFuUSE wiki tells you why.

Toonman said...

I don't pretend to be a professional by any means on this stuff, but i was playing around tonight here is what i've found.

With 10.5, installing Macfuse 1.0 and ntfs-3g (Update 4) i was able to get the drive mounted, but everytime i went to write to the ntfs drive from the Mac it would say "filename too long".

So scanning through these things here, i figured i'd give it a try.

Macfuse install into /Library/Filesystems, whereas ntfs-3g installs into /System/Library/Filesystems.

I copied ntfs-3g.fs into /Library/Filesystems and also copied fuse.fs into /System/Library/Filesystems.

I can now write to the drive no problems (after a killall Finder).

Just thought i'd try help out.

Toonman said...

Sorry i'm delusional, that didnt fix the issue i was having.

Leave it up to the professionals :)

VanillaIcee said...

Getting this working on Leopard, I noticed quite a few errors in ntfs-3g.util. This is true atleast for the 1.0 version of Leopard macfuse:

1) mount_fusefs is now located in /Library/Filesystems/fusefs.fs/Support/

2) PFX should probably not contain ROOT, as ROOT points to ntfs-3g.fs, unless the command line utilities are moved into the bundle. Without fixing this calls to ntfscat, ntfslabel, and fuse_wait do not work when running mount_ntfs-3g

3) handing mount_ntfs-3g a mount point with a space does not work because it gives ntfs3g volname=firstword secondword instead of volname="firstword secondword"

4) -olocal may want to be used in 10.5 to allow drive to show up in sidebar of finder, otherwise it only shows up under Computer

Erik said...

This one is for Szabolcs Szakacsits:

Thanks to him, I know have a copy of OS X 10.5 in my hand. You should all pay your respect to him for being a good person and a good developer. :>

When I've got it set up correctly, I'll be able to prepare a release for Leopard. Be patient.

Jason said...

Not working well with MacFuse 1.0.
The problem is I can't copy files to an ntfs usb drive in Finder. There's always an error saying I don't have sufficient permissions at the END of each copy and it deletes what has just been copied! However using cp in terminal works fine.

Downgrading MacFuse to 0.4.0 fixed the problem. I'm not sure whose fault it is.

Jason said...

BTW I'm using tiger, 10.4.10

Erik said...


I'm familiar with the issue. It appeared in MacFUSE 0.4.0 when I didn't have the "default_permissions" flag turned on. Maybe in MacFUSE 1.0.0 it wants it to be turned off, or some other flag turned on. I think it will be hard to make a package that will be usable with both versions, but I'll look into it.
In the meantime, use MacFUSE 0.4.0.

Erik said...

Jason: If you want to fiddle with the mount script, open /System/Library/Filesystems/ntfs-3g.fs/ntfs-3g.util and search for the string "default_permissions" and change it to "defer_permissions" or remove the flag to see if it works (if you remove it, be sure to remove the "," that follows).

Jesse said...

Thumbs up for picking this project up, saved my bacon a couple weeks ago. Now that I'm in Leopard I'm sad to see it broken, and the copying over fuse.fs and ntfs3g.fs trick didn't work. Rolling back to MacFuse .4 didn't work either, not that I was expecting much. Best of luck getting things going with the new cat.

ugsasaki said...

You must edit ntfs-3g.util to use MacFUSE 1.0.0 + ntfs-3g 1.0004 Update 4 on Leopard (and Tiger).

1 run and type command.

$ sudo /Applications/ /System/Library/Filesystems/ntfs-3g.fs/ntfs-3g.util

2 find line include "default_permissions".

3 replace it, like below:

local OPTIONS="default_permissions...

local OPTIONS="local,auto_xattr,defer_permissions"

4 save it and re-mount ntfs partition.

Sorry, I CAN'T reply any questions for this comment, because I have poor ENGLISH SKIL... :(

Erik said...

That's a great tip. I suspected it had something to do with those parameters.

Right now I'm having issues with my hard drive (I'm going to have to replace it) so it will be some time before I get a good dual booting 10.4/10.5 environment. In the meantime, use this tip for Leopard along with moving the ntfs-3g.fs package to /Library/Filesystems.

Toonman said...

Unfortunately this doesn't stop the "files names too long for destination problem" :(

ugsasaki said...

Please confirm below.

Check 0
After Edit ntfs-3g.util, unmount ntfs volume and re-mount it.

Check 1
"auto_xattr" option is typed correctly.

Check 2
Leopard is, not UPGRADE INSTALL but CLEAN INSTALL. UPGRADE INSTALL will causes some problems.

Toonman said...

I've got those in there and i can read/write to my external drive now actually

The bootcamp partition is still another problem, but that's no real issue.

My external drive works perfectly now with Leopard. Thanks heaps :)

mrelwood said...


I followed ugsasaki's guide, and I got my bootcamp partition working marvellously, and it mounts automatically. It shows on the desktop with the same icon as the Mac HD, which surprised me. But no problem, it works! And seems fast. Must do more testing.

I am not a programmer, and don't know that much about Mac internals, but since I got it working, anyone can. Here's the whole guide:

1) Install MacFuse Core 10.5 1.0.0 and reboot.
2) Install ntfs-3g 1.1004 ublio and reboot.
3) Change all permissions to Read&Write on /System/Library/Filesystems/ntfs-3g.fs
4) Show package contents of the same file.
5) You'll find a file called ntfs-3g.util. Open it with TextEdit.
6) Find line: local OPTIONS="default_permissions..."
7) Replace the whole line with:
local OPTIONS="local,auto_xattr,defer_permissions"
8) Save the file, and copy the file to /Library/Filesystems/
9) Reboot.

I'm not sure if reboot is required that often, but that's what I did, and it works.

Thanks all Yous!

Jason said...

On Tiger with MacFuse 1.0.0, "defer_permissions" does the trick. Nothing else is needed. Also I found "local" rather interesting. Why would MacFuse default to appear like a network drive? BTW, I found the "volicon" option does nothing for me.

Erik said...

That's right, the volicon option does nothing... and I'm in the process of investigating why. It works for my rarfs_fuse but not for ntfs-3g. I'd like to have a nice custom icon to distinguish ntfs-3g drives from other mounts, but on the other hand the "local" option also seems like a nice solution.

Eloom123 said...
This comment has been removed by the author.
Eloom123 said...

Ignore my past comment, I was using ntfs-3g 1.0004 Update 2, not Update 4 and was having the -n problem other users have reported.

I can confirm that ugsasaki's method for fixing the Leopard write issues are working. Thank you for solving this problem so quickly, I rely heavily on NTFS support in Mac OS and found Leopard very unusable without it.

Keep up the good work erik, this package you have created is very reliable and integrates seamlessly into Mac OS. It's the perfect solution for NTFS support in Mac OS.

Toonman said...

Yeh once again, this rocks.

I actually rebooted again and my bootcamp partition works also (as described above it shows with normal mac HDD icon) ... but read/write work

Additionally, with caching enabled my usb drive works great too :)

Great to see this all working awesomely with Leopard :) Great tips from uga too :)

Toonman said...

Anyone had any problems with bootcamp partition not being selectable in the startup disk now ?

The fixes above seem to play a bit of havoc with that ...

twelve said...

I'd install MacFUSE 1.0 and ntfs-3g 1.1004u4 and changed local OPTIONS= string to "local,auto_xattr,defer_permissions" as decribed above. Now I can write to NTFS drive, but can't copy files _from_ it: when I try to drag any file or folder on NTFS volume, cursor becomes crossed circle (like "no parking" road sign :) and if I try copy/paste, I get "The items on the Clipboard cannot be pasted to his location. One or more of the items may have been deleted or are no longer available".

BUT! If I copying files thru command line (cp ~/Desktop/filename.ext /Volumes/MyNTFSVolume/ ) or via muCommander, it's all fine.

mrelwood said...

Damn, confirming the above: Can not copy FROM NTFS-3G volume with Finder.

Erik said...

twelve & mrelwood:
That problem should go away if you just restart the Finder (Apple-Option-Esc, select the Finder and relaunch). I have no idea why it occurs.
I have experienced it in 10.4 and it goes away after a Finder restart.

Not a high priortity issue if you can solve it like I did.

Erik said...

toonman: NTFS disk not showing up in startup pane is a known issue with ntfs-3g in general. I should list these known issues someplace. :)

Eloom123 said...

I can also confirm, I am having the exact problem twelve has reported. Restarting the finder did not have any effect.

Any ETA's on a working Leopard release of this package?

ugsasaki said...

I usually use this AppleScript.
Please try it.

tell application "Finder"
display dialog "Restart and Boot Windows?" default button 2 with icon note
end tell
do shell script "sudo bless --device /dev/disk0s3 --legacy --setBoot" password "YOURPASSWORD" with administrator privileges
do shell script "sudo shutdown -r now" with administrator privileges

ugsasaki said...

... or use rEFIt.

Brian Kendall said...

I tried using both NTFS-3G 1.1004 Update 2 and update 4 with MacFuse 1.0.0 under Tiger, and had the same problem as everyone else. Specifically, I couldn't copy files to or from the partition, nor could I move files around on the parition. However, I could read, write, and delete files.

I tried following ugsasaki's instructions and editting the ntfs-3g.util file but it didn't fix the problem. Strangely, afterwards I was able to copy files to the partition from that point on, but I still couldn't copy anything off of it, or move files around. Restarting Finder didn't fix anything either.

So I tried uninstalling both MacFuse 1.0.0 and ntfs-3g, and reinstalled MacFuse 0.4.0 and ntfs-3g update 2, and now everything seems to be working fine. I'll keep an eye on how things go to see if I can reinstall MacFuse 1.0.0 at some point later.

Jason said...

Well I confirm the "can't copy from" bug. I wasn't paying attention to this last time. Turning on debug option, I get a lot of messages like

unique: 0, opcode: GETATTR (3), nodeid: 1, insize: 40
unique: 0, error: 0 (Unknown error: 0), outsize: 112
unique: 1, opcode: GETATTR (3), nodeid: 1, insize: 40
unique: 1, error: 0 (Unknown error: 0), outsize: 112
unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 40
unique: 2, error: 0 (Unknown error: 0), outsize: 112

Erik said...

This is a really weird issue. Has anyone managed to solve it, so the package works with MacFUSE 1.0? In that case, please reply...

I've been trying out different MacFUSE options all day, but without luck. I'm unsure if MacFUSE is to blame, or if I should speak to Szaka for ntfs-3g issues.

It certainly seems like a MacFUSE issue, since ntfs-3g works perfectly on other platforms. On the other hand, I'm not sure what Finder expects a file system driver to deliver in terms of permission handling etc. (not being able to copy files from an NTFS volume smells like a permission issue).

The fact that all is well when using the command line tells us that it's not an issue with POSIX permissions, but with something else, probably Mac-specific.
I have experienced this issue (not being able to copy files, Finder unwilling to cooperate) with 0.4.0 from time to time (not that often), but in that case a reboot of the Finder made it go away. With MacFUSE 1.0.0, that trick doesn't work, whether you work in Tiger or Leopard.

Patrik said...

I thought I should just mention this, in case anyone else sees the same problem.

I'm not positive this has anything to do with ntfs-3g or MacFuse, but yesterday all of a sudden, my boot camp installation of Win XP stopped working. Neither 'last working config' nor 'failsafe' modes worked. Now I finally found a way to run chkdsk on a non-booting Windows disk, and it appears to be sorting itself out.

I did however get some error notes when running chkdsk (please have patience with my loose translations):

CHKDSK is verifying files (step 1 of 3)...
Truncating the damaged attributes list for file xxxxxx
Truncating the damaged attributes list for file xxxxxy
The damaged post in the attributes list with type code 128 in the fule xxxxxy was removed. (three times)
Removing the damaged attributes post (128, "") from the file post segment 17708. (three times with different files)
File verification complete.
Removing abandoned file post segment: (numbers listed above).

This all occurred like two days after installing 1.1004, and one day after running the 'ublio activate' command. I'm actually unsure whether I upgraded to MacFuse 1.0, but I'm quite sure and can't think of any way of checking it...

I have not installed any apps in Windows since then, except MPlayer which should have no significance as to this problem. Basically the only mac app using ntfs-3g regularly is Xtorrent, which uses the ntfs disk for downloading.

Szaka said...

Patrik: Please check your hardware and disk for hardware faults (bad sectors, etc). It seems that the market was flooded with lower quality disks recently (mostly from seagate, lacie, samsung).

About not being able to read files: it may be just a permission issues, i.e. the reading user indeed doesn't have right to read the file. By default the driver gives access to anybody but not if any of the {default|defer})_permissions, uid, gid, or any of the *mask option is used. Any of those option turns on posix permission handling.

If this is not the issue then it must be an OS X, MacFUSE or Finder specific one.

Anonymous said...

ntfs-3g 1.1104 released! So it is possible to build a new one including you patches (if it is still required)?

Erik said...

Anonymous, November 4, 2007 7:50 PM:

I have built 1.1104 both with patches and without. When I get home this evening I'll try to build a release package and publish it.

Howver, I'm confused about what people are saying about Leopard, that it needs the file system to be in /Library/Filesystems. Why? In my Leopard install it worked perfectly with /System/Library/Filesystems, and all the native file systems were located there. It seems it's only fusefs.fs that positions itself in /Library/Filesystems...

jediganesh said...

Hi, I dloaded the stable version and installed it and the MacFUSE files. Now when I plug in my ext hdd it doesn even dectect it anymore! Can some pls help me??

Erik said...


This version is very old. Please use the latest version, listed on the top of the page at (currently 1.2506).
There is also an FAQ post on this blog if you browse backwards that might help you.