When you try to install Remote Control Agent on a Windows NT 4.0 system, the process may fail, outputting the message Display Driver File not Found.

Response

The Windows NT 4.0 system may be running in the VGA mode. From the Control Panel, choose Display to display the Display Properties dialog box, and then press Display Type. If the Current Files shows vga.sys, vga.dll, the system is in the VGA mode. Install the display driver provided by the machine.

If you create an application in JAVA2 and attempt to activate it on an agent, the agent's screen might not appear on the controller display because the application uses Direct Draw when rendering drawings.

Response

You can avoid this problem by specifying the following option when starting JAVA2 which will explicitly inhibit the use of Direct Draw:

-Dsun.java2d.noddraw=true

In the PC environment where the display board chip-set is 3D RAGE II by ATI, if the agent is running on Windows Me or Windows 98, some controllers may not be able to display the agent's screen correctly. This will normally depend on the version of the display driver.

Response

Setting an appropriate value in the agent's registry may eliminate this problem. Start the registry editor (regedit.exe). Choose Edit, New, and then String Value, create AgentHookOption under HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\JP1/RemoteControlAgent, and then set 1 as its data.

When connected to a Windows Me or Windows 98 agent, the controller may not be able to update the agent's screen view in the Remote Control window.

Response

The agent may have run out of memory. If the status bar of the Remote Control window shows the lack of memory icon (), use the Memory Settings dialog box for the Remote Control Agent environment setup and choose Customize memory allocation rather than Use default settings. Then adjust the memory allocation. For details on the memory settings used by the agent, see 3.4.8 Memory settings (for Windows Me and Windows 98).

On the controller side, refresh the screen status of the Remote Control window.

During a remote control operation, some mouse or keyboard operations on the agent screen may not function properly.

Response

The Ctrl or Alt key may be pressed on the agent machine. In this case, press the Ctrl or Alt key again to free up the system.

You can configure the controller to display an icon on the Remote Control window's status bar indicating the status of the agent's Ctrl and Alt keys. For details, see 3.3.5(3) Status bar.

After Remote Control Agent installation, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, or Windows 2000 may be unable to start.

Response

Remote Control Agent might conflict with non-Hitachi remote control products. Use the following procedure to correct the problem.

1. Start Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, or Windows 2000 in safe mode, and then uninstall Remote Control Agent.
2. Restart the PC.
3. If non-Hitachi remote control products have been installed, uninstall them.
4. Restart the PC.
5. Re-install Remote Control Agent.

The following procedure is used to start the PC in safe mode:

1. Restart the PC.
2. A message appears at the bottom of the screen, asking you to press the F8 key to display startup options. Press the F8 key.
3. Select Safe Mode using arrow keys, and then press the Enter key.
   Turn off the Num Lock key if you want to use the arrow keys on the numeric key pad.
   
4. Use the arrow keys to select the Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, or Windows 2000 operating system you want to start up.

If you try to use Remote Control Manager or Remote Control Agent without restarting the PC after installing the program, the following message may be displayed and the program may fail to start: The ordinal 6907 could not be located in the dynamic link library MFC42.DLL.

Response

Restart the PC and then start Remote Control Manager or Remote Control Agent.

With a version of Internet Explorer earlier than 5.01 is installed, the icon is displayed incorrectly when the status window of the agent is docked to the edge of the desktop.

Response

Install Internet Explorer 5.01 or later.