Hi, Jernej Simon?i? wrote:> As long as you have cygwin with development tools installed, it's just > ./configure && make.autotools magic. I myself have few clue of contemporary MS-Windows.> https://eternallybored.org/misc/xorriso/xorriso-1.4.2-cygwin32.zipThank you for flying xorriso.> > > oscdimg.exe -a -m -o -j1 > > > -bootdata:2#p0,e,bcd\isolinux\boot.bin#pEF,e,bcd\boot\efiboot.ima CD > > > sysresccd.isoI read https://technet.microsoft.com/en-us/library/hh824847.aspx to propose this translation xorriso -as mkisofs -v -J \ -b /isolinux/boot.bin \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -eltorito-alt-boot \ -e /boot/efiboot.ima \ -no-emul-boot \ -o sysresccd.iso \ CD Options -b and -e want the image file path in the ISO, not on hard disk. I assume that "CD\isolinux\boot.bin" will show up as "/isolinux/boot.bin". Please adjust to "/cd/isolinux/boot.bin" if i am wrong. For detail info see man xorrisofs You get Rock Ridge for free. If this makes undesired differences when mounting by Linux, you may prevent it by xorrisofs option --norock . (Or use mount(8) option -o "norock" to let Linux mount Joliet as next best name space.) Not translated: -a Displays the allocation summary for files and directories. -m Ignores the maximum size limit of an image. -o Optimizes storage by encoding duplicate files only once using a MD5 hashing algorithm to compare files. Option -a might be similar to xorriso command -find ... -exec report_lba. Option -m is a bit obscure to me. ISO 9660 max size is 2 exp 43 = 8 TiB. Option -o looks like an interesting feature. I wonder how oscdimg.exe knows that it has to apply boot-info-table patching to the boot.bin file. Have a nice day :) Thomas
On Monday, April 4, 2016, 22:01:32, Thomas Schmitt via Syslinux wrote:> Jernej Simon?i? wrote: >> As long as you have cygwin with development tools installed, it's just >> ./configure && make. > autotools magic. I myself have few clue of contemporary MS-Windows.Well, cygwin is just barely Windows :)>> https://eternallybored.org/misc/xorriso/xorriso-1.4.2-cygwin32.zip> Options -b and -e want the image file path in the ISO, not on hard disk. > I assume that "CD\isolinux\boot.bin" will show up as "/isolinux/boot.bin". > Please adjust to "/cd/isolinux/boot.bin" if i am wrong.I'll use isolinux.bin directly - oscdimg complained that it's too large, so I just dded the first 2048 bytes to boot.bin to get it to shut up.> Option -a might be similar to xorriso command -find ... -exec report_lba.-a is just because I'm curious - doesn't make a difference.> Option -m is a bit obscure to me. ISO 9660 max size is 2 exp 43 = 8 TiB.This one isn't actually necessary with my test, since the resulting ISO is small enough, but IIRC, without it oscdimg won't make ISOs larger than 700MB.> Option -o looks like an interesting feature.It's very useful when you have duplicate files.> I wonder how oscdimg.exe knows that it has to apply boot-info-table > patching to the boot.bin file.Probably doesn't - the resulting ISO doesn't boot in BIOS mode in VMWare (isolinux reports Image checksum error). In EFI mode both xorriso and osdcimg-produced ISO fail the same way - "Virtual machine encountered unhandled exception in firmware". -- < Jernej Simon?i? ><><><><>< http://eternallybored.org/ > No amount of genius can overcome a preoccupation with detail. -- Levy's Eighth Law of the Disillusionment of the True Liberal
> On Monday, April 4, 2016, 22:01:32, Thomas Schmitt via Syslinux wrote: > > > Jernej Simon?i? wrote: > >> As long as you have cygwin with development tools installed, it's just > >> ./configure && make.I am not opening a discussion here, but I feel compelled to warn some causal reader(s)... Again, that's not really "easy, for everyone". It might _sound_ easy, but, for some reason, people with (computer's) technical skills tend to forget that most users don't have them.> > autotools magic. I myself have few clue of contemporary MS-Windows. > > Well, cygwin is just barely Windows :) > > >> https://eternallybored.org/misc/xorriso/xorriso-1.4.2-cygwin32.zip > > > Options -b and -e want the image file path in the ISO, not on hard disk. > > I assume that "CD\isolinux\boot.bin" will show up as "/isolinux/boot.bin". > > Please adjust to "/cd/isolinux/boot.bin" if i am wrong. > > I'll use isolinux.bin directly - oscdimg complained that it's too > large, so I just dded the first 2048 bytes to boot.bin to get it to > shut up. >Of course, that will certainly make the BIOS boot fail (as it did). Whether it influences the resulting UEFI part when using oscdimg, I do not know.> > Option -a might be similar to xorriso command -find ... -exec report_lba. > > -a is just because I'm curious - doesn't make a difference. > > > Option -m is a bit obscure to me. ISO 9660 max size is 2 exp 43 = 8 TiB. > > This one isn't actually necessary with my test, since the resulting > ISO is small enough, but IIRC, without it oscdimg won't make ISOs > larger than 700MB. > > > Option -o looks like an interesting feature. > > It's very useful when you have duplicate files. >When testing / troubleshooting, KISS. We should try to avoid using parameters that are not essential for the relevant tests.> > I wonder how oscdimg.exe knows that it has to apply boot-info-table > > patching to the boot.bin file. > > Probably doesn't - the resulting ISO doesn't boot in BIOS mode in > VMWare (isolinux reports Image checksum error). In EFI mode both > xorriso and osdcimg-produced ISO fail the same way - "Virtual machine > encountered unhandled exception in firmware". >At any rate, Peter has confirmed what has been my guess all along. That also suggests the reason why there has been no public comments from Syslinux developers in any of our prior (and long) discussions about isohybrid, ISOLINUX or mkdiskimage, whether regarding BIOS or UEFI (and so, no proposed-patch implemented :( either). Regards, Ady.
Hi, Jernej Simon?i? wrote:> I'll use isolinux.bin directly - oscdimg complained that it's too > large, so I just dded the first 2048 bytes to boot.bin to get it to > shut up.That's quite a deadly surgery. It is true that BIOS shall only load 2 KB of the binary. But by help of the boot information table within this initial code piece isolinux.bin can locate the other bytes of its file, if not cut off. Well, the checksum in the unpatched boot info table was not valid anyway. I now remember a (german) discussion which involved Imgburn. It yielded that if you scroll up from http://forum.imgburn.com/index.php?/topic/6392-the-imgburn-functions/#entry66440 you get to a paragraph 3.3.2.3.4 "Bootable Disc". The shown settings together with enabled "[] Patch Boot Information Table" caused isolinux.bin to boot correctly. I do not see an option to choose platform id. So the shown version of Imgburn cannot mark a boot image for EFI. (But given the very detailed options which it offers, i assume that meanwhile such an option was added.)> "Virtual machine encountered unhandled exception in firmware".The SYSLINUX software must step heavily on EFI's toes after it woke up from CD-ROM media. Have a nice day :) Thomas