HP OpenVMS Systems

ask the wizard
Content starts here

Seeking help with unsupported hardware?

» close window

The Question is:

I have recently hooked up my AlphaStation 500au to a cheap-o Belkin SOHO KVM.
 Everything is fine, except that the IntelliMouse wheel will not act as the
 third mouse button.  I'm not looking to use the wheel, just the DECWindows
 copy/paste function of the
 traditional third button.

The Answer is :

  The OpenVMS Wizard is unaware of a system with the name "AlphaStation
  500au", though there are systems such as the AlphaStation 500 and the
  Personal Workstation 500au series.  The OpenVMS Wizard will assume
  that this is a Personal Workstation series, though both of these
  series systems do use the PC-style DIN connections.
  OpenVMS has only recently seen driver work around the mouse wheel (and
  the OpenVMS Wizard is not aware of formal support of any mouse with a
  wheel), nor does OpenVMS support the specified KVM switch.
  Accordingly, you will now have to perform (directly or indirectly) the
  testing effort and any associated device integration.  The OpenVMS FAQ
  has details on some of the considerations here, including sections on
  third-party hardware support (though targeting SCSI storage, the
  considerations are similar), and on the use of PC keyboards and mice
  and associated hardware gadgets on VAX and Alpha systems running OpenVMS.
  Part of the value of the supported devices is simple: the devices will
  work with the supported configuration, or HP will assist with replacement
  or upgrades to various components that will ensure that the devices work.
  The OpenVMS Wizard is not in a position to assist with efforts involving
  hardware testing and integration, simply because of the scale of the
  effort that can be involved.  The device integration and support effort
  -- starting with access to the hardware involved -- can range from the
  trivial (plug it in and it works) to a complete OpenVMS kernel re-write,
  and there can be cases where specific devices might never work (right).
  As for this case (as with most other similar debugging sequences), please
  replace the device (the mouse) with a supported device.
  Please then replace intervening hardware (the KVM) with a different
  device or (if available) with supported hardware.
  Then try a direct connection with a fully supported configuration.
  Topics related to keyboards and mice and device integration include
  (7374), (5759), (4295), and (3063).  Various existing discussions of
  third-party hardware are also available.  For keyboard mappings for
  DECwindows (X Windows), please see topics including (5869).

answer written or last revised on ( 28-OCT-2002 )

» close window