Re: PowerPC cd status

[Matt Porter <porter@debian.org>]

On Wed, Mar 22, 2000 at 11:20:40PM -0500, Daniel Jacobowitz wrote:
> On Wed, Mar 22, 2000 at 07:13:30PM -0900, Ethan Benson wrote:
> > yes there is something there, but not much:
> > 
> > 0000000 4552 0200 0000 1e44 0001 0001 0000 0000
> > 0000020 0000 0000 0000 0000 0000 0000 0000 0000
> > *
> > 0000760 0000 0000 0000 0000 0000 0000 0000 55aa
> > 0001000
> > 
> > 
> > that is the first 512 bytes of the image made by mkhybrid that i have
> > been testing.
> > 
> > here is the next 512:
> > 
> > 0000000 504d 0000 0000 0002 0000 0001 0000 0002
> > 0000020 4170 706c 6500 0000 0000 0000 0000 0000
> > 0000040 0000 0000 0000 0000 0000 0000 0000 0000
> > 0000060 4170 706c 655f 7061 7274 6974 696f 6e5f
> > 0000100 6d61 7000 0000 0000 0000 0000 0000 0000
> > 0000120 0000 0000 0000 0002 0000 0033 0000 0000
> > 0000140 0000 0000 0000 0000 0000 0000 0000 0000
> > *
> > 0001000
> > 
> > this is documented in /usr/share/doc/mac-fdisk/README.gz it says you
> > can have both a PC partition table and a mac partition table but the
> > disk will not be intel bootable. (probably becuse of those couple
> > bytes in use where a bootstrap would go)
> 
> Right.  The question is if that interferes with PReP.

No problem.  The PReP boot scheme uses a PC partition table.  However, the
bootstrap code area in block 0 that contains the table is not used.  It
seems clear to me now that since the mac table allows for a PC partition
table in it (minus the bootstrap code area) it works fine for booting
PReP.  The only thing that is used is that one of the primary partition
entries is set to type 0x41 (PReP Boot) and loaded with an absolute offset
and size of the image to be loaded from the block device.

-- 
Matt Porter
porter@debian.org