UNIVERSAL DRIVER
The newest preferred method for locking records in MAPCON is achieved using the Universal Driver.
LOG EVERYONE OUT AND BACKUP THE MAPCON SYSTEM BEFORE STARTING.
Note: Follow either Windows or Novell setup instructions.
Windows 2000/2003 Server
1) Install the Universal Driver from a workstation. Run the Server installation setup.exe and follow instructions. Use the default location to install the service.
2) On the server, in Control Panel, Administrative Tools, under Services, check for the Linear Hash service which should now be started.
Setting up Clients for Windows 2000/2003 servers:
1) Run the Universal Driver Client installation setup.exe from the CD.
2) When prompted with location of OpenInsight application, point to the root folder of MAPCON where OINSIGHT.EXE is located (typically called wmapcon).
3) Change the driver to the Universal Driver 3.0.0.2 (The driver should be this version or higher.) Click Ok.
4) Set Sharing and Permissions so that all users have Full Control, and the System user also has Full Control of all folders and files within MAPCON.
5) Use Notepad to create a revparam file in the root directory ONLY! Remove the .txt extension after creating it. It has only one line and should look like this:
ServerOnly=1
Optional: The Service connects by default using Named Pipes. To improve the performance of the connection using TCP/IP, do the following:
(Note: editing the registry is done at the user s risk.)
On server, Start, Run, REGEDIT
My computer HKEY_LOCAL_MACHINE SOFTWARE REVSOFT REVELATION UNIVERSAL DRIVER 3.0
Change TO
AnonymousUserName ServiceLogOn
NamedPipeName None
TcpIpPort 777
Add to the revparam file:
ServerOnly=1
TcpIpPort=777
Stop and Restart the Linear Hash Service.
INSTALLATION IS COMPLETE!
Novell Server
1A) Optional (Do this only if performing an upgrade of the NLM) - Shut down the original NLM. Use the command LHSTOP
1B) Backup NLM files (LH*.NLM) to another area. Delete all files called revparam located within the MAPCON directories. Ex: revparam would be found in the root M:\wmapcon and in \datavol, \mapcon. \toolbox, etc.
2) Install the Universal Driver from a workstation.
3) Create the LH3SRVC.INI file on the Novell server. This file must be in the same place as the NLM files on the server. The file will look like this (it is case sensitive):
# Initial configuration - See Revelation manual for examples
[Global]
TcpIpPort=9998
NamedPipeName=None
AnonymousUsername-ServiceLogOn
[Shares]
Mapcon=SYS:Apps\Mapcon
#<ShareName2>=<DirectoryLocation2>
4) In the LH3SRVC.INI file, the share name (under the header [Shares] ) must point to the location of the Oinsight.exe file on the server. Make sure this path matches the path of the live system exactly, including case.
5) Create the LH3SRVC.LOG This file is a log file that will be deleted later. The file must be located on the Novell server where the new IP NLMs reside.
6) Start the NLM with command LH3START
Note: to stop the NLM use LH3STOP
7) Note the size of the log file, LH3SRVC.LOG There should be some information in it.
Setting up Clients for Novell Servers
1) Run NETDRV.exe Change the driver to the All Networks Driver 2.1 (32-bit) or All Networks Driver 1.5 (16-bit standard system).
2) Login to MAPCON and log back out. This verifies things run without the driver. That way, if the driver fails, we know it's the driver and not something else.
3) Run the Universal Driver client installation.
4) Run NETDRV.exe again. Change the driver to the Universal Driver 3.0.0.2 (The driver version should be this version or higher).
5) Add the file LH3.LOG to the client root directory.
6) Create a revparam file in the root directory Only! It should look like this:
ServerOnly=TRUE
ServerName=192.168.1.2
TcpIpPort=9998
ShareName=Mapcon
a) Enter the appropriate IP Address of the server for ServerName.
b) Enter the appropriate ShareName from the LH3SRVC.INI file. Make sure this name matches exactly, including case.
7) Login to MAPCON. If successful, check the LH3.LOG file (client) and the LH3SRVC.LOG file (server). If those files are increasing in size with multiple logins, then things are working.
a) Delete both log files.
b) Remove the IPX protocol from all workstations. If the IPX protocol cannot be removed, then make IP the preferred protocol by listing it first.
INSTALLATION IS COMPLETE!
Troubleshooting
If things don't work, you're probably getting an FS231 or FS492 error.
FS231- Things are communicating but they're not understanding each other. More than likely, the revparam or the LH3SRVC.INI is in the wrong place or is incorrect.
FS492- Nothing is connecting. Make sure there are no revparam files in the subfolders, just in the root directory.
Some other things to check:
a. Check case on everything.
b. Try pinging the IP address from the workstation.
c. Novell: Make sure the .ini file is with the NLMs on the server.
d. Stop and start the service.
e. Verify the share name, which is case sensitive.
f. Make sure the IP protocol is on the workstation and is listed first (before IPX).
Slow performance Issues:
a. Remove the IPX protocol from workstation.
b. If using the Novell Application launcher, right click on the icon and do Verify if the option is there.