========================================================================= HLSERVER.NLM Version 2.00 July 1998 ========================================================================= Please also read the general HL-Server READ-DOS.TXT file ! Introduction ============ The HL-Server NLM provides the same functionality as the HL-Server TSR, the HLS32 and the HLS32SVC service. An application using HL-Server cannot recognize any difference between them. The Hardlocks used are the same, so you can select the HL-Server that fits best into your customers network environment. All applications using the Hardlock network routines supporting the Service Advertising Protocol (SAP) can use the HL-Server NLM without any changes. SAP ist supported by the Hardlock API's and HL-Crypt since January 1993. In this version of the NLM, the HL-Server access cannot be limited to a single network segment, because all NLM's reside on a virtual LAN segment in the file server and must always be accessible via segment boundaries. Starting HL-Server ================== HLSERVER.NLM is started at the file server console (or RCONSOLE) by LOAD HLSERVER options The changes in available command line options vs. the HL-Server TSR are listed below: option TSR NLM ============ =========================== =============================== -? shows all available command line options -install installs HL-Server (this option may be ommitted, HL- Server installs automatically if correct module addresses are specified) -uninstall stops HL-Server and | not availible for NLM removes it from memory | | HLSERVER.NLM may be | unloaded by "UNLOAD HLSERVER" | or through the HL-Server | main menu -module:n[,m] module addresses of Hardlocks to be served This may be follwed by a comma and a login limit, where the limit cannot exceed any other limitations (HL-Server licence or application licence). At least one Hardlock | Parameter is optional. must be specified | Requested Hardlocks will | be added automatically This parameter may be re- | Up to ten hardlocks peated up to three times, | may be specified. to have multiple appli- | cation hardlocks served. | -display Enables the status line | not available for NLM display in the first | screen line | Status information can be | obtained from the HL-Server | screen. (switch between the | file server screen with | ALT-ESC or CTRL-ESC) -comm:n Selects network protocols | -comm:ipx disables IP to be used | -name:s HL-Server name to be displayed on the local an remote menu screens. The default value for | The default value for this this option is "HLServer" | option is the file server | name. -logindisable Disables new logins into the HL-Server This option may be | This option can only be speci- switched via the command | fied when starting HL-Server. line even if HL-Server | For switching while it is is running. | running, use the "Options" | menu entry at the HL-Server | console screen. -timeout:n Timeout in Minutes (0=no timeout, default=15) This value may be changed | This value can only be speci- from the command line | fied when starting HL-Server. even if HL-Server is | For changing it while running, running. | use the "Options" menu entry | at the HL-Server console | Screen. -password:s specifies the password for remote deletion of login entries with the HL-Server menu surface -boxsize:n adjusts the receive | not available for NLM buffer size | Since memory consumption is | not critical on the file | server, this (critical) option | is not necessary here. -quickoff diables quick Hardlock memory access (cache) -auto | Automatic return to system | console screen | This is an NLM-only option. | The active screen is | switched back to the system | console after initializing | HL-Server. It's nice to have | this in batch files (.NCF) -search:n,n,... | specifies the LPT ports (278,378, | 3BC) where to search for the | HL-Server Hardlocks. The addresses | must be entered hexadecimal. | (default = all) -forcecolor | disables monitor detection -forcemono | and forces use of color/mono- | chrome screen attributes Examples of loading the HL-Server NLM: LOAD HLSERVER The HL-Server is loaded without any Hardlocks specified. Whenever a client application request an unknown Hardlock, HL-Server looks for this Hardlock and adds it automatically, if available. LOAD HLSERVER -M:2547,5 -M:2548 -AUTO The HL-Server NLM is loaded to serve Hardlocks 2547 and 2548. The login table size for the first Hardlock is limited to 5 entries. The option -AUTO switches back to the system console after initialisation of HL-Server. All command line options may be specified in the configuration file SYS:SYSTEM/HLSERVER.CFG. The syntax is identical to the command line, but the options may be split into several lines. Please refer to the example configuration file. HL-Server Menu Surface ====================== The menu surface of HL-Server TSR can be used to monitor an test the HL-Server NLM. There are no differences between monitoring an HL-Server TSR and the NLM. The NLM itself uses a status screen and functions for manipulation the login tables and some parameters. HL-Server Level =============== With HL-Server NLM, the term "HL-Server Level" is introduced. While the version number denotes the implementation status of a product, the level describes the functionality that is presented to the client applications. HL-Servers with the same level (TSR, NLM, HLS32, HLS32SVC) provide identical functions. In older versions of the TSR without an explicit level, the version number also expresses the level. Requirements, Hints =================== - The demo mode is activated only if there is no HL-Server Hardlock, but only the demo Hardlock (29809). With an HL-Server Hardlock, it will be treated normally. - On very fast, heavy loaded file servers, the message "Process xxxx did not relinquish control frequently" may appear sometimes. This was noticed using NetWare 4.0x (not only when running HL-Server, but also with NetWare build in tools). This message is not critical, and may be turned off by "SET RELINQUISH CONTROL ALERTS OFF". Aladdin Knowledge Systems Axel Koehler
mol96