Re: what are .sdk archives?

[touchstone]

On 2007-12-26 17:01:11 -0700, dempson@actrix.gen.nz (David Empson) said:

> Michael J. Mahon <mjmahon@aol.com> wrote:
>
> > Michael Kent wrote:
> > > To: touchstone
> > > > i give up!!
> > >
> > > > thanks everyone for their input on this, but i simply cannot get an
> > > > unforked file transfered from a mac.
> > >
> > > If you have access to a IIgs -- perhaps through emulation -- ShrinkIt GS
> > > can handle the .sdk archives directly, and it will handle forked files
> > > just fine.  You could then re-archive the disk or files into a different
> > > format if you have to.
> >
> > And once you get UNFORKIT working (which is actually a pretty small
> > Applesoft program), you can easily access everything else.
> >
> > Have I mentioned how much I wish the Mac would not add forks to
> > files that don't have them?  ;-)
>
> It doesn't.  The only reason a Mac will add a resource fork to a file
> which doesn't have one is if you do something like add a custom icon to
> the file. It is perfectly OK to have a file on the Mac with a data fork
> and a zero length resource fork.

the mac is not adding a macintosh resource fork.  although prodos is 
claiming that a forked
file exists, while it may, it is not refering to the macintosh fork.  
the forked prodos archivew i was
working with had resource forks of zero k, and would only add the fork 
if i asked the fork
editor to add one.

generally, getting files from a mac to an apple ii is no problem.  the 
'no problem' area involves
dos 3.3 and prodos archives in a .dsk, .do or .po archive, using macadt 
to transfer the image.  in
this circumstance, adt ignores any mac metadata and just transfers the 
image directly from the
data fork.

the trouble arose when i started looking at .sdk, .shk and .bxy 
archives that are not disk images,
but disk or file archives of various lengths ouside of the 143360 bytes 
requires of a .dsk.  i finally did
get these on my //e after setting up a //gs emulator with gs/os 6.0.1, 
shrinkitgs and unforkit0.1.
i ended up creating 'blank' 140k .dsk images, and working with the 
archives in the emulator, saving
them to the .dsk image and then onto the //e.  works like a semi-charm.

thanks again for all the info,