ServSwitch User's Manual

MATRIX SERVSWITCH™

You can’t seem to scan or switch to certain ports at all.

A. Are other users accessing the CPU ports you’re trying to reach in “private

mode”? If so, you won’t be able to use those ports until the private-mode users

release them—even if you are a private-mode user yourself. See Sections 4.6 and

5.4.

B. You can only reach CPU ports that belong to your group. If you need to access a

computer that is not in your group, you’ll have to add the computer to your group

(see Section 4.7) or change the group membership of your user profile (see

Section 4.6).

C. The system’s “Maximum computer” setting is too low. Set this to match the

number of CPUs in your system; see Section 4.2 for how to do this through the on-

screen display or Section 7.2 for how to do this through the serial port.

The Matrix ServSwitch scans or switches to empty or nonexistent ports.

The system’s “Maximum computer” setting is too high. Set this to match the

number of CPUs in your system; see Section 4.2 for how to do this through the on-

screen display or Section 7.2 for how to do this through the serial port.

The Matrix ServSwitch keeps displaying “Connection failed, queue is full” when

you scan.

There are already two users connected to one of the ports you’re trying to scan.

You will keep getting this message until someone disconnects from that port.

An IBM compatible computer’s mouse driver doesn’t load.

A. What type of mouse is the CPU looking for? If it’s an RS-232 serial mouse, see

steps B and D. If it’s a PS/2 or PS/2 wheel mouse, see steps C and D. If it’s a

Microsoft BallPoint mouse, see step D. At the time of this writing, the Matrix

ServSwitch does not support other types of mice.

B. RS-232 serial mouse: Make sure that you’re using the right COM port, and that

the mouse driver is looking for the correct port.

C. PS/2 or PS/2 wheel mouse: To recognize the mouse, the CPU must be directly

connected to it, or indirectly connected to it through the Matrix ServSwitch, at

boot-up time. Make sure that all cables are properly seated and that the Switch and

submaster are ON, then reboot the CPU.

D. Your mouse driver might be old or incompatible with your mouse. Try the latest

version of the Microsoft mouse driver.