So I've got this FluxEngine thing which lets you read and write exotic floppy disk formats on normal PC drives (with some extra hardware): http://cowlark.com/fluxengine/ It'll do Mac 400kB and 800kB disks.
I'm currently adding support for direct filesystem access, so that you can read and write files directly without needing to image the disk. Naturally, HFS is one of the formats (via libhfs ripped out of hfsutils). However, the Very Special Nature of Mac files is raising its ugly head again. I need a unified way to present both the data and resource forks in a single file. I decided in AppleSingle and implemented it, and AFAICT it works, but further investigation shows that nearly all tooling prefers MacBinary.
I thought that AppleSingle was supposed to _replace_ MacBinary (re https://www.ietf.org/archive/id/draft-newman-macbin-binhex-harmful-00.txt). Did this actually happen? Is MacBinary actually more useful and preferred in the real world?
I'm currently adding support for direct filesystem access, so that you can read and write files directly without needing to image the disk. Naturally, HFS is one of the formats (via libhfs ripped out of hfsutils). However, the Very Special Nature of Mac files is raising its ugly head again. I need a unified way to present both the data and resource forks in a single file. I decided in AppleSingle and implemented it, and AFAICT it works, but further investigation shows that nearly all tooling prefers MacBinary.
I thought that AppleSingle was supposed to _replace_ MacBinary (re https://www.ietf.org/archive/id/draft-newman-macbin-binhex-harmful-00.txt). Did this actually happen? Is MacBinary actually more useful and preferred in the real world?