FUSE-HFS now works on Monterey!

[emendelson]

Step by step:

1. Download from your link.

2. Move img file to the desktop

3. Double-click on the img file.

Ventura on an Apple Silicon MacBook Air.

Maybe reinstall Ventura on your machine?

[JDW]

Step by step:

1. Download from your link.

2. Move img file to the desktop

3. Double-click on the img file.

Ventura on an Apple Silicon MacBook Air.

Maybe reinstall Ventura on your machine?

I am using the version of MacOS that is the title of this thread — Monterey. Ventura is a newer version of MacOS that comes with its own set of issues, which is why I am preferring to stick with what works for me (in all other apps I use) for now. But even if one wishes to content that it works in Ventura, the title of this thread focuses on Monterey, which is why I am a bit confused why it is not working in Monterey on an M1 Max MacBook Pro.

I am more inclined to believe there is something blocking MacFUSE from working on my Monterey machine, rather than it being an "upgrade to Ventura for a fix" type of solution. And yet, as I mentioned earlier, it is not an issue with the settings chosen when booting into Recovery. Those settings are perfect.

And like I said, there is no issue with my M1 MBP otherwise. Every other app works perfectly. It is merely MacFUSE and the accessing of HFS images that is an issue right now, for reasons I don't fully understand, since the title of this thread mentions Monterey, and I would therefore expect it to work properly on Monterey.

Hmmm....

[emendelson]

Forgot which system you were using. So here's Monterey:

[Ronald P. Regensburg]

I do not use MacFUSE and I do not intend to install it as i want to avoid, now deprecated, kernel extensions.

A few things to note:

- If MacFUSE (like other software that depends on kernel extensions) was installed in an earlier macOS version, it continues to work after upgrading macOS and even after migrating to a newer Mac. So the experience of users that already used MacFUSE before Monterey or Ventura cannot be compared to your situation.

- A kernel extension that is newly installed in Monterey (or Ventura) can only be allowed to load if it is from a "identified developer", see the dialog in the Recovery environment where you allow kexts to be used: "Allow user management of kernel extensions from identified developers". I do not know if the MacFUSE software is signed and notarized. If not, you are out of luck.

- If the software is from a "identified developer", and if it is installed properly, and if kexts are allowed to be used, you will need to restart your Mac for the alert from Privacy & Security to appear and you can 'Allow' the kext to be loaded in Privacy & Security.

[emendelson]

I was curious about this, and I had a borrowed Apple Silicon machine with a completely clean Monterey installation - no macFUSE, nothing at all.

So I installed macFUSE and fuseHFS following the step-by-step here:

https://imgur.com/a/0Rkn8AM

and it worked perfectly.

Summary: Install macFUSE 4.5; try to enable system extensions; get the message that I have to enable extensions in the Recovery Environment; shut down; open the Recovery Environment and enable reduced security; restart; enable the extension; restart again; install fuseHFS and all's well.

Ronald, macFUSE is from an identified developer (his name is in one of the screen shots). So, as you say, in System Preferences you need to allow app downloaded from App Store and identified developers, and this should work well as illustrated on the linked page.

[JDW]

I do not use MacFUSE and I do not intend to install it as i want to avoid, now deprecated, kernel extensions.

The result of course is that very few people on Apple Silicon Macs have given it a try. So I am not surprised or swayed by the success stories. If we had a larger pool of testers, no doubt I would then not be the lone person who cannot get it to work. This is not said to persuade you to try it yourself, it is just a fact about the small testing pool of people we have right now.

A few things to note:

- If MacFUSE (like other software that depends on kernel extensions) was installed in an earlier macOS version, it continues to work after upgrading macOS and even after migrating to a newer Mac. So the experience of users that already used MacFUSE before Monterey or Ventura cannot be compared to your situation.

- A kernel extension that is newly installed in Monterey (or Ventura) can only be allowed to load if it is from a "identified developer", see the dialog in the Recovery environment where you allow kexts to be used: "Allow user management of kernel extensions from identified developers". I do not know if the MacFUSE software is signed and notarized. If not, you are out of luck.

- If the software is from a "identified developer", and if it is installed properly, and if kexts are allowed to be used, you will need to restart your Mac for the alert from Privacy & Security to appear and you can 'Allow' the kext to be loaded in Privacy & Security.

I have noted all of those things and did everything perfectly, not once, but several times. It does not work on my M1 Max MBP, showing the error dialog I posted in my previous posts in this thread.

...I installed macFUSE and fuseHFS following the step-by-step here:

