Hallo Herr Bernd Böckmann via Freedos-devel,

am Mittwoch, 16. April 2025 um 14:15 schrieben Sie:


>> Am 14.04.2025 um 23:10 schrieb Bernd Böckmann <bernd-free...@boeckmann.io>:
>> 
>> I will prepare such a kernel and make it available to Willi, but start with 
>> displaying 40:96 right before and after the menu selection, before and after 
>> the INT 16 calls are being made...

> I sent Willi an updated kernel which displays the 40:96 byte at various 
> stages of kernel initialization. Willi uploaded screenshots:

> https://nextcloud.iww.rwth-aachen.de/index.php/s/z9bqWBdom8A8nZz

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. it shows that the flag

  sometimes is misdetected to 00
  in most cases remains constant.
  sometimes - during menu selection - magically gets redetected as 10

besides what Bret already posted ("the extended keyboard gets detected by BIOS 
POST and remains constant") which I agree with 100%:

the photos don't tell, if Willi is letting the keyboard alone during POST, or ( 
as your mails suggest) hitting the keyboard
just to show that it doesn't work reliably.


> 40:96 is zero at early kernel stages, and is eventually changed to 10h when 
> navigating the FreeDOS boot menu or some specific
>  keys are pressed when the BIOS POSTs. The exact logic what causes 40:96 to 
> be changed is unclear to me.
>  Maybe some INT16 call triggers a BIOS internal detection logic.

40:96 is 01 most of the time, and remains at 01 - as it should.


> Not sure how to proceed. Maybe categorizing this as BIOS flaw
This looks definitively like a BIOS flaw.

>  and using mkeyb /E is the best option. 
I think I suggested this before.

> An even better option would be letting the user verify the keyboard type upon 
> FreeDOS installation
nope. millions of users have to think about 
   do you have an extended keyboard (whatever that is) Yes/No
because one buggy BIOS? absolutely NO!

> , and adapting fdauto.bat accordingly.
neither

> Bernd

Tom











_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to