>> how should a KEYB scancode->keycode driver react to copdepage
>> changes, and how are these communictated?
> Well, first of all the keyboard driver should detect the current
> Code Page on installation and not just assume one.
codepage is a display thing, essentially it's the table how to con
On 07/10/2021 15:43, tom ehlert wrote:
DISPLAY.SYS calls INT 2F.AD81h when the Code Page is changed to
inform KEYB so it can change its mapping.
please provide an example where this is necessary AND plausible.
In Poland, there were a few codepages used during the DOS era. The two
main ones we
Hallo Herr Mateusz Viste,
am Donnerstag, 7. Oktober 2021 um 17:00 schrieben Sie:
> On 07/10/2021 15:43, tom ehlert wrote:
>>> DISPLAY.SYS calls INT 2F.AD81h when the Code Page is changed to
>>> inform KEYB so it can change its mapping.
>> please provide an example where this is necessary AND plau
> codepage is a display thing, essentially it's the table how to
> convert 8-bit bytes into a visable character set, and mostly
> unrelated to the way the keyboard driver converts scancodes into
> bytes.
The Code Page and the Keyboard layout are not unrelated at all -- they are
HIGHLY related. M
> Plus, you can have situations where there is not a unique set of
> ASCII/scan code combinations. E.g., ASCII 13 (Carriage Return) can
> be generated by Enter, Grey Enter (on the NumPad), Ctrl-M, Alt-013,
> and maybe other ways too. If the user tells me to "type" an ASCII 13, which
> key(s) d
On 07/10/2021 18:47, tom ehlert wrote:
were these 2 layouts dynamically switchable (and actually
switched)
They were actually not switchable, mainly due to their implementation:
CP852 was provided by "mode con cp" through MS-DOS, while the Mazovia
codepage was usually loaded through a custom
> On 07/10/2021 18:47, tom ehlert wrote:
>> were these 2 layouts dynamically switchable (and actually
>> switched)
> They were actually not switchable, mainly due to their implementation:
> CP852 was provided by "mode con cp" through MS-DOS, while the Mazovia
> codepage was usually loaded through
> the user told you to type ASCII 13. why don't you 'type' 0x13 using
> INT16, AH=05h? use scancode 0x02 and send complains to me?
I'm not actually "complaining" about MKEYB since KEYB is available and does
things "correctly" -- so there's no need for me to use MKEYB. In fact, as a
user, I liv