The problem occurs when running Win4Lin *within* a VNC session. The same goes for QEMU.
I don't fully understand the difference between loading X at the console versus loading it at a virtual console, but I think that some keyboard mappings (among other things) are treated differently in the virtual console. When I first started playing around with WTS, over a year ago, I was using XDMCP on the server and Cygwin/X on the client--I had the exact same problem... The number keypad didn't work. So it's probably just that X doesn't load everything at the virtual console that is does at the real console. Ron Bickers wrote: >On Thu January 26 2006 17:41, Tom Smith wrote: > > > >>Sheesh, I finally found a solution to this very annoying problem (may >>also help the gentleman with the UK keyboard problem (Peter Ruskin?)... >>I actually discovered this while playing around with QEMU, it had the >>EXACT same problem as WTS. >> >> > >I just stopped using Win4Lin and started using QEMU (tired of kernel patching >and being so far behind gentoo-sources). The numlock key works fine in both >for me (sort of). The only thing wrong is that if it says it's on in the >Windows session, it's really off, and vice versa. The keypad numbers *do* >work as expected, though. Is there more to this problem that I'm missing? > > > -- gentoo-user@gentoo.org mailing list
