On Mon, 6 Nov 2000, Chris Tribo wrote:

> On Mon, 6 Nov 2000, Henry B. Hotz wrote:
> 
> > Now as to that "partition zero" stuff:  as I understand it it's a 
> > misnomer because there is really a "fake" Apple Partition Map there 

That's actually not correct. "partition 0" is a kind of notation OF 1 & 2
used to say, "use whatever looks right". For netbooting, I have to say,
"boot enet:0". In that case, it uses the bootp info to figure out what to
tftp.

While there is driver info in block 0 of the Apple partition map (well
block 0 of the disk), it's certainly not needed on OF 1 & 2 to boot -
installboot has never set it up right before, yet booted. :-)

> > with enough in it that OF can find the boot blocks with bootxx in 
> > them.  That's why you can't use "partition zero" with real Apple 
> > Partition Maps on the newer machines.  I think the zero means the 
> > boot blocks or the first bootable partition, and the meaning depends 
> > on the OF version number.  None of this is part of ofwboot.

I think the problem with the new machines is that they are either pickier
about what is needed to make a good driver, or that they just don't
support booting with a driver anymore. Which makes sense - these drivers
need the Apple Rom around to boot, but the roms are (on version 3 OF)
loaded from the file OF loads - thus drivers which need AppleRoms can't be
used to load the Apple Roms. :-)

> 	How is the *BSD and MacOS drive sharing && dual booting work coming
> along? Any status updates from our Port-master?

Drive sharing works. Setting up drive sharing is not simple. I don't think
tsubai has done much with dual-booting. I have, and ran into a problem. I
have a version if installboot which will not overwrite an existing Apple
Partition Map, but when I try to boot with that, it doesn't work.

> > >AFAIK:  Booting MacOS on OF 3 machines changes nothing.  On OF 2 machines
> > >only affects real-base.  On OF 1 machines resets all to default values.
> > >
> > >Someone correct me if I'm wrong.
> > 
> > All the machines I can play with freely are OF 1.0.5.  Chris, can you 
> > confirm that it's *only* the real-base that gets changed?
> 
> 	The only environment it changed was real-base when booting w/2.0f1
> to MacOS. It maintained across reboots into OFW. I can't confirm any

I too can confirm that booting in to MacOS resets real-base on my 2.0f1
machine.

> better than that unless the end result would be me taking a 15lb sledge
> hammer to my G3. One of these days in the very distant future I'll try
> learning PPC assembly and Forth...............and MIPS, 68k, 88k asym,
> etc.

You don't need all of that. :-)

I also think we might need to make two ofwboot.xcf's. I can't netboot the
one we now have, which is set to work with load-base == 600000 unless I
have loadbase != 600000. But the MacOS X boot loader (which is the next
thing to load if I want to boot MacOS) will NOT work with loadbase !=
600000. An ofwboot.xcf set for 680000 will netboot fine with load-base ==
600000. Yes, this is weird!

Take care,

Bill