similar to: "isolinux.bin missing or corrupt" when booting USB flash drive in old PC

Hi, for some reason David always omits the Cc: to this list. He has now reported to Martin and me the outcome of the latest two MBR test proposals. - His BIOS announces no LBA addressing but another extra feature. This lead to unexpected success in one of David's tests. - The newest fix proposal by Martin is a full success ! Distros which produce isohybrid should consider to already

Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read

CC:ing syslinux David Christensen reports that my latest isohdpfd.bin reported C, thus it failed early (carry set) in finding an EBIOS. My interpretation is that it must corrupt CX so isolinux is fooled into trying EBIOS first. So, again David, can you please try this one: <http://www.ludd.ltu.se/~ams/tmp/isodavid.tgz> To keep your (our?) spirits up I've named it of you. It

On Tue, Mar 21, 2017 at 09:03:35AM +0100, Thomas Schmitt via Syslinux wrote: > I think we should offer David a binary which he can combine with > the MBR of the ISO and the image with the recognizable blocks. > I will later today upload a binary version of my block producer > and post the URL. > > The combination will be: > 432 bytes from Martin's MBR > 80 bytes

On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: > isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. > Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx

CC:ing syslinux. Thanks for testing David. On Thu, Mar 23, 2017 at 05:23:51PM -0700, David Christensen wrote: > Trying isohdpfd.bin: ... > Boot it in D865GBFLK Pentium 4 3.4E GHz -- I see a screenful of information, > with "Key?" at the bottom (see attached picture IMG_1578-r.JPG). > > > When I press a key, I see the following message at the bottom and the >

> On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > > Some of the things you should / could (re)test / (re)try: > > > > _ Verify the md5sum of the ISO image. > > SHA256 verified for downloaded image and for contents of USB flash drive > (see below). > > > > _ Is this particular USB device _still_ capable of booting newer > > computers? >

David Christensen wrote: > This is how I prepared an ADATA USB Flash Drive 4 GB: ... install-mbr /dev/sdb ... [Rest of very clear description snipped.] What's that? That desn't exist in the Debian I'm running. Otherwise you gave a very good description of what you're doing. >From another message: > Please provide a URL for documentation that explains how to build a >

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

Thomas Schmitt wrote: > (I could need a reference document for the assembler language in isohdpfx.S. > Does anybody know a good one ?) "info gas", in particular you want to read the chapter named "i386-Dependent". Then you'd want the x86 manuals from amd or intel for the instructions themselves but they are documented backwards. -- MartinS

David Christensen wrote: > It looks like the call to "error" (line 276) is made if a summation of > the bytes in the first four sectors of a partition don't add up to > HYBRID_MAGIC (?). HYBRID_MAGIC = 0x7078c0fb isolinux_hybrid_signature = 0x7c00+64 ... cmpl $HYBRID_MAGIC,(isolinux_hybrid_signature) jne bad_signature ... bad_signature: call error .ascii

David Christensen wrote: > What syntax is used in isohdpfx.S -- it doesn't match my Intel gas syntax. "info gas machine i386 i386-syn i386-var" if you have the gas manual installed. -- MartinS

On 03/19/2017 09:42 PM, Martin Str|mberg via Syslinux wrote: > David Christensen wrote: >> This is how I prepared an ADATA USB Flash Drive 4 GB: > ... > install-mbr /dev/sdb > ... > [Rest of very clear description snipped.] > > What's that? That desn't exist in the Debian I'm running. > Otherwise you gave a very good description of what you're doing.

On Fri, Mar 24, 2017 at 2:55 PM, Martin Str|mberg via Syslinux <syslinux at zytor.com> wrote: > On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: >> isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. >> Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" >> could be set. >>

Thomas Schmitt wrote: > Now looking deeply impressed at the 4600+ pages pile of > > https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf ... > It seems that at page 571 begins the reference of instructions. Up to > page 1120. Ouch. Ah, it mostly just rubbish since they "invented" MMX/SSE*/AVX. Just long sequences of almost

Hi, David Christensen wrote: > I see the source code for the error message: > .ascii "isolinux.bin missing or corrupt.\r\n" The riddle is why the MBR code does not get to see the expected bytes. > Figuring out why debian-8.7.1-i386-xfce-CD-1.iso works on CD, but doesn't > work on USB, The immediate reason is that from CD the program isolinux.bin is loaded

Hi, MartinS wrote: > Sigh. Ok. I deserve that. I was stubbornly looking at the structure of the documentation rather than at the documented sequence of instruction parameters. I ponder whether it would be possible to create a diagnostic MBR which does not necessarily have to boot but rather tells what the isohybrid MBR would perceive: Presence of partition table, EBIOS or CBIOS, block

Hi, Ady wrote: > http://repo.or.cz/syslinux.git/tree/HEAD:/diag > "handoff.bin This does not look like it would tell much of the properties in question. Nevertheless its print functions might be of interest for an isohybrid diagnostic MBR. > and at least 2 geodsp*.{bin,img(gz)} I am now reading http://repo.or.cz/syslinux.git/blob/HEAD:/diag/geodsp/README These programs

Hi, Ady wrote: > In the last few years, ISOLINUX has received very low attention, both > upstream and downstream. Nevertheless the well established Linux distros use it for their ISOs. Most have adopted mjg's isohybrid --uefi layout. Only SuSE does it different. So for me with my xorriso hat on, ISOLINUX is as an important partner as is GRUB. > So I' am about to (attempt to)