Many thanks to Tom Blinn, that points me to the fact that what I'm trying
to do is unsupported:
> It's not a solvable problem. Each system believes that it controls the
> keyboard; neither system is designed to support sharing a keyboard (or
> a mouse) with other systems; each system has a different implementation
> for keyboard mappings and programs the keyboard to work as it expects;
> consequently, it's not a solvable problem.
>
> Putting it another way, neither Alpha systems using an SRM console nor
> Tru64 UNIX is designed to share a keyboard through a switch with a PC
> or any other system. What you are trying to do is unsupported.
>
> Tom
but Tom Brand - many thanks to you too - suggests a possible solution:
> Use a Raritan KVM switch instead <http://www.raritan.com>.
>
> These switches have separate processors to handle the keyboard/mouse
> for each host. This way, the host never realizes that it is
> connected to a KVM.
The original question follows.
Bye.
Alessandro
> Dear gurus,
>
> I've a keyboard mapping problem.
>
> I'm trying to use a console switch (Belkin OmniCube 2 port) connected
> to an AXP (AlphaStation 255) Digital Unix 4.0d and to a PC (WNT).
> After the boot of the Alpha all is right, but when i boot the PC, and
> I switch back to the Alpha, I found problems in some key
> (Alt and CapsLock behave like the Ctrl key, and Ctrl key like CapsLock,
> all middle-zone keys - with arrows - behave like the right-zone keys, with
> numbers, and so on).
> The same problem happens using the PC if I booted the Alpha after the PC
> (but with a different mapping).
>
> Anyone has found and solved this problem?
>
> Thank you in advance for your help.
>
> Alessandro
>
============================================================
Alessandro Brunengo
System and Network Administrator
Istituto Nazionale di Fisica Nucleare
Via Dodecaneso, 33
16146 - Genova - ITALY
tel. +39-010-3536317
fax. +39-010-310461
Received on Fri Feb 04 2000 - 08:14:19 NZDT