search for: chddisolinux

...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 > computer stops: > > ISOLINUX 6.03 20150819 CHDDisolinux: Image checksum error, sorry... > > > Trying isohdpfc.bin: ... > Boot it in D865GBFLK Pentium 4 3.4E GHz -- I see a screenful of information, > with "Key?" at the bottom. Is it exactly the same numbers as in the picture you attached for the isohdpfd.bin boot? > When...

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

...ture IMG_1578-r.JPG: The data block shown is the correct start block of isolinux.bin. Whatever happened next, it is not due to failure to address the right block. (I did not compare byte by byte. But two start lines , two end lines, and magic number FBC07870 match.) > ISOLINUX 6.03 20150819 CHDDisolinux: Image checksum error, sorry... This error message stems from isolinux.bin, not from the MBR. So we really ended up in the running boot image program. The checksum is tested with all isolinux.bin starts. From CD too. It belongs to the Boot Info Table feature inside isolinux.bin (see "man mki...

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