NETWORK INSTALLATION GUIDE
TABLE OF CONTENTS
1 Installation of software on file server
2 Installation of software on workstation
2.1 Standard Workstation
2.2 Installation by Script
2.2.1 Script file
3 Installation of hardlock server (optional)
3.1 Hardlock Server installation
3.1.1 Windows NT installation
3.1.2 Windows 95 installation
3.1.3 Windows 3.1x and DOS installation
3.1.4 NetWare installation
3.2 Hardlock Workstation installation
3.3 Upgrade from an older HLS32 version
3.4 Known Problems
4 Installation of a local hardlock (optional)
1
PLAXIS
1 INSTALLATION OF SOFTWARE ON FILE SERVER
Start the Installshield Wizard (setup.exe) from CD-ROM.
As Destination Location, select or create a folder on the file server.
Select Server as Installation Type
Note: If the file-server is an Windows NT Server and needs to function as network
hardlock server as well (or if a Windows NT Workstation has been chosen as
hardlock server), access to the parallel port needs to be installed. By default,
access to the hardlock is not installed during a Server Installation. Manually
install the local hardlock drivers first (as described in Chapter 4) before
installing the network hardlock.
2 INSTALLATION OF SOFTWARE ON WORKSTATION
Two procedures exist for the installation of workstations:
- Standard Workstation
- Installation by Script
2.1 Standard Workstation
Start the Installshield Wizard (setup.exe) from CD-ROM.
As Destination Location, select or create a folder on the workstation or select
or create a designated user folder on the file server.
Select Workstation as Installation Type.
The above procedure performs 5 tasks:
Install the Borland Database Engine (BDE).
Install the Material sets database.
Making default user preferences in the registry.
Asking the user to indicate where the program files can be found.
Creating shortcut in the program folder
2.2 Installation by Script
2
NETWORK INSTALLATION GUIDE
For large networks it can be inefficient to perform the Standard Workstation
installation procedure. If users start programs using scripts there is an easier method to
install Plaxis. In a script the following tasks need attention:
Installation of Borland Database Engine ( BDE) & Installation of Material sets
database (tasks 1 & 2 of the standard workstation installation).
These tasks can be performed by using the BDE50.EXE, located in the Plaxis
program folder on the file server (see section Steps in Script below).
Making default user preferences in the registry (task 3 of the standard workstation
installation).
This task can be omitted, resulting in the creation of default settings when
Plaxis is first executed.
Creating shortcut in the program folder (task 4 of the standard workstation
installation).
The creation of shortcuts can be realised in the script as well. Users need
shortcuts to the four sub-programs:
- Plaxis Input (GEO.EXE)
- Plaxis Calculations (BATCH.EXE)
- Plaxis Output (PLAXOUT.EXE)
- Plaxis Curves (CURVES.EXE)
3
PLAXIS
2.2.1 Script file
After a Server installation the file BDE50.EXE is located on the file server in the Plaxis
program folder. Running the file BDE50.EXE will:
Install the BDE installation in the folder:
"<Common Files>\Borland Shared\ BDE".
Install the Material sets database in the folder
"<Program Files>\Plaxis71\".
If users start programs using scripts the following actions should be performed in the
script:
Check if BDE has already been installed on the workstation (for BDE check: see
below).
If BDE does not exist: install BDE .
Create shortcuts.
Start Plaxis Input (GEO.EXE).
Check for BDE :
Check if registry block:
"HKEY_LOCAL_MACHINE\Software\Borland\Database Engine" exists.
If this block exists :
Read CONFIGFILE01 key
Extract filepath from key
Search for IDAPI32.DLL in this path
Check for version number of this DLL, must be 5 or higher.
If registry block and key are not found, or version < 5 then install BDE.
4
NETWORK INSTALLATION GUIDE
3 INSTALLATION OF HARDLOCK SERVER (OPTIONAL)
This procedure is only necessary when using the Plaxis network hardlock key
(green/purple key).
The protocol that can be used to access the network hardlock depends on the operating
system used on the server :
Windows NT 3.51, 4.0 IPX, TCP/IP, Netbios
Windows 95 IPX, TCP/IP, Netbios
Windows 3.1x IPX, Netbios
DOS IPX, Netbios
OS/2 IPX, Netbios
Netware 5.0 IPX, TCP/IP
NetWare 3.1x, 4.xx IPX
To install a network hardlock two actions are necessary :
The Hardlock Server program must be installed.
The search environment variable must be defined on the workstation.
3.1 Hardlock Server installation
The Hardlock Server program to be installed depends on the operating system used on
the server. The appropriate files are installed during the installation type Server in the
folder HLserver of the Plaxis program folder.
Windows NT 3.51, 4.0 HLS32SVC.EXE
Windows 95 HLS32.EXE
Windows 3.1x HLSERVER.EXE
DOS HLSERVER.EXE
OS/2 HLSERVER.EXE
NetWare 3.1x, 4.xx, 5.0 HLSERVER.NLM
3.1.1 Windows NT installation
First, the hardlock system drivers must be installed to be able to approach the LPT port
of the server. This installation is done automatically when installing Plaxis but it can
5
PLAXIS
also be done manually with the HLDINST.EXE program. To do so switch to the driver
directory ..\<PLAXISDIR>\WINNT and enter:
HLDINSTinstall
The Windows NT service can now be installed in two different ways :
Start HLSADMIN.EXE.
It runs on WinNT 3.51 with Service Pack #3 or higher, Win95, WinNT 4.0.
It does not run on Win32s !
In the tree view, select the machine marked as "local".
Click then the green traffic light in the toolbar; the HL-Server service will
be installed and will start to run.
Install your Hardlock using the "Add Hardlock" Button in the toolbar.
Alternatively, the service can be installed and started from the command line or a
batch file. The HLS32SVC.EXE should reside in the Windows system directory.
hls32svcinstall
hls32svcstart
hls32cmdadd25459
The HL-Server service is now running and can be used. It will be started at every
system boot until it is removed by "Remove" from the "Service" menu.
To find HL-Server via IPX from within other network segments, the SAP agent must
be active on the HL-Server machine (Control Panel Network Services Add
SAP Agent).
6
NETWORK INSTALLATION GUIDE
3.1.2 Windows 95 installation
First, the virtual device driver HARDLOCK.VXD must be installed to be able to access
the LPT port of the server. This installation is done automatically when installing
Plaxis. It can also be done manually using the HLDINST.EXE program from the
<PLAXISDIR>\WIN95 directory.
The Hardlock Server program is must then be installed from the
<PLAXISDIR>\HLSERVER\NT_95 directory:
HLS32m:25459
This call may be issued from a command line prompt, or included in the Startup
group.
As in former versions of HL-Server, up to three module addresses can be specified.
Hardlock can be added to and removed from a running server using HLSADMIN.EXE
3.1.3 Windows 3.1x and DOS installation
There is no special installation required to access the local LPT port. The Hardlock
Server program can be installed directly typing :
HLSERVERim:25459
For Windows 3.1x this TSR should be started before Windows, not in a Windows
DOS box.
Only the HLSERVER.EXE program is absolutely required on the computer on which
you loaded the HL-Server as a resident system. If you also want to use the menu
interface and online help, the HLSERVER.OVL and HLSERVER.HLP files must also be
available.
7
PLAXIS
3.1.4 NetWare installation
To install the NLM, you need to access the server console or use the RCONSOLE
program. Make sure that you have supervisor access under NetWare. There is no
special installation required to access the local LPT port.
The Hardlock Server program can be installed directly typing :
LOADHLSERVERim:25459
To start the HL-Server easily as an NLM, we recommend that you also use the files
HLSERVER.CFG (configuration file) and HLSERVER.NCF (simple Batch file).
3.2 Hardlock Workstation installation
When the network hardlock has been installed on the server it is not required to do
any installation on the workstation to be able to access the network hardlock.
However, in some cases it is practical to explicitly specify a search sequence using
environment variables to avoid conflicts when the system automatically searches LPT
port addresses. When using TCP/IP, specifying the address where the hardlock can be
found will decrease the search time.
The syntax of the environment variables reads as follows:
HL_SEARCH=[Port],...,[Protocol],...
8
NETWORK INSTALLATION GUIDE
[Port] comprises the I/O address in hexadecimal form and a port ID:
Port ID: Explanation:
p = parallel Normal parallel port
s = serial Normal serial port
e = ECP Parallel port in ECP mode
n = NEC (Japan) Japanese NEC models have a different port
assignment. This parameter activates a special
handling so that a separate NEC API is not required.
c = Compaq Contura The multiplexer of the docking base (used for
Docking Base switching between the parallel port and Ethernet
adapter) is switched to the parallel port for querying a
Hardlock.
i = IBM PS/2 The IBM PS/2 ID eliminates errors when
reprogramming the port of certain video drivers under
Windows. (The system cannot find Hardlock once
Windows is started). Previously, this was done
internally by the Hardlock API. This function can
now only be activated by using the environment
variable.
[Protocol] defines the protocol used for accessing an HL-Server. The following key
words are currently supported:
Protocol: Explanation:
IPX HL-Server searched for via IPX or SAP.
IP HL-Server searched for via TCP/IP
NETBIOS HL-Server searched for via NETBIOS.
Example:
SETHL_SEARCH=378p
The system only searches for the Hardlock at the local parallel port with the address
0x378.
9
PLAXIS
SETHL_SEARCH=378e,2f8s
The system searches for the Hardlock at the local parallel port with the address
0x378. The port is switched from ECP mode to "normal mode while the Hardlock is
being accessed. If the system cannot find the Hardlock, it then searches for it at the
serial port with the address 0x2f8.
SETHL_SEARCH=IPX,278p
The system first searches for a Hardlock supplied by the HL-Server using IPX/SAP.
If it is not able to log into the HL-Server, it then searches for the Hardlock at the
local parallel port with address 0x278.
SETHL_SEARCH=378p,278p,3BCp,IPX,NETBIOS,IP
This corresponds to the automatic search sequence ( HL_LOGIN with DONT_CARE) if
the environment variable is not defined. This entry is thus redundant.
3.2.1 Using TCP/IP
When the network hardlock is to be approached with the TCP/IP protocol it is possible
to specify the address where hardlock can be found. The search sequence for the IP
protocol will then be :
1. Environment variable HLS_IPADDR (see below)
2. If no environment variable has been defined, the search takes place via DNS
or HOSTS for the station HLSERVER.
3. If no address has been found, the search takes place via broadcast
(255.255.255.255) in the local segment.
10
NETWORK INSTALLATION GUIDE
To transfer IP packets, Winsock calls over a corresponding (16 or 32 bit)
WINSOCK.DLL. Please note that during installation many Internet clients install their
own WINSOCK.DLL (CompuServe, AOL, T-online). In this case, accessing IP calls the
Internet provider if the HL-Server was not found via IPX and NetBios. You then need
to exclude IP from the search with the following command:
SETHL_SEARCH=IPX,NetBios
In order to improve the search via the TCP/IP protocol, the environment variable
HLS_IPADDR has been introduced. With it one or more IP addresses or names can be
defined. However, by entering several addresses at the same time - in contrast to
HL_SEARCH - you cannot predict which of the defined Hardlock Servers will
ultimately be used.
Example:
SET HLS_IPADDR=192.9.209.17,hardlock.server
HLS IPADDR can also be used to define broadcast addresses:
SET HLS_IPADDR=192.9.209.255,192.9.201.255
Since IP networks generally have considerably greater differences in propagation
time than IPX networks (e.g. WAN routes), timeouts and retries for the clients must be
kept within bounds. The default values are set so that the HL-Server can be found
with an existing 64kbit connection.
SETHLS_WAIT=
sets the delay between retries in milliseconds
default TCP/IP: 1000,
IPX: 200 (*)
min 200
max 30000
(*) the defaults vary, SET HLS_WAIT changes the values for IPX AND TCP/IP !
SETHLS_RETRIES=
11
PLAXIS
sets the number of retries until message DONGLE_NOT_FOUND is returned:
default 5
min 2
max 30
3.3 Upgrade from an older HLS32 version
HLS32SVC
1. Stop the service (using HLSAdmin or hls32svc -stop).
2. Remove the service (using HLSAdmin or hls32svc -remove).
3. Install and start the new version, as described above.
4. Use HLSAdmin to check if the version number of the.
5. Service running really is the new one.
6. Add your Hardlocks using "Add Hardlock" (or hls32cmd -add).
HLS32.EXE
1. Terminate the program.
2. Copy the new version of HLS32.EXE over the old one.
3. Restart the new version, with unchanged parameters.
3.4 Known Problems
On Windows 95, HLSAdmin cannot disable or enable protocols of an
HLS32.EXE that is installed on the same machine. Workaround: Select the
protocols you want to use at the command line (-comm:ipx,...) when starting
HLS32.EXE, or change the protocol settings from a remote machine using
HLSAdmin.
Starting two applications using the 16bit API DLL successively and very
quickly may lead to a system crash under Win31 and Win95.
4 INSTALLATION OF A LOCAL HARDLOCK (OPTIONAL)
12
NETWORK INSTALLATION GUIDE
This procedure is necessary when installing the Plaxis Network hardlock key
(coloured key) on a Windows NT computer or when using the Standard Plaxis
hardlock key (black key) on any machine. The standard hardlock can be used in
combination with the network key.
Plaxis automatically installs local Hardlock drivers, when performing the
Installation Type Personal Computer, Workstation and User defined (select Local
Hardlock drivers).
However, a network key has to be installed on a Windows NT machine or if the
automatic installation mentioned before fails the drivers can be installed manually.
To do so, please go to the appropriate folder according to your operating system
(folders: Win95,Win98,WinNT) and run the program HLDINST.EXE with the
appropriate command-line option. Available options are:
HLDINSTinstall : install hardlock drivers
HLDINSTremove : remove currently installed hardlock driver
HLDINSTfremove : force remove (kill open processes without query)
Normally, the first option is sufficient. During installation the program can ask
whether programs currently accessing the Hardlock may be removed in order to
install the (new) Hardlock drivers. Make sure all work has been saved in the
concerning programs before replying "Yes" to this question.
13
