Re: SOLVED [gentoo-user] Win4Lin NumLock issue

[Peter Ruskin]

On Thursday 26 January 2006 22: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.
>
> The problem appears to be an X keyboard mapping issue. In my
> situation, the users only use the number keypad for entering
> numbers. So I created the following
>
> ~/.Xmodmap:
> keycode 79=7
> keycode 80=8
> keycode 81=9
> keycode 83=4
> keycode 84=5
> keycode 85=6
> keycode 87=1
> keycode 88=2
> keycode 89=3
> keycode 90=0
> keycode 91=period
> keycode 86 = plus
> keycode 77 =
>
> This essentially hard codes the number keypad and (theoretically)
> disables the Num Lock button ("keycode 77")--theoretically
> because the number keypad now works perfectly but only if the Num
> Lock LED is ON on the client side (Windows, in my case).
>
> I still don't fully understand why or how this works because the
> number keypad has always worked within X during a VNC session,
> problems arose only during a Win4Lin or QEMU session and only
> within those sessions.
>
OK, that works here but it's a crude workaround.  I only use the 
NumPad keys for numbers too but I don't like this solution.

My solution is to to not use Win4LinPro or qemu - you can get 
Parallels Workstation for $49 and it's almost as good as vmware.

-- 
Peter
========================================================================
Gentoo Linux: Portage 2.0.54.	kernel-2.6.15-gentoo-r1.
i686 AMD Athlon(tm) XP 3200+.		gcc(GCC): 3.4.5.
KDE: 3.5.0.				Qt: 3.3.4.
========================================================================
-- 
gentoo-user@g.o mailing list