Table of Contents
Advertisement
If you're using a PS/2 type mouse with a DOS or Windows 3.x CPU, don't issue
this command if the CPU doesn't have a mouse driver loaded—many such CPUs
will crash if you send them unexpected mouse data. (CPUs running UNIX
versions of Windows don't have this problem.) If your shared CPU is like this, and
you have chronic problems when you try to run applications that don't use the
mouse but don't disable the mouse either, take these precautions:
• If you never actually use the mouse with the CPU (as would probably be the
case if, for example, the CPU were a Novell
plug the mouse strand of the CPU Adapter Cable into the CPU's mouse port,
or don't load a mouse driver at all. If you do use the mouse, are running
Windows 3.x, and sometimes exit to DOS, make sure you load a DOS mouse
driver before running Windows.
• If you've loaded a DOS mouse driver and are going to use an application such
as NetWare that disables the PS/2 mouse, first REM out any statements in your
startup files (AUTOEXEC.BAT, etc.) that load the mouse driver, then reboot
the computer to remove the mouse driver from memory. (Having the mouse
driver unload itself doesn't do the job.)
4.3.5 S
N
B
END
ULL
PS/2 type mice send control data to CPUs in three- or four-byte increments.
Sometimes, because of electronic transients, unusual power-up effects, or plugging
and unplugging of cables from live equipment, the currently selected CPU in a
ServSwitch Jr. system can lose one or two bytes of this control information and get
"out of sync" with the shared mouse. In this situation, the mouse might seem to
refuse to move the pointer or cursor, open windows for no reason, or exhibit other
strange behavior. To get the CPU back in sync, send this command to tell the
Switch to send a "null byte" to the CPU's PS/2 mouse port (this has no other effect
than getting the CPU "caught up"). To issue the Send Null Byte command, press
and release the left Control key, then type [N]. If the mouse still isn't right after
you issue this command, the CPU must have been more than one byte out of sync.
Issuing the command once or twice more should do the trick.
The CPU will be thrown out of sync if it has a PS/2 mouse port and it's in sync
when you issue this command. Issue this command two more times to get it back in
sync again. This command has no effect on CPUs that are attached to the Switch
through an RS-232 mouse port.
If you have version 9.01 or higher of the Microsoft mouse driver, the CPU should
never get out of sync. Contact Microsoft if you would like to upgrade your
Microsoft mouse driver.
(CPU
PS/2 M
YTE
S WITH
®
NetWare
P
O
)
OUSE
ORTS
NLY
CHAPTER 4: Operation
®
®
file server), either don't
or later
27
Advertisement
Table of Contents
