TheRave Posted October 9, 2010 Posted October 9, 2010 (edited) Its not possible for me to create a bootable grub2 cd with imgburn. I build the iso image and test it with a vmware and i get only a black screen at boot. I take a grub2 image called super_grub_disk_hybrid-1.98s1.iso from here: http://developer.berlios.de/project/showfiles.php?group_id=10921 and take the grub folder from the iso for my data cd. In the grub folder is a file called eltorito.img. I take this as bootimage with options no emu, load segment 07C0 and 1 sector. With cdrtools this works immediately - no problem, but with imgburn this doesn´t work. Some infos from isoinfo.exe: Original file: D:\Downloads>isoinfo.exe -d -i super_grub_disk_hybrid-1.98s1.iso CD-ROM is in ISO 9660 format System id: GNU Volume id: CDROM Volume set id: Publisher id: Data preparer id: Application id: GRUB ISO 9660 filesystem builder Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 705 El Torito VD version 1 found, boot catalog is in sector 40 NO Joliet present SUSP signatures version 1 found Rock Ridge signatures version 1 found Rock Ridge id 'RRIP_1991A' Eltorito validation header: Hid 1 Arch 0 (x86) ID '' Cksum AA 55 OK Key 55 AA Eltorito defaultboot header: Bootid 88 (bootable) Boot media 0 (No Emulation Boot) Load segment 0 Sys type 0 Nsect 1 Bootoff A2 162 ----------------------------------------------------------------------------- created iso with cdrtools D:\Downloads>isoinfo.exe -d -i cdrtools.iso CD-ROM is in ISO 9660 format System id: Volume id: CD Volume set id: Publisher id: Data preparer id: Application id: Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 139998 El Torito VD version 1 found, boot catalog is in sector 34 CD-ROM uses ISO 9660:1999 relaxed format NO Joliet present No SUSP/Rock Ridge present Eltorito validation header: Hid 1 Arch 0 (x86) ' ID ' Cksum 9D 55 OK Key 55 AA Eltorito defaultboot header: Bootid 88 (bootable) Boot media 0 (No Emulation Boot) Load segment 0 Sys type 0 Nsect 1 Bootoff 23 35 --------------------------------------------------------------------------------- created iso with imgburn D:\Downloads>isoinfo.exe -d -i imgburn.iso CD-ROM is in ISO 9660 format System id: GNU Volume id: CDROM Volume set id: UNDEFINED Publisher id: Data preparer id: Application id: Copyright File id: Abstract File id: Bibliographic File id: Volume set size is: 1 Volume set sequence number is: 1 Logical block size is: 2048 Volume size is: 139866 El Torito VD version 1 found, boot catalog is in sector 19 NO Joliet present No SUSP/Rock Ridge present Eltorito validation header: Hid 1 Arch 0 (x86) ID 'Unknown' Cksum 0D 01 OK Key 55 AA Eltorito defaultboot header: Bootid 88 (bootable) Boot media 0 (No Emulation Boot) Load segment 0 Sys type 0 Nsect 1 Bootoff 14 20 Edited October 9, 2010 by TheRave
LIGHTNING UK! Posted October 9, 2010 Posted October 9, 2010 Relax the ISO9660 file system restrictions. It uses the most restrictive by default and you probably need things like longer file names, ansi character set etc.
TheRave Posted October 9, 2010 Author Posted October 9, 2010 (edited) Relax the ISO9660 file system restrictions. It uses the most restrictive by default and you probably need things like longer file names, ansi character set etc. But on the iso is only the grub folder and a little file for testing. I have played a lot of time with the options. I set iso Level to x, tried different character sets and ticker on all checkboxes under 9660 restrictions. Nothing helps. VMWare won´t boot from imgburn.iso. I have also disabled RockRidge in cdrtools.iso to see how it works and the iso booting also without RockRidge. Edited October 9, 2010 by TheRave
LIGHTNING UK! Posted October 9, 2010 Posted October 9, 2010 Ah sorry, I see the problem. Your boot image is part of another file and the boot image should actually be pointed to the data of that file rather than be stored as its own copy. Not only that, the eltorito.img needs its 'boot information table' patched. Currently, this is hardcoded to be done with isolinux.bin but nothing else. I've already tweaked the code to search the image content for a file matching the boot image one. If it finds one, it'll point the boot image file at the file within the image rather than storing the data twice. I will add a checkbox to enable patching of the 'boot information table' within any boot image rather than just the hardcoded 'isolinux.bin'.
TheRave Posted October 9, 2010 Author Posted October 9, 2010 Yes i have seen with bbie in the supergrub-iso the image1.bin. I have also tried to take this as "bootimage" file. Also without success. So i have take eltorito.img from the grub folder. Is it possible to extract the eltorito.img? And i have tried to build the iso with mkisofs without the "-boot-info-table" option now . And i see there the same problem now. :-) Thanks for your help.
Recommended Posts