search for: bin20170324

Displaying 4 results from an estimated 4 matches for "bin20170324".

2017 Mar 26
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...(but not all) "00s" in place of the "90s"? (Considering that these images are generated mostly by xorriso, perhaps Thomas might be able to answer?) To ilustrate what I mean (and what I'm trying to understand), I am presenting here the first part of Martin's isolinux.bin20170324 and the respective part from the original isohyrbid image from Debian (note: the strange format I am presenting them is intentional): Martin's: 33 ED 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 Original Debian's bin: 45 52 08 00 00 00...
2017 Mar 26
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...combinations, is there really one generic "receipt" that can be provided so as to help users (other than those using the specific Debian ISO image that was tested by David)? We seem to be suggesting to just dd' the first 432 bytes of their USB devices with Martin's isohybrid .bin20170324 (overwriting their first 432 bytes that were previously written when they used dd with their original isohybrid image on the same USB device). Would this be a generic receipt, independently of: _ the original size of the original isohybrid image? _ whichever CHS geometry that was used for the...
2017 Mar 26
2
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi, Gene Cumm wrote: > it seems the stack format got > set, changed, then mostly reverted back, with this code being the last > piece missing from 2009. The commit to isohdpfx.S of 2009-05-31 looks incomplete. The sequence of the stack pointers was swapped, but the sequence of stack pushes was not.
2017 Mar 26
2
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition