Closed GoogleCodeExporter closed 8 years ago
MacFUSE doesn't have anything to do with burnable discs. How did you conclude
that "MacFUSE disables" them?
Just circumstantial evidence?
Did you install MacFUSE alone, or did you install some file systems that use
MacFUSE (ntfs-3g, for example)?
Where did you get these packages from?
Have you looked at the "CDs & DVDs" preference pane in System Preferences to
check what your current behavior
is for blank discs?
Original comment by si...@gmail.com
on 31 May 2007 at 4:01
There wasn't a problem with burnable disks immediately before I installed
MacFUSE, but there was a problem
after. So yes, circumstantial evidence but I thought it was a valid inference.
I installed ntfs-3g but I've removed that as well.
Blank CDs and DVDs were set to open the finder.
Original comment by ermitgil...@gmail.com
on 31 May 2007 at 5:06
> So yes, circumstantial evidence but I thought it was a valid inference.
All of MacFUSE Core's components are passive--unless you actively use MacFUSE,
nothing even "kicks in".
Think of MacFUSE as a library of code that anybody can use to write file
systems.
There's no "official" ntfs-3g package for Mac OS X. Which specific ntfs-3g
package did you install and where
did you get it from? Recently there was some talk here and in the macfuse-devel
mailing list that a "broken"
ntfs-3g package "disabled" mounting of most/all disk images, or something like
that. Try searching here or
on Google. I think some people also had trouble uninstalling that version of
ntfs-3g cleanly. Unless the
following post is also by you, this person seems to be having a similar issue:
http://forum.ntfs-3g.org/viewtopic.php?t=523
Original comment by si...@gmail.com
on 31 May 2007 at 6:16
Ok. Thanks for the swift responses. Those seem to be the same problems I've
been having, though I've never
had any probems with disk images.
I got my version of ntfs-3f from
http://shadowofged.blogspot.com/2007/03/ntfs-3g-for-mac-os-x.html,
which was listed as the Mac OS X version on the main page of ntfs-3g.org.
Original comment by ermitgil...@gmail.com
on 31 May 2007 at 6:44
See some of the comments in issue 194 on this site. Looks like somebody was
able to fix such issues by cleanly
uninstalling ntfs-3g.
Original comment by si...@gmail.com
on 31 May 2007 at 6:55
Original comment by si...@gmail.com
on 31 May 2007 at 6:03
I too had the issue with some but not all disk images failing to mount.
Resolution was indeed removal of NTFS-3G using the .command files provided with
the developer's distribution.
Original comment by grahampe...@gmail.com
on 7 Jun 2007 at 5:54
Original issue reported on code.google.com by
ermitgil...@gmail.com
on 31 May 2007 at 2:55