Re: netboot different behavior on ROM 01 and 03 GS

[Tony Kavadias <tonzaggl@gmail.com>]

On Dec 31 2010, 7:19 am, Ivan X <ivan...@yahoo.com> wrote:
> > Because PC Exchange on the Mac does not know anything about resource
> > forks on ProDOS disks.  If you copy a file with a resource fork on the
> > Mac to a ProDOS disk, PC Exchange does not copy that resource fork
> > over to the ProDOS disk.
>
> Beg to differ.

Right you are!  I have thought to try this out for myself on Mac OS
7.5.5 and Mac OS 8.1... unfortunately, Mac OS 9.1 causes the system to
die when writing to a ProDOS disk.  It seems to me that Apple broke
ProDOS compatibility at some stage after Mac OS 8.1... don't know when
and why, and I don't have a spare partition on my Mac to work out the
details!

So yes, Macs can be used to copy files between HFS and ProDOS volumes
without risk of damaging either Mac or GS/OS resource forks so long as
the "foreign" platform makes no attempt to change a resource map it
can't read.  I stand corrected.

> While that's true of the old Apple File Exchange application
> from System 7.0.1 and before, both the ProDOS File System and PC Exchange
> extensions are well aware of ProDOS resource forks, and utilize them. In
> fact, if you copy a Mac file to a ProDOS volume, it will always create a
> forked file by default, which is why I wrote UnForkIt for ProDOS 8 a long
> time ago. The only way to prevent this from happening is to ensure that the
> Mac file has creator "pdos" and type "TEXT" or type "pxyy" where x is the
> byte for the ProDOS file type and yy is the byte pair for the ProDOS aux
> type (usually $0000, which in ASCII terms is NULL NULL or ctrl-@ ctrl-@).
>
> And, the ROM 01 machine does boot, so it seems that the files made it over
> ok. It's just the ROM 03 that's barfing (though Peter Wong and Geoff Body
> sent possible solutions -- thanks, guys).

-- tonza