How to write nero format files on Solaris or HP-UX?

[Dave (from the UK)]

I'm trying to write a CD where I have a Nero (.nrg)

http://www.nero.com/eng/index.html

format image - it was written with Nero 6. The resulting CD should be
bootable on an HP workstation.

I can't seem to do write a bootable image.

Cdrecord can not work with nero format files.

I found the nrg2iso utility,

http://gregory.kokanosky.free.fr/v4/linux/nrg2iso.en.html

which is supposed to convert from nero to ISO, but this does not seem to
work for me.

There are two problems

1) The resulting iso is not a multiple of 512 bytes. lofiadm refuses to
work with that and cdrecord whilst able to write it, gives a warning
about padding it.

(I don't need to use lofiadm, but thought I'd look what is on it).

2) More importantly, the resulting CD which I wrote with cdrecord on my
Sun will not boot.

I have looked at the source of nrg2iso (only 124 lines long) and see it
simply skips over 307200 bytes of the Nero file, then writes the
remainder out as an ISO. I could easily modify it to create a file of a
multiple of 512 bytes, but I don't fancy spending a week pouring over
what I can find on the Nero file format and reading all about ISO files.

Any ideas for a quick solution? I tried finding a trial of Nero, but
seem unable to do so for Windows. There is one for linux I think, but I
don't really fancy installing linux to write a blinking CD.

Any solutions for Solaris (preferably), or Windows (second choice) or
HP-UX (third)?

[bgeer]

Post by Dave (from the UK)
I'm trying to write a CD where I have a Nero (.nrg)

If you're using Nero, I assume you are making your image on a Winblows
machine. Nero doesn't appear to write Rock Ridge extensions, so you
get 8.3 file naming on the cd when you mount it on the various Unices.

For any cd's destined for Solaris & other Unices which don't know
about Joliet, I always use mkisofs.exe, as in

mkisofs -V "Some Title" -rJ -o somename.iso [list of subdirectory[s]]

Yeah, I know it isn't a gui - who needs a gui anyways? :-)

I haven't tried building a boot cd for Unices on Winblows. Should
work, tho.

I then use Nero/Sonic/[some other gui] to burn the iso since I never
have cdrecord on the computer with the burner.

Search for cdrtools for windows. Can't remember exactly where I found
it, perhaps maybe here ftp://ftp.berlios.de/pub/cdrecord/alpha/.

Cheers, Bob

[Dave (from the UK)]

Post by bgeer

Post by Dave (from the UK)
I'm trying to write a CD where I have a Nero (.nrg)

If you're using Nero, I assume you are making your image on a Winblows
machine.

Someone else wrote the image on windows. I was given a nero image. (Nero
does run on Linux BTW too).

I need to burn the image, although a friend with Nero on his windows
computer offered to help, so the immediate problem is solved, although
I still need to get some media that can handle 800 MB, which none of
mine can. But the problem is now solved thanks.

Post by bgeer
Nero doesn't appear to write Rock Ridge extensions, so you
get 8.3 file naming on the cd when you mount it on the various Unices.

That is not true - I have just mounted the CD on a UNIX box (HP running
HP-UX 11 to be precise). The image was burnt on Windows using Nero, but
the file names are not limited to 8.3 (at least not on HP-UX).

I think the nero file is basically an iso, with some other rubbish added
to make it proprietry.

Post by bgeer
For any cd's destined for Solaris & other Unices which don't know
about Joliet, I always use mkisofs.exe, as in
mkisofs -V "Some Title" -rJ -o somename.iso [list of subdirectory[s]]
Yeah, I know it isn't a gui - who needs a gui anyways? :-)

Sometimes the gui is nice if you are adding lots of different files in
different places. Point and click is nice then, but you can do it with
xcdroast on Solaris and no doubt other systems too.

Post by bgeer
Search for cdrtools for windows. Can't remember exactly where I found
it, perhaps maybe here ftp://ftp.berlios.de/pub/cdrecord/alpha/.

Cheers. I know the UNIX one does not support Nero, so I doubt the
windows one does, but perhaps it does. I think the problem with Nero
files is that it their own propietry format.

Post by bgeer
Cheers, Bob

[Doug McIntyre]

Post by Dave (from the UK)

Post by bgeer
Nero doesn't appear to write Rock Ridge extensions, so you
get 8.3 file naming on the cd when you mount it on the various Unices.

That is not true - I have just mounted the CD on a UNIX box (HP running
HP-UX 11 to be precise). The image was burnt on Windows using Nero, but
the file names are not limited to 8.3 (at least not on HP-UX).

Later revisions of the ISO9660 spec (ie. from 1999 IIRC) do allow
longer filenames in standard ISO 9660 discs. 32.3 is now allowed,
although you can go longer but lose some compatibility. From what I
remember, most systems I tried had zero problems with longer names
than even 32.3 except for MacOSX stopped at 32.3. You could see the
files, but not access them.

[Benjamin Gawert]

Post by Doug McIntyre
Later revisions of the ISO9660 spec (ie. from 1999 IIRC) do allow
longer filenames in standard ISO 9660 discs. 32.3 is now allowed,
although you can go longer but lose some compatibility.

Long filenames are possible for a much longer time. I bought my first CD
recorder 1995 and burned CD-Rs with Romeo file system which were easily
readable with SGI IRIX and other UNIXes (IIRC up to 128 char.).

Benjamin

[Ulrich Windl]

Post by Doug McIntyre

Post by Dave (from the UK)

Post by bgeer
Nero doesn't appear to write Rock Ridge extensions, so you
get 8.3 file naming on the cd when you mount it on the various Unices.

That is not true - I have just mounted the CD on a UNIX box (HP running
HP-UX 11 to be precise). The image was burnt on Windows using Nero, but
the file names are not limited to 8.3 (at least not on HP-UX).

Later revisions of the ISO9660 spec (ie. from 1999 IIRC) do allow
longer filenames in standard ISO 9660 discs. 32.3 is now allowed,
although you can go longer but lose some compatibility. From what I
remember, most systems I tried had zero problems with longer names
than even 32.3 except for MacOSX stopped at 32.3. You could see the
files, but not access them.

It's a very sad technology demonstration that HP-UX delivers: The same CD
displays fine In Windows/XP and Linux, almost fine in HP-UX 11.23 (ignores the
second session of a multi-session CD), and poor in HP-UX 11.11 (8-dot-3
filenames with semicolon and version number).

When mastering CDs, I refuse to breal standards. So my CDs have ISO9660 Level
1, Rock Ridge Extensions, and Joliet v3 extensions (only to make M$
happy). For DOS you can have TRANS.TBL too look up reasonable file names.

Regards,
Ulrich