search for: isohybrid_mbr

Thomas Schmitt wrote: > I still don't get the "backwards" aspect. (Probably not enough background > knowledge.) Sigh. inst x, y gas use x and possibly y, operates according to inst and puts the result in y. Intel lives with the misconception this should mean use y and possibly x, operate according to inst and put the result in x. If you come from gas background the first

...sohybrid MBR would perceive: Presence of partition table, EBIOS or CBIOS, block address used with INT 13, content of the block read by the first INT 13, ... One could preserve the isohybrid MBR of an ISO and replace it by the diagnostic one for testing purposes: dd if=/dev/sdc bs=1 count=512 of=isohybrid_mbr.bin dd of=/dev/sdc bs=1 count=432 if=diagnostic_mbr_code.bin The diagnostic MBR should only use 432 bytes because at byte 432 to 435 of the isohybrid MBR there is the 512-byte-block address of file isolinux.bin, which was patched in by isohybrid or xorriso. So the code would be able to work wit...

...ce of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... > > One could preserve the isohybrid MBR of an ISO and replace it by > the diagnostic one for testing purposes: > > dd if=/dev/sdc bs=1 count=512 of=isohybrid_mbr.bin > > dd of=/dev/sdc bs=1 count=432 if=diagnostic_mbr_code.bin > > The diagnostic MBR should only use 432 bytes because at byte 432 > to 435 of the isohybrid MBR there is the 512-byte-block address of > file isolinux.bin, which was patched in by isohybrid or xorriso. > So...