DOS ain't dead

Debug/X v2.50, JemmDbg, 386SWAT, Keyboard.sys (Developers)

posted by Japheth , Germany (South), 14.05.2024, 08:44

> I don't think you're going to find an easy way to do this. Keyboard
> layouts are VERY complicated and confusing. E.g., you need to worry about
> things like code pages and keyboard modes. Some keyboards have a Latin
> Mode in addition to a "native" mode (Cyrillic, Hebrew, Greek, etc.).

Seems you didn't fully read my post:

> The debugger doesn't need any sophisticated tables, it doesn't handle file or
> file names, it's just the alphanumeric keys, '#','$','%', BS and ENTER.

Without the need for "dead keys", extended keys and the like, the situation is not longer "VERY complicated". Actually, the approach that I first considered seams feasible: to trap keyboard ports 0x60 and 0x64, then feed the keyboard driver with a bunch of make codes/break codes combinations and see what it makes out of that.

---
MS-DOS forever!

Complete thread:

• Debug/X v2.50, JDeb386, 386SWAT, Keyboard.sys - Japheth, 13.05.2024, 13:26 (Developers)
  • Debug/X v2.50, JemmDbg, 386SWAT, Keyboard.sys - tom, 13.05.2024, 13:50
    • Debug/X v2.50, JemmDbg, 386SWAT, Keyboard.sys - Japheth, 17.05.2024, 18:44
      • MKeyB & MS SmartDrv - Japheth, 22.05.2024, 12:54
  • Debug/X v2.50, JemmDbg, 386SWAT, Keyboard.sys - bretjohn, 13.05.2024, 19:20
    • Debug/X v2.50, JemmDbg, 386SWAT, Keyboard.sys - Japheth, 14.05.2024, 08:44
      • Debug/X v2.50, JemmDbg, 386SWAT, Keyboard.sys - bretjohn, 14.05.2024, 16:04
  • Debug/X v2.50 & JDeb386 released - Japheth, 03.06.2024, 07:59