wrote:Example: For the file UZ.KL (keyboard layout for Uzbekistan) specify
"keyboardlayout=uz" in the DOSBox configuration file.
The integration of keyboard layout packages (like keybrd2.sys) works similar.
Alas, keyboardlayout=keybrd2 fails and keyboardlayout=keybrd2.sys gets DOSBox stuck. keyb.com keybrd2 and keyb.com keybrd2.sys fail as well.
So how can one load something from those sys files?
Thanks!
What do you really want to do?
I want, for example, the command keyb uz to require keybrd3.sys and not uz.kl.
Put keybrd3.sys into the directory where you are when you execute keyb.com, or into the directory of your dosbox.exe
If I put all four sys files, does DOSBox just look for UZ in all of them until it finds it?
Sort of. There's a priority of the .kl over the .sys (keyboard/keybrd2/keybrd3) over the internal-compiled (.sys import) ones.
No, I meant if no KL files are around does it look for UZ inside keyboard.sys, then in keybrd2.sys, then in keybrd3.sys and finally in keybrd4.sys?
wrote:the .sys (keyboard/keybrd2/keybrd3) over the internal-compiled (.sys import) ones.
What's the latter?
I meant if no KL files are around does it look for UZ inside keyboard.sys, then in keybrd2.sys, then in keybrd3.sys and finally in keybrd4.sys?
Yes, see what I said. Except that keybrd4.sys won't be searched.
What's the latter?
the .sys files compiled into dosbox.
wrote:Except that keybrd4.sys won't be searched.
Why not?
Check the sources.
I take your word that the sources also ignore keybrd4.sys. I just wonder why.
Didn't exist.