search for: getlinsec_ebios

...gt; diff -u -r1.181 ldlinux.asm > --- ldlinux.asm 18 Jan 2005 13:13:50 -0000 1.181 > +++ ldlinux.asm 3 Aug 2005 00:28:18 -0000 > @@ -328,7 +328,7 @@ > ; > ; We have EDD support... > ; > - mov byte [getlinsec.jmp+1],getlinsec_ebios-(getlinsec.jmp+2) > + ; mov byte [getlinsec.jmp+1],getlinsec_ebios-(getlinsec.jmp+2) > .noedd: I noticed the same problem and the above patch seems to fix it. I don't currently have a DOS or WIN system installed, and have a 128MB USB flash drive, where I noticed the proble...

This version cleans up the Ethersel (PCI config probing) changes I have been iterating with Alex Heinz. It's not the same code (so please test, especially Alex), but it should work the same. As before, if you have a machine for which 2.13 worked and 3.0x hasn't worked, please test this version too. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi, C/H/S addressing and reading of first block seems to be ok in isohdpfd.bin. The main suspect for the failure of the attempt with isohdpfd.bin is the number or content of the blocks read after the first one. But i have no clue why isohdpfc.bin should do better than isohdpfd.bin. They differ just by one instruction (JC = 0x72 versus JMP = 0xEB) which both are performed before the reading and

...------------------------ If this is indeed the wrong sequence in isolinux.bin then the riddle arises why the second try of David with isohdpfc.bin succeeded. And why do our virtual BIOSes work ? Don't they get the fake EBIOS flag ? Can it be that isolinux.bin unconditionally first tries "getlinsec_ebios" before it defaults to "getlinsec_cbios" which is a consumer of "bsSecPerTrack" and "bsHeads" ? How can so few bytes impose so many riddles ? Have a nice day :) Thomas