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