https://imgur.com/a/0Rkn8AM

and it worked perfectly.

Another success story. Well, I'm happy for you. But let it be known that your step-by-step is precisely what I did, although I had the settings in Recovery set properly before I even installed MacFUSE. And after having done repeated installs, it still refuses to work, showing the error dialog shown in my earlier posts.

I've basically given up at this point. And perhaps we should, for reasons that Ronald said in his previous post.

Honestly, the only thing I even need it for is to access the HFS formatted drive partitions on the SD card used by the Tash20. I really wish it had been designed like the FloppyEMU to use DSK images instead. Then there would be absolutely no need to try to make my Apple Silicon Mac read HFS at all. I could just use Mini vMac to manipulate files.

Oh well... At least I can say I gave it my best shot.

My humble thanks for all the kind feedback in this thread. It didn't help me, but maybe other people will get lucky.

Best wishes.

[emendelson]

Reinstalling macOS leaves your settings in place and often solves problems with programs that don't work. It can't do any harm.

[JDW]

Reinstalling macOS leaves your settings in place and often solves problems with programs that don't work. It can't do any harm.

True, but as you said, "it leaves settings in place." So even after I go to the trouble of reinstalling MacOS Monterey, if it still does not work, someone in this thread would simply quip, "Yeah, it's a setting. Not sure what, but glad I don't have that problem like you!"

We now have 2-3 people who've gotten it to work, and here I am twiddling my fingers.

Of course, we might also then have someone come along and say "just do a clean install of MacOS and see what happens." That, of course, would be an even bigger job for me, as a lot of things would need to be reinstalled to get my system working again like it is now.

It's all very fiddly and troublesome, for reasons I don't fully understand.

Nevertheless, I will give your suggestion some thought. It's not a no-brainer though because of the time required. I would need to do a full backup first, which is always the right thing to do before reinstalling MacOS.

Probably a faster solution would be for me to boot from an external SSD that has MacOS Ventura on it and see if that works. If not, I could then reinstall MacOS on that external drive and see if that fixes the issue. If not, I can then truly say I've tried it all and throw in the towel.

[kanjitalk755]

Honestly, the only thing I even need it for is to access the HFS formatted drive partitions on the SD card used by the Tash20.

It is possible to create an image file even if the SD card cannot be mounted.

1) Insert the SD card.
2) Click "Ignore" for Finder dialog.
3) From a terminal window, check the SD card device file by "diskutil list".
4) Make an image file by "sudo dd if=/dev/disk# of=sd.img bs=1m".

"sudo dd" is a very dangerous command, so be careful not to mistake it.

The generated image file can be mounted on a mini vMac, etc.

[Ronald P. Regensburg]

Maybe easier and safer:

Monterey will not mount HFS volumes, but it will allow creating disk images from such volumes with Disk Utility:

- Connect the media
- Dismiss the alert (Ignore)
- In Disk Utility the HFS volume will appear greyed
- Select the volume (it may be erroneously identified as a Mac OS Extended volume)
- Choose in the file menu to create a new disk image from the selected volume
- In the Save dialog choose the format read/write

The resulting .dmg image file should mount fine in Mini vMac, BasiliskII, etc.

[emendelson]

I think the OP is not trying to create an image but read an existing one:

All I want is to be able to mount this SD card with HFS partitions on my Apple Silicon Mac.

[JDW]

I think the OP is not trying to create an image but read an existing one:

Exactly! I know very well how to create disk images. EDITING EXISTING IMAGES is all I'm after right now, via my modern Mac.

I booted from my external 2TB SSD with MacOS Ventura. I installed all OS updates. I then installed MacFUSE 4.5.0, only to see in System Settings that "FUSE for OS X" version 2.6.0 has already been installed! (Must have been in the distant past under a much older MacOS version that I since updated with newer MacOS versions.)

I then followed the advice of "bfleischer" here:
https://github.com/osxfuse/osxfuse/issues/864

He basically says to download MacFUSE 4.5.0, then use Extras > Uninstaller to uninstall old version 2.x versions, but that does NOT work in my cause. It only uninstalls version 4.5.0 (if installed), leaving version 2.6.0 in place. I wrote a comment on that Github page, but since the last reply there was 2021, I'm not holding my breath for a speedy reply.

Could be I have the same issue on my Monterey drive, although I've not rebooted into that yet.

So the question now becomes, how in the world do we uninstalled version 2.6.0 using our modern M1 Macs?

[emendelson]

