User manual

4 - 4
ReM client installation hangs
after accepting the license
agreement.
User is trying to install from a
shared folder/drive. Installa-
tion from a network path is
not supported.
Installation must be performed from a
local or mapped drive in order to ensure
the installer has the necessary access
rights. To resolve, the user needs to
stop the process, delete the add regis-
try service by executing the command:
sc.exe delete "addregistry" or delete the
registry key
HKEY_LOCALMACHINE\SYS-
TEM\CURRENTCONTROLSET\SER-
VICES\addregistry. On Win2k the user
needs to delete the registry key addreg-
istry, since sc.exe might not work and
then copy the installation files to a local
or mapped drive and launch from there.
After installing the Remote
MasterMind client on
WEPOS1.0 with filter driver,
Windows requests to restart
the system. After restarting,
a dialog window prompts the
user to provide the location
for a driver file.
WEPOS 1.0 has a bug which
prevents it from finding the
necessary files for the driver.
Use the Browse button in the dialog to
manually browse for the required files,
which can be found in [Program
files]\JPOSScanner\FilterDriver folder.
Note: The above Microsoft bug limits
the user’s ability to use the silent
installer in the WEPOS
environment when installing
configurations that either need
the Filter driver or use the USB
Serial (COM) interface. In
POSReady 2009, Microsoft has
corrected this problem and none
of these limitations exist.
When you install the ReM cli-
ent agent in Windows 2000,
the following error message
displays:
“ReMWebMBean.exe -
Unable to Locate DLL. The
dynamic link library
MSVCR71.dll could not be
found in the specified
path.....”
This error is caused by a
Windows 2000 bug with JRE
1.6. After the installation
completes and you reboot
the host, this error will go
away. There is no impact on
the ReM installation.
Click OK then continue with installation.
Perform the host reboot when
requested.
“Run-Time error 430” mes-
sage displays during installa-
tion.
The computer has not
booted properly, and the
boot process is still running.
Therefore, the installer can-
not find all needed registry
entries and components.
Uninstall the client agent then reboot
the computer.
Ensure the computer has booted prop-
erly, then install the client agent again.
Symptoms Possible Causes Solution