[parisc-linux] Burning CD Images difficulties: revisited

Thu, 10 Oct 2002 09:27:37 +0200

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2702E.8229A8D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: Jeffo [mailto:jeffo@pop.hsbc.com.br]
> Hello all!
> I hope this is the right place for posting such a question:
>=20
> - I=B4ve tried MANY times  (5) burning an PA-RISC image to a=20
> bootable CD.
> Couldn=B4t make my system
> boot from the CD though...the image I=B4m talking about is this one:
> http://pateam.esiee.fr/cd-images/palinux-0.9.3.iso

Other replies indicate how to test the image.

>=20
> I have a 712/60 HP station, with an external SCSI CD-rom=20
> drive. The drive is
> at ID "scsi.3.0".
> I do the boot search after the POST routine, it finds my SCSI=20
> drive, its
> brand and everything else.

What brand is it? Run-time, there are no special requirements.

>=20
> When I try to boot from the CD the station simply does=20
> nothing. It tryes to boot and returns
> to the BOOT_ADMIN screen. ONCE I could get a message like "loading =
the
> stuff, etc....OPS, KERNEL something".
> And only ONCE...in one of the first CDs.

Boot time, the HP bootloader requires 2KByte block size. Most (if not =
all)
CDRom players use 512Byte blocksize by default. Try to figure out if =
your
CDRom can do a 2KByte blocksize.

>=20
> I did an extensive search on the Internet regarding this=20
> subject, and used all hints found for
> the burning software (yes, I=B4m burning on XP, unfortunately=20
> all linuxes I=B4ve found doens=B4t
> have CD writers)...used Nero 5.5, CDRWin 4.0B and Blindwrite.=20
> None of them seem to burn this image
> correctly. And I say that with the knowledge after burning many, many
> applications, games, etc
> onto CD-R. Protected or not. For AIX, for Windows, for Solaris.
> Weird...

As above, most likely, the image is not the problem, it's the blocksize =
the
drive provides to the system.

>=20
> The simptoms are:
>=20
> - If I load the CD on a windows machine, everything seems to be fine,
> DESPITE all filenames being in CAPS... (bad sign?)

iso9660 is a single-case (that's the all-caps) and versioned (that's =
the ;1)
filesystem.

> - On the 712/60 it won=B4t boot.
> - After booting into HP-UX, if I try to mount the CD it takes=20
> a looong time and then the OS finally mounts it, but all filenames =
are=20
> capitalised AND SOMETIMES, the ";1" suffix is appended to every =
filename.
I=B4ve seen
> something about that on Nero, but on tabs that you simply  cannot =
change.
> (something like "doesn=B4t append ;1 on...")
> - I contacted a friend and co-worker which is a "Linux" guy,=20
> but he wasn=B4t willing to help much..
> - Things that I=B4ve read on the net like "Search the iso or=20
> the CD for the #8000 sector and see if the MAGIC word is on there =
(CD001)=20
> and IT IS in all Cds I=B4ve searched.
>=20
> I am REALLY interested in putting this thing to run up on my HP
> station....but I=B4m having a hard time...

If you have no success on the CDRom player, try a netboot if you have =
an
other machine around. Check the website for more info. A search key can =
be
"bootp" since that's the network boot protocol.

Success
CBee

------_=_NextPart_001_01C2702E.8229A8D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>RE: [parisc-linux] Burning CD Images difficulties: =
revisited</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Jeffo [<A =
HREF=3D"mailto:jeffo@pop.hsbc.com.br">mailto:jeffo@pop.hsbc.com.br</A>]<=
/FONT>
<BR><FONT SIZE=3D2>&gt; Hello all!</FONT>
<BR><FONT SIZE=3D2>&gt; I hope this is the right place for posting such =
a question:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; - I=B4ve tried MANY times&nbsp; (5) burning an =
PA-RISC image to a </FONT>
<BR><FONT SIZE=3D2>&gt; bootable CD.</FONT>
<BR><FONT SIZE=3D2>&gt; Couldn=B4t make my system</FONT>
<BR><FONT SIZE=3D2>&gt; boot from the CD though...the image I=B4m =
talking about is this one:</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://pateam.esiee.fr/cd-images/palinux-0.9.3.iso" =
TARGET=3D"_blank">http://pateam.esiee.fr/cd-images/palinux-0.9.3.iso</A>=
</FONT>
</P>

