Error msg "operating system too old" on OSX 10.5 on connect

[GoogleCodeExporter]

When I connect my ntfs formatted usb hard disk drive to my mbp running OSX
10.5 (Leopard) I get the following error: "Operating System Too Old".
The volume is then correctly mounted in finder and read access works as
expected. However any writing operations on the drive are not possible.

What version of the product are you using? On what operating system?
MacFUSE-Core-10.4-1.0.0, OSX 10.5

please tell me if additional information is required.

Original issue reported on code.google.com by googelyb...@gmail.com on 10 Nov 2007 at 12:36

[GoogleCodeExporter]

Just updated to the latest macfuse (1.1.1) and ntfs3g (1.1104) now the problem 
ist a
little bit different: Writing to the first partition of my external usb drive 
works
but writing to the second partition is still impossible. And I do not receive 
the
above stated error msg anymore. When I compare the properties (cmd+i in finder) 
of
both volumes I noticed the following difference: 
Volume1 (writable):  Format: NTFS-3g (MacFuse) 
Volume2 (read only): Format: Windows NT FileSystem (NTFS)
It seems like it loads the default osx driver for the second volume...

Original comment by googelyb...@gmail.com on 10 Nov 2007 at 1:20

[GoogleCodeExporter]

1. The "10.4" in MacFUSE-Core-10.4 means it's for 10.4 only. That's why the 
download link says "for Tiger". 
That's why there's a separate download link right next to it for 10.5.

2. This place is only for reporting *BUGS* in MacFUSE Core, not for random 
discussion/usage help. When your 
usage issue turns out to be a bug in MacFUSE Core, *THEN* this is the 
appropriate place to report/track it.

3. For random discussion/usage help, please post in the macfuse-devel forum. I 
don't use ntfs-3g, but many 
others on the forum do. Hopefully they can help you.

Original comment by si...@gmail.com on 10 Nov 2007 at 7:41

• Changed state: Invalid

[GoogleCodeExporter]

Sorry for the confusion, of course I installed the 10.5 version for Leopard but 
when
posting the issue I became viction of a stupid typing mistake. Anyway, since the
initial error message originated from mac fuse and I did everything as it has 
been
told it was clear for me that this is a bug, and since no similar issue existed 
I
reported it in order to help you improve it...

Original comment by googelyb...@gmail.com on 11 Nov 2007 at 10:58