Get the Find Any File app. Search for all files on the disk that have "macfuse" in the name, and delete them.

[JDW]

Get the Find Any File app. Search for all files on the disk that have "macfuse" in the name, and delete them.

While it was easy to find them that way, I cannot delete them due to insufficient permissions.

Opening MacOS Terminal, then typing "sudo rm " and then dragging and dropping individual files, then pressing return, does not delete them either. Still get permissions errors.

It's basically one file I need to delete in this path:

MySSD > Library > StagedExtensions > Library > Filesystems > macfuse.fs

UPDATE#1
Found the MacOS Terminal solution to delete the wicked kernel extension from the past...

sudo kextcache --clear-staging

It's now deleted. I will restart, install version 4.5.0, restart again, then install FuseHFS, restart again, and see what happens. Fingers crossed!

UPDATE#2
Two problems:

1. I am still seeing "FUSE for OS X" (version 2.6.0) in System Settings when I type "fuse" in the search bar within System Settings. Clearly, I need to use Find Any File to search for something else, but searching for "fuse" is out of the question because there are tens of thousands of files with that as part of their filename, making it far too much trouble to sift through them all. I would need to know exact filenames.

2. Inserting my SD card from the Tash20 does nothing. No error dialog, so that's a change, but not mounting at all is bad. Opening Disk Utility shows "Apple SDXC Reader Media" with two drives under it: (1) Sys 6.0.8 and (2) HD20. These are the drive partitions that should be there. But when I select one (within Disk Utility) and click the Mount button, it throws an error dialog with the following 3 lines of text...

Could not mount "Sys 6.0.8".
(com.apple.DiskManagement.dis
enter error 49153.)



