Conference turris::microvax

    I seem to remember the VAXstation selftest failing when the system
    was missing a keyboard. I would guess you can't use the newer
    keyboards. I think the mouse connector is physically different too.
    
    jim
    

:    My customer wants to rebuild his ops area, he would like to remove a
:    number of his Digital keyboards and Mice and replace them with a switch
:    system and a single PC keyboard and mouse.

   Older systems (and probably various newer systems) will not reboot
   if the keyboard is disconnected.  Further, the presence (or absence)
   of the keyboard is one of the factors that determines the licensing
   status on certain classes of systems -- removal of the keyboard can
   turn a workstation into a server, and causes a requirement for server
   licenses.

:    The Digital keyboards and mice currently connect to a range of
:    Vaxstations the systems provide graphical representations of that
:    systems services.

   I'd look at a package such as the VAXcluster console (VCS) package.
   (Now POLYCENTER CONSOLE MANAGER, or some such...)
    
:    can you switch a DEC keyboard/mouse on and off a system without
:    affecting its operation. IE is there any timeout on the driver etc.
:    
:    Is a PC mouse compatable with a dec mouse with clocking etc.

   AlphaStation keyboards and mice use PC protocols and PC signalling.
   Prior to this series of systems, the keyboards and mice are quite
   incompatible.

    Ed,
    
    As has been said, VAXstations etc don't use PC keyboards and mice. If
    your customer really wants multiple systems sharing one keyboard and
    mouse via a "switch box" it can be done but it isn't necessarily
    supported by Digital. If your customer has real money for this kind of
    thing and isn't just flying a kite, you might want to call Access
    Keyboards in Reading, who have done this kind of thing in the past.
    
    Then again, PolyCentre Console Manager is probably a more sensible way
    of achieving a similar result, with 100% Digital support...
    
    regards
    john

    
    Thanks everyone,
    
    VCS is not an option, as not only does he want to swich between
    Vaxstations but also other vendors systems. They are talking about 
    fitting dummy loads onto the keyboard and mouse ports to cure the 
    self test problem.
    
    Thanks for the Access name I shall pass that to the customer.
    
    Regards
    EDK

I never thought there was a restriction in VCS to control only Digital systems.
If the system has a character cell console port, VCS should be able to deal with
it as well.  PLUS, you get lots of benefits with VCS such as a central log of
console messages and such.

Oh well...

	David

    Sorry your right...
    
    Polycenter Console Manager can manage any system or device on any
    platform that can send ASCII data over an RS232 line, has an EIA
    console port , and supports XON/XOFF and I?O buffering according to 
    the Poly center solutions guide. That will teach me to RTFM...
    
    the customer does not however wish to "manage" the systems. What he
    wants is a number of displays that provide him with the graphic
    displays that each system outputs. he then wants to be able to swith
    between the  displays interacting with each using a Microsoft mouse
    and keyboard, even though it may be a Digital Vaxstation providing the
    output or a PC.
    
    Is the mouse on a Vaxstation a serial connection ?
    
    Are there drivers that will allow Microsoft keyboards and Mice to be
    used on DEC equipment, or can DEC keyboards and Mice be adapted to use
    on PC's.
    
    Many thanks 
    EDK 
     

   If the customer is asking these questions in this particular fashion,
   I don't recommend they try the hack-the-keyboard-signalling approach.

:    Are there drivers that will allow Microsoft keyboards and Mice to be
:    used on DEC equipment, or can DEC keyboards and Mice be adapted to use
:    on PC's.

   The signalling and wiring protocols are completely incompatible with
   the LK101, LK201, and LK401 series -- the traditional banana-plug and
   RJ-plug keyboards.  The newer DIN-plug LK250, LK450, LK46x, and LK47x
   keyboards used on the AlphaStation and AlphaServer series are largely
   (entirely?) compatible.  (But I still don't recommend `hot-plugging'
   the keyboards -- the host's view of the keyboard state can get all
   snarled up...)

   Again, the protocols and schemes used to communicate with the keyboard
   and the mouse are not really clearly documented for the customers.  And
   they are *not* the PC protocols.

   If the customer is not managing the systems, then there's no need for
   the keyboard nor the mouse -- just leave them connected and stuffed
   down inside an enclosure somewhere near the system.

   --

   If there is a need for `management', then look at using reverse LAT and
   switching the ports as needed.  (`poor man's VCS'...)

   Alternatives to the the hardware hackery are VCS, Argus -- the PC
   management station -- and DECamds.  The latter two mechanisms are
   part of OpenVMS.  Combinations also work.