Thanks for the feedback Peter.  I'm the guilty party on the seemingly poor
documentation.  You'll have to excuse me if it's not quite up to snuff in
the area of creating the CD's on the MacOS side, but I really don't use
MacOS too much , and I don't own a burner or software on the MacOS side.
As Jeff mentions, you'll need to use BootX to kick things off for an older
machine, although it doesn't have to be setup as an extension.  Apparently
there is no archive of the list, although I've asked the same site that
archives the cooker list if they would also cover us.  I know many are
anxious for a beta2 CD, but I'd like to address a couple more issues
before I do that.  In particular the machines that are hitting the kernel
panic trying to boot, the machines with 2.4.4 kernel problems and at
least add some functionality to the post install X setup, even if it's not
100%.

Stew Benedict

-- 
MandrakeSoft    OH/TN, USA      http://perso.mandrakesoft.com/~sbenedict/


On Mon, 25 Jun 2001 [EMAIL PROTECTED] wrote:

> Thanks for your prompt reply Jeff.  I will check out the pointers you
> mentioned (I should have joined this ML straight away rather than wasting
> time trying to find the rather scattered info on the Mandrake PPC webpage
> forum).  I realize it is a beta, but even still, some pointers attached as a
> readme to the download file would have been useful.
> 
> > From: jeff <[EMAIL PROTECTED]>
> > Date: Sun, 24 Jun 2001 10:47:43 -0500 (CDT)
> 
> > BTW, the disk will not be
> > bootable on an Old World machine.  You will need to use BootX.  And you're
> > going to have other problems as well, until new iso images are released.
> 
> Any pointers on info as to how I use BootX (like I said a total newbie to
> Linux but very willing and able to learn).  If there are other problems even
> through the BootX route, are they insurmountable?  Should I just wait for
> the new iso images or is it possible to hack my way through it?
> 
> P.S. Is there any digest form of this list available?  Nothing was mentioned
> in the welcome message.
> 
> Thanks again, Pete.
> <[EMAIL PROTECTED]>
> 
> 
> 


Reply via email to