Release Notes for 5.10.19
- "Stand-Alone" setup type added to the installation procedure. This is only added for clarity - it is functionally exactly the same as "Server".
- Error reporting by NPLSecure has been improved, and an Error Codes section has been added to the installation guide. Common Problems section has been rewritten.
- Setting NiaknetwEnabled=0 prevented NPLSecure from functioning. This has been changed so that it is ignored by NPLSecure.
- Inclusion of the "LAUNCH.EXE" file.
In some cases, LIST # generates odd results, such as:
2260 - 2230
2290 - 2290
?26=4 - 5130
?29=4 - 5320
?2:=4 - 5140 5330
?2<=4 - 5340
?2?=4 - 5310
?3;=4 - 5190
4000 - 2050
When using NPLSecure, the RunTime generates 2 temporary fff* files in the Windows directory each time it is run. Files are not cleaned up upon exit.
Release Notes for 5.10.17
- Support has been added in $DECLARE for the NUM() floating point data type.
- The user limit upgrade procedure has been updated: if it fails, resulting messages have been clarified.
- The user limit upgrade and SHOWNPL procedures now include NIAKWA_RUNTIME in the places in which to search for the license file.
NPLSecure service is supposed to be logging informational messages when doing things like looking for security, but those messages were not in the event log.
Windows 2000 Only: Security fails with a false "user limit exceeded error" when executing the runtime on the security server, only from a drive which is mapped to a local drive. This is a bad idea anyway because 1) Using the server as a workstation causes a serious performance drain for other workstations; 2) Mapping to a local drive has been known to cause very poor disk performance in some situations (see our Tech Note 99); and 3) It is possible to use the local drive letter rather than the mapped letter.