Page 1 of 1
Win98 guest function keys problem
Posted: 8. Jan 2015, 11:24
by AntonK
My PC is ASUS zenbook 64 bit with Win7 64 bit.
I have intsalled a VMvirualBox 4.3.20 with extensions pack 4.3.20r96996.
Guest OS is Win98, my application run unter win98/DOS7 and need function codes F1 to F12.
In this configuration I can't use it, because a keypress send a wrong code(for F1: ';', F2: '<' etc.).
In the past run my Application unter DOS7 with config.sys and ANSI.SYS in Fullscreen as console application.
What should I do to use my application with F1 to F12.
Thank You in advance
Anton
Re: Win98 guest function keys problem
Posted: 8. Jan 2015, 21:02
by scottgus1
A quick search tells me an Asus Zenbook is a laptop. Most laptops combine the F# keys with the manufacturer's desired commands, like volume up/down, wifi on/off, screen brightness, mute, etc. The laptops usually default to having the manufacturer's commands as the default actions when the combined key is pressed, and one has to hold down another key, like "Fn" on my Lenovo laptop, to get the F# function key. Have you tried to see if that situation is getting in the way of your guest?
If that's the case, most manufacturers have a way to switch the default action to be the F#, and the manufacturer's commands would need the "Fn" key pressed. If you find you always need the F# as default, find the utility to switch the action on your Zenbook.
Re: Win98 guest function keys problem
Posted: 10. Jan 2015, 11:49
by AntonK
Hello scottgus1
Thank you for pointing out this possibility, I have not thought of.
I will first write a small test program to find out what for
code is sent when pressing F1..F12.
Thanks again
Anton
Re: Win98 guest function keys problem
Posted: 10. Jan 2015, 17:18
by AntonK
Hello scottgus1
I have solved the problem. In the virtual
Windows directory is the config.nt.
Here you just add:
device =% systemroot% \ system32 \ ansi.sys
and now run all function keys.
best regards
Anton
Re: Win98 guest function keys problem
Posted: 12. Jan 2015, 14:50
by scottgus1
Never would have thought of that. Good troubleshooting, Anton!