There is probably a freebie or two online somewhere. But, you could
probably program up a simple app to do it. As I recall, the files in
the Resource.frk folder are Macintosh resource forks copied as a
binary stream to the corresponding file's data fork. You use the file
system API that opens the resource fork as a stream (don't recall the
exact one right now) and dump the data into it.
The simplest old-school way to do it was to put the files onto a
Windows floppy and stick it in a Mac. When you copy the outer file
to the Mac, it'll be converted.
On the downside, the old PC Codewarrior stuff would occasionally
create PICT resources with incorrect terminators. These would crash
an OS-9 Mac (don't recall if I tried it on an OS X Mac.) These were
fixed by adding one more zero byte at the end if I recall (needed a 2-
byte terminator instead of the 1-byte terminator that it had.)
On Dec 1, 2006, at 1:22 PM, P REEDER wrote:
> On non-HFS file systems, Mac forked files are split into a file
> containing the data fork, and file in a Resource.frk directory for
> the resource fork.
> I'm trying to compile the palmOne sample code with a XCode/prc-
> tools environment. Unfortunately, unzipping the palmOne archives
> produces resource files that are split for a non-HFS file system.
> ConstructorX does not recognize these as being Palm resource files.
> Is there any Mac-only way to reconvert these split files into
> something comprehensible? (Ideally, into .rcp files, but if I can
> reconvert them to Mac forked files, presumably rsrc2rcp can do that.)
> For information on using the PalmSource Developer Forums, or to
> unsubscribe, please see http://www.palmos.com/dev/support/forums/