1. Include the mouse driver in CCONFIG.SYS. Ensure the following line is in the CCONFIG.SYS file: DEVICE=\CDOS\MOUSE.SYS
  2. Use SETUP to enable COM1 or COM2 as a mouse, 1200 baud, 8 data bits, not parity. Disable all protocol for the port.
  3. Connect the mouse to the proper COM port and reboot.

    Verify the mouse driver is loaded by observing the sign-on message. If no mouse sign-on message, verify that the driver is in your CDOS subdirectory.

    Also verify that the sign-on message indicates a mouse is logically attacted to either AUX0 (COM1) or AUX1 (COM2). If the AUX message does not appear, check SETUP.

  4. Run the ADUMB program and move the mouse.

    The screen should show something. If the mouse is on COM1, enter PRINTER=3 to check that some other task does not own the serial port. If the mouse is on COM2, use the command "AUX 1" before running ADUMB. Check ownership with PRINTER=4. Be sure it is free and available.

    If nothing displays when running ADUMB, the mouse may not work at 1200 baud. Use SETUP to change the baud rate to 2400, then cold start.

    If nothing works, the mouse may not work with the supplied mouse.sys, and should be tested under DOS.

  5. Invoke the application. The mouse should work.

    If the mouse is very erratic, change the baud rate to 2400 and reboot to test. Erratic operation may indicate that DOS has programmed the mouse before Concurrent has loaded. Remove the mouse driver from DOS and cold start.

  6. If the mouse is connected to a port other than COM1 or COM2, then use the CONFIG program to define the port as type MOUSE.
  7. If accessing the mouse on any station except the main console, use TERMSET MOUSE # CCPM to indicate the workstation is accessing the mouse on the aux port # (number 0 to 20).