search for: f000efc7

...gh memory Code 1656, meminfo 276, cmdline 66, stack 512 Total size needed = 2510 bytes, allocating 3K Old dos memory at 0x9f800 (map says 0xa0000), loading at 0x9ec00 1588: 0xffff 15E801: 0x3c00 0x07dea INT 13 08: Success, count = 1, BPT = 0000:0000 old: int13 = f0005c6f int15 = f000f859 int1e = f000efc7 new: int13 = 9ec0000a int15 = 9ec0038c int1e = f000efc7 Loading boot sector... booting... Starting PC DOS... Though, when using any post-3.83 version of MEMDISK, the same disk image results in an unfavorable state. Notably, after booting the image, the system's SATA drive is not visible to t...

It appears that the 3.74 completely broke the "keeppxe" directive -- not due to the command-line parser, but due to mishandling of the flag later. I consider this to be severe enough to do a short-cycle 3.75. As a result, I would like help with: a) are there any other bugs that snuck through? b) once I have a 3.75-pre1, I would really appreciate help testing it. The goal is to have

...66, stack 512 Total size needed = 2598 bytes, allocating 3K Old dos memory at 0x9fc00 (map says 0xa0000), loading at 0x9f000 1588: 0xffff 15E801: 0x3c00 0x7dc3 INT 13 08: Success, count = 1, BPT = 0000:0000 Drive probing gives drive shift limit: 0x82 old: int13 = f0005c6f int15 = f000f859 int1e = f000efc7 new: int13 = 9f00000a int15 = 9f0003ba int1e = f000efc7 Loading boot sector... press any key to boot... No 'lost drive' message was reported and the internal hard drive is now visible to the booted environment. I also tried (only on the OptiPlex GX280, at this time) this debug version with...