On Tue, 17 Sep 2002, Kevin K Woo wrote:

>
> Hi Michael,
>
>       I've noticed that the OF 2.4 boot procedure is different in the 1.6
> INSTALL document compared to the 1.5.2 INSTALL document. The change I
> noticed was the relevant boot invocation command in the 1.5.3 and 1.6
> INSTALL documents is:
>
>       boot ide1/disk@0:0 NETBSD.MACPPC
>
>       While in the 1.5.2 document it was:
>
>       boot ide1/disk@0:0,OFWBOOT.XCF NETBSD.MACPPC

Hmmm... OFWBOOT.XCF should probably be there.

>       I've tried both commands to boot the NetBSD 1.5.2 macppc standard
> ISO, but both commands gave me the "unrecognized Client Program format
> state not valid" error message. I'm quite confident that I've typed in the

What are the exact messages, both the error and preceeding it?

That sounds like an OF error message. If ofwboot.xcf fires up, it'll print
a message indicating it did so. Do you see that?

> filenames of the bootloader ("OFWBOOT.XCF" in uppercase) and the gzip'ed
> kernel ("NETBSD.MACPPC", also in uppercase), because these filenames are
> the filenames I see when I invoke "dir ide1/disk@0:0" while in OF 2.4. I
> also tried the boot command with the filenames in lowercase ("ofwboot.xcf"
> and "netbsd.macppc"), and naturally, that didn't work either.
>
>       From the INSTALL instructions and the port-macppc mailing list, I've
> seen that booting a hybrid CD with an OF 2.4 machine has brought mixed
> results. Should the NETBSD.MACPPC file be gzip'ed when on the CD? I do not
> know whether the OFWBOOT.XCF can decompress the gzip'ed NETBSD.MACPPC file.
> If the OFWBOOT.XCF file doesn't decompress gzip files, then that may
> explain why I've been unable to boot the standard 1.5.2 macppc ISO, given
> the NETBSD.MACPPC file in the standard 1.5.2 macppc ISO appears to be
> gzip'ed.

Take care,

Bill