Testing a mouse
Pseudo-ttys must be installed on the system in order to use
for more information.
If usemouse does not produce the
behavior described here, or you see the following error
messages, your mouse is not installed correctly.
Log in as root in multiuser mode on the terminal
you wish to test.
Enter the following at the system prompt:
As you move the mouse and click the buttons, characters should
be echoed to the screen. For example, output might include:
left mouse button (button 1) pressed and released
manual page for a complete listing of usemouse echo output.
If you are using a two button mouse, pressing both buttons
at once emulates the middle button.
To stop the usemouse utility, press the interrupt key,
usually <Del> or <Ctrl>-C.
Because usemouse starts a new shell when
executed, it is important to exit this shell before
starting a graphical application.
Open event driver failed:: No such file or directory Open
event driver failed:: Not enough space...giving up
To fix the problem:
First, verify that your mouse is supported by SCO OpenServer.
Confirm that you have run mkdev mouse and that your
mouse selection corresponds to the connected mouse hardware.
Make certain the cable is attached securely and, if you are
using a bus mouse, that the adapter card is properly
If you are using a bus mouse, verify that the bus mouse
card is recognized during the boot process and that there
is no conflict with the interrupt vector or base address.
Check the hardware configuration information using the
If you are using a serial mouse, verify that the serial
card to which your mouse is attached is recognized during
the boot process (by running hwconfig).
If the mouse is on a multiport board that uses its own
drivers, make certain the board works. Try the mouse on a
COM port to eliminate the possibility of a
third-party driver being the problem.
Removing a mouse
Changing mouse ports
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003