Persistent keyboard problem

[silavgroup]

Persistent problem with Win4Lin, and I am using current 1997 version.
This problem has been around and reported on for a very long time now.

The super key is reconfigured in the Host OS and never returned to
it's previous state after launching a console and running a session.

The problem is in Win4Lin and whatever it does to trap the mouse and
keyboard because the problem does not exist in KVM only installs of
Windows.

As you know in KVM alt crtl releases the mouse and keyboard to the
native host os.
I commend VB for trying to make a more fluid system, but by trapping
the operations and some how changing makes for some serious problems
as they exist currently, because a reboot is required to get your
keyboard functionality, and that is not more fluid, it is very tedious
and a real pain.

Is there an option that I am missing in properties to allow something
different to happen, such as is done with native KVM so that issue can
be resolved. This does not affect floating apps, because obviously the
way Win4Lin handles the keyboard is somewhat different as the super
key is not needed with floating apps.

Thank you.

[silavgroup]

PS I have also logged this with Tech Support, again. Just wondering if
anyone here has a word around or answer as last time I complained
about this they did not have anything.

[silavgroup]

There doesn't appear to be a way to add solved to the title of the
post, but this problem has been solved in release .2019.
Tech Support was right on top of my request and those guys in
engeenering had already been working on the fix and voila.
Again thanks for the good work.