Re: SOLVED [gentoo-user] Win4Lin NumLock issue

2006-01-27 Thread Ron Bickers
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?

-- 
Ron
-- 
gentoo-user@gentoo.org mailing list



Re: SOLVED [gentoo-user] Win4Lin NumLock issue

2006-01-27 Thread Tom Smith
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



Re: SOLVED [gentoo-user] Win4Lin NumLock issue

2006-01-26 Thread Tom Smith
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.

Anyway, thought this might help others who may be having the same or
similar problems.

~ Tom

John Jolet wrote:

 that no longer exists.
 at least that's what I was told when I was trying to install...they
 said use vanilla sources and patch.

 On Dec 8, 2005, at 7:33 PM, Tom Smith wrote:

 I'm running Win4Lin Terminal Server 3... They may have fixed the
 problem in your version.
  
 How do I go about getting a win4lin-sources kernel? I was unable to
 one anywhere. Maybe I would have better luck with that.

 */Ron Bickers [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]/* wrote:

 On Thu December 8 2005 16:47, Tom Smith wrote:

  Sorry, my brain's mush... I'm just a whole lot of tired! The
 problem is
  that the Num Lock keypad doesn't work.

 I just tried it and it works for me. I'm running win4lin-5.1.1 (from
 portage) with Win98SE and my custom win4lin-sources-2.6.11-r11
 kernel, which
 is just a 2.6.11 gentoo-sources ebuild with the Win4Lin patches
 added.

 -- 
 Ron



-- 
gentoo-user@gentoo.org mailing list