: So, rather than needing two complete Map files, you could have Map be the
: complete file and Map.resources be used just for SDL. MacOS 9 and X would
: see the data and resource fork of Map, while other systems would just see
: the data fork.
: Or, could someone write a simple install/setup program for Mac users? It
: could just read the data fork from Map.resource and Images.img2, and put
: it in the resource fork of Map and Images, or vice versa. It would work
: for any scenario.
: I actually don't know of a utility that lets you exchange data between the
: data and resource fork of any file. I've only managed it by transferring
: the files between Mac and PC systems (usually by means of an emulator).
: Of course, there's no good reason why Mac Aleph One shouldn't be able to read
: Images and terminal data from the data fork instead of the resource fork.
I have gotten the mac version to read SDL images and maps. But the maps cant be a .bin file you have to use portmaster.