Subject: Re: [netatalk-admins] Re: ushare to netatalk resource fork conversion?
From: Bill Studenmund (skippy@macro.stanford.edu)
Date: Mon Jul 07 1997 - 17:53:27 EDT
On Mon, 7 Jul 1997, Patrick M. Frazer wrote:
> I wish it were that easy. Good idea though. Thanks to Tim, Frank
> Morton and Dan Pritts for responses to my query.
>
> The synopsis of what I've heard is to turn the Ushare data into a
> MacBinary format and use Netatalk's command set built around 'megatron'
> to pull it back out. Sounds simple enough, but there's no way known to
> IPT's tech support guys to turn the Ushare data and resource forks into
> a MacBinary. (Ugh!) Having recently found the 'mcvert' package which
> will turn a "real" Mac file into a MacBinary format, I'm left with the
> task of turning the Ushare resource fork into a "normal" resource fork.
> The techs at IPT have provided this much information:
>
> Offset Description
> 0-32 Finder Info
> 33-255 Proprietary
> 256 Comment Length
> 257-456 Comment
> 457-511 Proprietary
> 512- Resource fork data
>
> It looks like if I can interpret and use the 32 bytes of Finder Info and
> the data after offset 512 I can construct a "normal" resource fork.
> Does anyone on this list have any insight into this? Anyone know how
> the 32 bytes of Finder Info are laid out? Anyone have some Tylenol?
How is the finder info layed out in either an .AppleDouble file, or in a
macbinary file? If it's a block of 32 bytes, I bet it's the same, so just
directly copy it over.
Take care,
Bill
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:25:30 EST