|
Post by Jos on Mar 11, 2021 17:13:22 GMT 1
vDos doesn’t emulate the keyboard INT 9. So hooking into that (dummy) interrupt code is useless since it won’t be executed.
Changing the bitmap font is also futile since vDos uses a TTF font. You can change the codepage (ASCII character translation) by the CHCP command. The keyboard layout is dictated by Windows.
Jos
|
|
|
Post by adim on Mar 12, 2021 8:31:23 GMT 1
Thank you very much Jos!
I've forgotten to set the right code page
as that was unnecessary for the original program
Have a nice weekend!
|
|
|
Post by harijono on Dec 19, 2021 11:59:38 GMT 1
in Win7 Ultimate, This is not an admin problem but The following program has performed an action that requires Windows to temporary change the color scheme to Windows 7 Basic. Warn from windows after run vDos: The color sheme has been changed to Windows 7 Basic. A running program isn't compatible with certain visual elements of Windows.
|
|
|
Post by Jos on Dec 19, 2021 12:23:06 GMT 1
You don’t get the “vDos should not run elevated”. Instead Windows complains about vDos performing some action that requires a change of the color scheme?
Any idea what that action would be. I don’t, and this wasn’t reported before…
The Win7 Ultimate color scheme is perhaps set to 16 bit color depth?
Jos
|
|