============================================================================= HL-Server NLM - History of changes ============================================================================= 2.00 (Level 3.30) July 1998 - automatic addition of requested Hardlocks The NLM may be started without any module address specified. Whenever a client application requests an unknown Hardlock, it will be automatically added, if available. - up to 10 Hardlocks supported - changed screen layout - F8 key invokes paket trace mode - ADD/REMOVE Hardlocks from server screen - option -comm:ipx selects IPX only - API_READ_ID function supported 2.00 BETA (Level 3.20) - TCP/IP support - ADD/REMOVE Hardlock via HLSADMIN - ENABLE/DISABLE of protocols via HLSADMIN - veni-vidi-vici switch renamed to -v (verbose) - additional level 3 status functionality (identical to HLS32*) to allow full administration via HLSAdmin - identification & background checking changed to level 3 - can be started without any Hardlocks specified - minimum timeout 1 minute (was: 10) - Duplicated counters problem fixed If one HL-Server was accessible via different MAC addresses, both USERINF and MAXUSERS could be duplicated in former versions. You must use new (Feb. 1998) HL-Servers and APIs for this fix to work (of course, you can mix old APIs with new Servers and vice versa if you are not concerned about this problem). 1.28 (Level 2.62) - API_AVAIL does not longer perform API_LOGIN. (This is identical to the HL-Server TSR) - Internal API_STATUSOFF is not used in NLM. The error counter is no longer incremented if this function is received. _____________________________________________________________________________ 1.26 (Level 2.60) - HL-Server NLM could not be found from within a Windows-95 M8 Dos Box, because Microsoft IPX does not truncate packets exceeding the buffer size, but returns an empty buffer. HL-Server NLM reply packets were 2 bytes too long and have been shortened. _____________________________________________________________________________ 1.25 (Level 2.55) _____________________________________________________________________________ 1.23 - Slow file server clock In rare cases, the file server clock may be slow when using HLSERVER.NLM. There is an option to correct this problem. Please contact our support if this problem occurrs. _____________________________________________________________________________ 1.22 - Bugfix: Using "Remote/Select" rsp. "Remote/Rescan" from the HL-Server menu surface, an illegal memory read operation was performed by the NLM. Depending on the file server's memory usage, the message "Memory read from nonexistent page" appeared. The file server or HL-Server was not functionally affected. _____________________________________________________________________________ 1.21 - The "LOGINS" signature in the application hardlock is considered valid even if no valid number follows. In this case, the number of logins will not be restricted, it will be equal to your HL-Server licence. _____________________________________________________________________________ 1.20 - The LPT ports (278,378,3BC) where to search the HL-Server Hardlocks may be explicitly specified; this can be used to exclude ports conflicting with other interface cards (e.g. network adapters) from the search. Example: LOAD HLSERVER MODULE:29809 SEARCH:278,3BC Only port addresses 278 und 3BC will be searched for HL-Server Hardlocks. There will be no access to port 378. The addresses must be entered hexadecimal. - 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. _____________________________________________________________________________ 1.12 - NLM's until version 1.11 replied to an INIT request even if the login table was full. As a result, the addition of HL-Server licences did not work correctly. If the first HL-Server found was full, it was impossible to access any other. - New detection routines for monochrome monitors implemented. Direct port access is now used to determine monochrome video adapters or color adapters with monochrome monitors. This detection may be overridden by the -FORCEMONO or -FORCECOLOR options. When using this options, the detection routines will not be used.
mol96