I suppose this is kind of a feature request for mkisofs, but it might also
be helpful information for other people who might have run into the same
problem.
As you may know, when creating a bootable CD, mkisofs automatically
generates the boot catalog. The resulting catalog has a blank "ID string".
(The ID string is stored in bytes 4 to 1B of the validation entry of the
boot catalog, see the El Torito spec for details.)
Some PC-like embedded systems will automatically boot from CD to update
their internal software, but to prevent the user from "accidentally"
installing Windows 98 or whatever, the BIOS checks the ID string to make
sure it is a proper software update for the device.
Now, I am doing some software development for such a device. For now, I am
able to make it work by running mkisofs to generate the iso image file, and
then running hexedit on the iso image. Using hexedit I search for the
validation record in the boot catalog, and manually write in the ID String
and the new checksum.
This is kind of a hassle, and is hard to automate. However, it works, and if
other people out there have run into the same problem I can give them hints
on how to do it.
It would be convenient if mkisofs had a command line option to pass in a
character sequence for the ID String, and of course automatically update the
checksum.
That would allow me to make a completely automated build process that pulls
files from our version control system and creates a boot CD without any
manual intervention.
Thanks!
Torrey Hoffman
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
