search for: force_cbio

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

Did you mean: force_cbios
2017 Mar 22
3
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...0xaa55, %bx jne 1f andw $1,%cx /* Bit 0 = fixed disk subset */ jz 1f With that jc changed to jnc you will invert the result of the EBIOS test and my qemu always has EBIOS. Download the resulting isohdpfx here: <http://www.ludd.ltu.se/~ams/tmp/isohdpfx.force_cbios.bin> Back to Thomas' debug prints. You can download my logger version of isohdpfx called isohdpfd here: <http://www.ludd.ltu.se/~ams/tmp/isohdpfd.bin> <http://www.ludd.ltu.se/~ams/tmp/isohdpfd.S> In the EBIOS case it will print: E<LBA0>/<LBA1>/<LBA2>/<...
2017 Mar 22
4
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...nge positions ! The effective read operation seems to use H/C = 32 , S/H = 63. The correct LBA would be addressed by H/C = 63 , S/H = 32. -------------------------------------------------------------------------- Reasoning: I have transplanted the "Force CBIOS" change from isohdpfx.force_cbios.bin to isohdpfd.bin. The Intel manual tells me that JNC is 0x73 (= 's') and JC is 0x72 ('r'). Looking for the instruction operand 0xaa55 in isohdpfd.bin leads me to the value 0x72 at byte position 56. So i patched isohdpfd.bin to let it force CBIOS by cp isohdpfd.bin isohdpfd.f...
2017 Mar 21
3
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
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 /*
2017 Mar 23
6
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
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