Problems Caused by Forgetting to Restart

You can run the Remote Control component immediately after installation, but some drivers might not be available until you restart the client computer. Depending on the operating system, one or more of the following specialized low-level drivers for Remote Control might not be fully installed if you do not restart the client computer.

Windows NT 3.51 and Windows 4.0

You must load the KBStuff.sys and RCHelp.sys services. Without these services, the ALT+key Remote Control keystroke sequences will not work during a Windows NT Remote Control session. These services are automatically installed at installation time, but they will not run until the computer has been restarted.

Windows 2000

The KBStuff.Sys and RCHelp.sys services are known as the following devices in Windows 2000: “SMS Virtual Keyboard” and “SMS Virtual Mouse”. For information about manually installing these device drivers on Windows 2000, see the “Installing the Keyboard and Mouse Virtual Device Drivers on Windows 2000 Clients” later in this chapter.

Windows 95 and Windows 98

A Virtual Device Driver (VXD) is inserted into the Windows registry to load the Vuser9x.vxd helper driver (the upgraded 32-bit version of the former Vuser9x.386 device driver TSR). Until the Windows 95 or Windows 98 client is restarted, Vuser9x cannot be loaded. Without this driver, full-screen DOS sessions and some keyboard features will not work correctly during a Windows 95 or Windows 98 Remote Control session.

Windows 3.1x and WFW 3.11

An upgraded version of the original Vuser.386 driver is inserted into the [386enh] section of the System.ini file. This driver will not load until Windows is restarted and the System.ini is re-read during startup. Until this driver loads, full-screen DOS sessions will not work during a Win3.1x or WFW 3.11 Remote Control session.