[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IIGs on a PC



kws@delphi.com writes ...
> 
> Rubywand <rubywand@swbell.net> writes:
> 
> >fork. Nulib will not unshrink a file which includes a Resource fork.
> 
> Not true.  Newer versions (3.25 is the newest) will extract the data fork.
> Older versions might not, but they should be able to list the contents
> (nulib tv file.shk).


     Thanks for the correction/clarification re. extracting data forks.

     Regarding v3.25, continued interest in Nulib improvement is,
certainly, good news for Apple II users who want to work with Apple II
.shk files on their PC's.
 
     An email from the current Nulib developer notes that Nulib v3.25 is
not yet available in MS-DOS or Windows- runnable form. Also, Nulib v3.25
still does not extract resource forks. So, for now, most PC users should
continue to depend upon Nulib v3.24.

 
> >     Another possibility is that the snag was introduced in the
> >Apple-to-PC transfer. If your Apple II telecom program is set to send a
> >Binary II header (e.g. "Binary Up", etc. is set to ON), this could
> >produce a file which Nulib would view as 'messed up'. Make sure that
> >your Apple telecom program does not attach a Binary II header. Also, do
> >not ask ShrinkIt to attach a Binary II header at the time you create a
> >..SHK file.
> 
> Newer versions also handle Binary II wrappers (and identify them as such).
>

     Yes. Some users may try to add a Binary II header in GS-ShrinkIt
and have their A2 telecom program set to do the same. This will cause
problems. In general, it is best to avoid adding any Binary II header.



Rubywand