P.S. If you want to see screenshots, see my post here (it's too much trouble to post screenshots in this forum!):
https://github.com/osxfuse/osxfuse/issu ... 1679786072

UPDATE#3
More screenshots below of my next failed attempt to delete all "osxfuse" files:
https://github.com/osxfuse/osxfuse/issu ... 1679872840

[JDW]

The amount of time I've spent on this is totally and utterly incredible, and to think, I still get the "The disk you attached was not readable by this computer" error dialog when my SD card is inserted!

For what it's worth, here's what I did...

1. Disabled SIP within the Terminal inside the Recovery environment on my M1 MBP. That basically unlocks the doors to everything I wanted to do before but couldn't. Didn't get disabled when booting from my external SSD for reasons I don't understand, but when I booted from my internal SSD (MacOS Monterey), I confirmed in the Terminal via "CSRUTIL STATUS" that it was disabled.
2. While booted into Monterey from my internal SSD, I used "Find Any File" to search for all instances of "osxfuse" and used the Terminal's "sudo rm -r " command line to zap those wicked files into oblivion.
3. Also using "Find Any File" I searched for all instances of "macfuse" and deleted those.
4. I restarted, then did a fresh install of MacFuse 4.5.0, then restarted again.
5. I did a fresh install of FuseHFS and restarted again. I now see only one control panel for MacFuse 4.5.0.
6. Sadly, when I insert my SD card, it's not readable, which means all my efforts have been in vain. That remains true even though some have mysteriously been blessed in getting this infuriating software to work for them!

Ack!

[emendelson]

Can you read the sample IMG file that you posted from an earlier thread? If so, that means that macFUSE is working but you need something else to read the SD card. You may need one of the file-system extensions for macFUSE listed here:

https://github.com/osxfuse/osxfuse/wiki

At this point, the place to ask for further help may be the macFUSE group, which seems active:

https://groups.google.com/g/osxfuse-group

[JDW]

Can you read the sample IMG file that you posted from an earlier thread?

No. Double-clicking any of my vintage Mac *.img files in the Finder while booted from the internal SSD on my M1 MBP running MacOS Monterey, even after all my work of deleting and fresh installing, results in the same error dialog I mentioned in my previous post.

[emendelson]

Possibly it's time to reinstall Monterey (after, as you say, making a backup)?

[Ronald P. Regensburg]

I doubt reinstalling the macOS will change anything. In Big Sur and later the OS itself is installed on its own sealed volume and cannot be changed, not even after removing system protections. The result after reinstalling will be identical. Any data outside the OS itself, including additional "system software" (software that will modify system behaviour like kexts) will not be affected by installing the OS. If incompatible, existing software will not be loaded.

From THE ECLECTIC LIGHT COMPANY, https://eclecticlight.co :

Big Sur and Monterey are different from all previous versions of macOS in that the great bulk of macOS is loaded and run from a Sealed System Volume (SSV). That is first installed on the separate System volume, every file checked for integrity, the whole volume ‘sealed’ with a cryptographic hash, and then saved as an immutable snapshot. Every time that system is booted, its integrity is verified against Apple’s master Seal. So as far as the System volume is concerned, there’s nothing to be gained in a clean over a regular install.

Maybe try a utility like "EtreCheckPro". It will report stuff like old kexts and unsigned files.

[emendelson]

I doubt reinstalling the macOS will change anything. In Big Sur and later the OS itself is installed on its own sealed volume and cannot be changed, not even after removing system protections. The result after reinstalling will be identical.

I don't pretend to know anything about this, but I think an OS reinstall also installs some files to the user data folder. A reinstall definitely fixed problems that I was having with either Monterey or Big Sur a few years ago. But, again, I don't pretend to know anything for certain.

[adespoton]

I'm back...

The OSXFUSE issue explains the discrepancy nicely. I upgraded from it to the later MacFUSE when I upgraded to Catalina IIRC, so never experienced the sealed volume issues that have been plaguing JDW.

Because I've been upgrading/migrating my OS since the 10.2 days, I've got a bunch of stuff in the System folder that didn't come from Apple; sounds like SSV+SIP are going to make anything but a clean install + migration a complete headache. Doing a clean install and then migrating settings will give you the opportunity to NOT transfer third party kexts and custom configs when restoring from TM backup -- but this seems like an awful lot of work for not much benefit.

At least we appear to have identified (and documented) the issue: having a 2.x OSXFUSE installed on a system upgraded to Big Sur/Monterey gets it wrapped inside SSV, which makes it really difficult to remove. And unless it's removed, MacFUSE 4.x refuses to run, which means the FuseHFS plugin for Monterey+ will never function.

A better solution may be to install hfstools, which will allow you to move files on/off the images from the command line, or use Basilisk II and a shared folder like I did for all the years that FuseHFS was broken by Apple's HFS driver conflicts. Not as nice as using MacFUSE/FuseHFS, but both solutions should work.

[MetalSnake]

There is a kext-less fuse here https://github.com/macos-fuse-t/fuse-t

I used that, and compiled fusehfs ( https://github.com/thejoelpatrol/fusehfs ) against fuse-t and I can mount HFS CDs (images and real CDs) on my M1 Mac with macOS 13 Ventura.

I did that a while back, so I can't remember the details. But with that I got it running without the need to deactivate security features like SIP. I remember I had to fiddle around with the files.

Hopefully this might help a bit.

[adespoton]

There is a kext-less fuse here https://github.com/macos-fuse-t/fuse-t

I used that, and compiled fusehfs ( https://github.com/thejoelpatrol/fusehfs ) against fuse-t and I can mount HFS CDs (images and real CDs) on my M1 Mac with macOS 13 Ventura.

I did that a while back, so I can't remember the details. But with that I got it running without the need to deactivate security features like SIP. I remember I had to fiddle around with the files.

Hopefully this might help a bit.

That's awesome! I figured someone would implement a kextless FUSE eventually, but I didn't realize it had been done already

This looks better than OSXFUSE; now I've just got to figure out how to uninstall OSXFUSE so I can install FUSE-T.

[emendelson]

There is a kext-less fuse here https://github.com/macos-fuse-t/fuse-t

I used that, and compiled fusehfs ( https://github.com/thejoelpatrol/fusehfs ) against fuse-t and I can mount HFS CDs (images and real CDs) on my M1 Mac with macOS 13 Ventura.

Are there precompiled binaries that we can install, and is there a step-by-step description of how to get it running??? Would be grateful for any guidance.

EDIT: FindAnyFile finds six files on my system with osxfuse in the name. Perhaps it's enough to delete them?

[adespoton]

There is a kext-less fuse here https://github.com/macos-fuse-t/fuse-t

I used that, and compiled fusehfs ( https://github.com/thejoelpatrol/fusehfs ) against fuse-t and I can mount HFS CDs (images and real CDs) on my M1 Mac with macOS 13 Ventura.

Are there precompiled binaries that we can install, and is there a step-by-step description of how to get it running??? Would be grateful for any guidance.

EDIT: FindAnyFile finds six files on my system with osxfuse in the name. Perhaps it's enough to delete them?

Because OSXFUSE depends on a kext, you'll want to properly uninstall the kext (clear the cache, remove the file, re-enable SIP, etc.). I think it's possible this can be done via the OSXFUSE installer.