NTFS-3G, Tuxera, Paragon drivers for writing NTFS won't work in 64-bit, even for Vanilla kernel, the only driver that works for 64-bit Snow Leopard is hidden inside Snow Leopard, you have to active it to use it, however, in my case, and from other people as well, it will make your NTFS partitions errors

A semi-complete solution exists
 

Hello Everyone!

I had this same problem but after blasting Google i found what i was looking for. Not the latest version it seems but hey, it works for ME and you can always recompile it yourself (any takers to build latest version on this forum?)

MacFUSE 2.1.7 for 64 bit Snow Leopard
===============================

you can get it from here -> http://static.caurea.org/MacFUSE/MacFUSE-2.1.7.dmg

The original link is dead so thanks google cache!

Got this info from -> http://www.turingtarpit.com/2009/04/...and-macfusion/

"Compile it yourself …
http://github.com/wereHamster/macfuse
Or download and install precompiled binary…
http://groups.google.com/group/macfuse/msg/f7de55623e8b8f57?"

I also recommend fuse-ext2 which also works on 86_64 kernel. It works for ext3

http://prdownloads.sourceforge.net/f...7.dmg?download

Have fun. i'm glad i could contribute something at last!

Please note, this is experimental software so no guarantees it will not cause problems etc.

Note - I selected the reliability mode in NTFS (which seems pretty slow) and you need the latest NTFS3G which has recently been updated:-

http://sourceforge.net/projects/cata...x.dmg/download

Its nice to access all drives under SL without stupid boot flag. Lets hope we see lots more stuff for the new kernel in 2010!

Cheers

:cool:

+ Original info from cached googlepage (http://groups.google.com/group/macfuse/msg/f7de55623e8b8f57?") re compiling etc :-

<START> On Sep 11, 2009, at 12:39 PM, corvo wrote:

> I would like to use MacFuse with 64-bit kernel, but I have no idea how
> to apply these patches. Maybe someone could post some sort of step by
> step instructions here? Thanks.

I made a package for those who don't know how to compile MacFUSE.
Disclaimer: I'm not a MacFUSE developer so I don't guarantee anything.
This package is provided as-is without any warranty! If it makes your
computer explode, DON'T BLAME ME! You have been warned.
I compiled it on my MacBook running MacOS X 10.6 and Xcode 3.2, git
revision c537453b7be9e63eab9c8caa84ef2a064396f485 (you can fetch the
code from my macfuse repository on github.com/wereHamster). This is
the command that I used:
./macfuse_buildtool.sh -c Release -p 10.5 -t smalldist -d

The package is available here: http://static.caurea.org/MacFUSE/MacFUSE-2.1.7.dmg

If you want to build the package yourself, clone my macfuse repository
on github, cd into core/ and run the above command.

tom <END>

For building, please check post on his group page for updates

http://groups.google.com/groups/prof...fjJfYkQTWXi1Vg

such as this one:-

http://groups.google.com/group/macfu...73b1b26cf62c53

Please feel free to pm me or post if you have any tips, find a better solution or have compiled a better / more up to date version :-)

Also, if anyone has any experience of using Tuxera with Macfuse, please let me know. I read this interesting post:-

http://www.tuxera.com/forum/viewtopi...bb8a619d6b018d

Does this mean the only advantages to pure 64bit kernel are that it allows you to address over 32gb memory?

I understand that the hybrid kernel uses PAE so i guess a pure 64bit kernel would be a bit faster because of that.

64bit preference pane here -> http://macfuse.googlegroups.com/web/...Mt0t6nY0uV5FIQ

UPDATE! -> After reading some more about this, it would seem that although this works, there are some fixes that need to be made to make this 100& stable and fast on the 86_64 kernel :-

http://groups.google.com/group/macfu...951b355e57db56

I will watch this space, eagerly awaiting developments :)

pcj can you upload your last modified kernel for amd? link on rapidshare is dead...

so??? nobody can answer?

do you think this problem will ever be solved? its like talking to death ears.. if the computer wasn't a laptop I would have not kept using it..

I have an older dual Xeon machine which has the same problems, but i don't want to dump it because it is equipped with 4gb of ecc ram and dual intel ethernet. Can anybody confirm the problems are only caused by the SSE3 emulator?

I don't think it will be solved because (from Voodo Document)
Without source code, people have to rebuild a SSE3 emulator from stratch.

It might also be GCD.. but I don't think there is a documented way to disable it. again, reverese enginnering takes a lot of time because of many trial and error. and the free community would not do it

Libdispatch is open source, so there shouldn't be much reverse engineering needed.

The problem is loading gdb in would cause the beachball problem in Xcode..It would be better if it CRASHED then we can get the log.., and then a log would be generated, I also cannot take a "Sample" in Activity monitor.. that would just beachball also.. having it beachball for hours on the "main" thread is hard to debug..

unless someone have other ways, like kernel_debug_kit_snow_leopard_10a432.dmg in the 10.6 distribution before in the newsgroup

Version 1.0 has been released, it seem to works on AMD arch=x86_64
http://bbs.pcbeta.com/thread-635115-1-1.html

http://rapidshare.com/files/365667843/Kernel_V1.0.zip
http://www.megaupload.com/?d=CNB9B4HS