<P><FONT SIZE=3D2>Other replies indicate how to test the image.</FONT>
</P>

&gt; 
 &gt; I have a 712/60 HP station, with an external =
SCSI CD-rom 
 &gt; drive. The drive is
 &gt; at ID &quot;scsi.3.0&quot;.
 &gt; I do the boot search after the POST routine, it =
finds my SCSI 
 &gt; drive, its
 &gt; brand and everything else.

What brand is it? Run-time, there are no special =
requirements.

&gt; 
 &gt; When I try to boot from the CD the station =
simply does 
 &gt; nothing. It tryes to boot and returns
 &gt; to the BOOT_ADMIN screen. ONCE I could get a =
message like &quot;loading the
 &gt; stuff, etc....OPS, KERNEL =
something&quot;.
 &gt; And only ONCE...in one of the first CDs.

Boot time, the HP bootloader requires 2KByte block =
size. Most (if not all) CDRom players use 512Byte blocksize by default. =
Try to figure out if your CDRom can do a 2KByte blocksize.

&gt; 
 &gt; I did an extensive search on the Internet =
regarding this 
 &gt; subject, and used all hints found for
 &gt; the burning software (yes, I=B4m burning on XP, =
unfortunately 
 &gt; all linuxes I=B4ve found doens=B4t
 &gt; have CD writers)...used Nero 5.5, CDRWin 4.0B =
and Blindwrite. 
 &gt; None of them seem to burn this image
 &gt; correctly. And I say that with the knowledge =
after burning many, many
 &gt; applications, games, etc
 &gt; onto CD-R. Protected or not. For AIX, for =
Windows, for Solaris.
 &gt; Weird...

<P><FONT SIZE=3D2>As above, most likely, the image is not the problem, =
it's the blocksize the drive provides to the system.</FONT>
</P>

&gt; 
 &gt; The simptoms are:
 &gt; 
 &gt; - If I load the CD on a windows machine, =
everything seems to be fine,
 &gt; DESPITE all filenames being in CAPS... (bad =
sign?)

<P><FONT SIZE=3D2>iso9660 is a single-case (that's the all-caps) and =
versioned (that's the ;1) filesystem.</FONT>
</P>

&gt; - On the 712/60 it won=B4t boot.
 &gt; - After booting into HP-UX, if I try to mount =
the CD it takes 
 &gt; a looong time and then the OS finally mounts =
it, but all filenames are 
 &gt; capitalised AND SOMETIMES, the &quot;;1&quot; =
suffix is appended to every filename. I=B4ve seen
 &gt; something about that on Nero, but on tabs that =
you simply&nbsp; cannot change.
 &gt; (something like &quot;doesn=B4t append ;1 =
on...&quot;)
 &gt; - I contacted a friend and co-worker which is a =
&quot;Linux&quot; guy, 
 &gt; but he wasn=B4t willing to help much..
 &gt; - Things that I=B4ve read on the net like =
&quot;Search the iso or 
 &gt; the CD for the #8000 sector and see if the =
MAGIC word is on there (CD001) 
 &gt; and IT IS in all Cds I=B4ve searched.
 &gt; 
 &gt; I am REALLY interested in putting this thing to =
run up on my HP
 &gt; station....but I=B4m having a hard =
time...

If you have no success on the CDRom player, try a =
netboot if you have an other machine around. Check the website for more =
info. A search key can be &quot;bootp&quot; since that's the network =
boot protocol.

<P><FONT SIZE=3D2>Success</FONT>
<BR><FONT SIZE=3D2>CBee</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C2702E.8229A8D0--