To investigate a isohybrided ubuntu-14.10-desktop-amd64.iso, both MBR and GPT partitions loopback loop ubuntu.iso ls (loop) (loop,msdos2) (loop,apple2) (loop,apple2) ls (loop,msdos2)efiboot bootx64.efi grubx64.efi The file ubuntu.iso hexedited, gpt deleted, MBR boot code deleted.One non active partiton entry and Magic Bytes exist still: loopback mounts the EFI image at (loop,msdos2).
Yes, thats a good guess: Both approaches works, ls (loop,msdos2)efiboot is possible: With CHS values 1C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 1D0 FF FF EF FE FF FF D0 56 22 00 C0 11 00 00 00 00 1E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA Zeroed CHS values 1C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1D0 00 00 EF 00 00 00 D0 56 22 00 C0 11 00 00 00 00 1E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA. It seems same original ifu.iso. The batch should work fine however for the more normal Acronis.isos that have a plain superfloppy image. Acronis 2014 Zip File And PostI have not that particular ifu image, so I have nothing to test it with, you could extract from it Sectors 0-39, compress them in a zip file and post the archive. Using dsfo that would be: dsfo ifu.iso 0 81920 ifysectors039.bin Wonko I can not attach file on forum. Try loopback loopback ElTorito (loop)10813224 set root(ElTorito,msdos1) and I got error disk ElTorito,msdos1 not found. The idea by cdob (and what the batch should do) is to modify the whole.iso adding to it a iso-hybrid MBR with the mapping to the volume. So, you want to map the whole.iso as loopback device, like: loopback ElTorito ifu.iso. ![]() Also, I was try unpack ifu.iso, keep only bootx64.efi and ifu.ini. Oh good, it can use without iso file. Yes, the booting is the difficult part. Time to try previous question menuentry Acronis True Image Home 2015 ISO ElTorito. I mean, if we use the little batch, we get a isohybrided.iso with the partition entry in first slot, aka msdos1 in the stupid GRUB2 syntax, (OK) but if next step is anyway that of chainloading a kernel and a initrd (that can be called dat9.datdat8.dat but also - say - dat13.datdat12.dat) so there is anyway the need to manually find which file is the actual kernel and initrd, there is IMHO very little practical advantage in having. Vmware: windows 8x64; uefi -All work (ati15.iso; add12.iso) Vmware: windows 8(x32, x64); legacy bios - Ati15.iso: ok - Add12.iso: not work All test with grub2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2021
Categories |