>> Am 16.04.2025 um 21:32 schrieb tom ehlert via Freedos-devel >> <freedos-devel@lists.sourceforge.net>: >> >> before you posted "the flag gets cleared even before the first driver is >> loaded, depending on what gets selected in the FreeDOS >> boot menu (probably more which keys get pressed to achieve the selection)." >> >> the photoshow above doesn't show that.
> Yes, BEFORE! I did not say that the photo show proves this. With the added > debug output, additional insight was gained. You summarised it good, apart > from the assumption that the keyboard is mis-detected, which is likely but > not yet proven. Whatever "proven" means. in photo ..182916.jpg we have BEFORE PRECONFIG KEYBOARDFLAG 00 which is VERY early in the boot process. of course you could add this test before "Copyright ... GPL...", but I doubt this will make any difference. Software is deterministic (most of the times). > It might also be a corruption caused by the BIOS itself. we will never know if it's misdetected or corrupted - and it doesn't make a difference. > To rule out the unlikely situation that 40:96 gets corrupted by the kernel, I > also will inspect this value at the boot loader stage after Easter. > Interestingly, under a directly booted lDebug, it shows as 10h. Proves what? 10h is detected often enough under normal circumstances. You have to test lDebug 20 times to make any conclusions. And also treat the keyboard similar as when booting normally. > But lDebug may do something with INT16 before dumping the value (although the > dump is done via the LDEBUG.SLD startup file)... whatever LDEBUG.SLD does. Report the results. Tom _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
