Heres the news: (1) LNS 3 Service Pack 3 Now Available! (2) Mailing List Information [including how to unsubscribe] --------------------------------------- (1) LNS 3 Service Pack 3 Now Available! --------------------------------------- Download Service Pack 3 to get the latest reliability, compatibility, and performance updates for LNS 3. Download today from Echelons web site at http://www.echelon.com/support/dev_toolbox/updates.asp. Echelon highly recommends the use of this Service Pack. The entire ReadMe for the Service Pack is included here: ================================================================== LNS(tm) for Windows(r) 3.0 Service Pack 3 (SP3) Read Me File Updated September 7, 2001 Copyright (c) 2001 Echelon Corporation. All Rights Reserved. ================================================================== CONTENTS ======== 1. Overview 2. Installation Instructions 3. LNS 3.0, LNS 3.01 And LNS 3.02 Issues Fixed in LNS 3.03 3.1 AppDevice.Upgrade() method problems 3.2 Credit incorrectly charged on device application upgrade 3.3 LNS applications on LonWorks/IP channels cant use MD5 authentication 3.4 CP forward-reference causes import or upload error 3.5 NSD upgrade causes host dynamic NVs to disappear 3.6 Memory leak in LcaLdrfLanguages.GetItem() 3.7 Cant monitor up to published point limit 3.8 Single point monitoring startup does not report error on comm error 3.9 Heap error when monitoring on dual processor PC 3.10 Re-enabling monitor point does not re-enable error reporting 3.11 Load() after NeuronID property change used original Neuron ID 3.12 Current value not always reported after re-enabling monitor point 4. LNS 3.0 And LNS 3.01 Issues Fixed in LNS 3.02 (and included in LNS 3.03) 4.1 Cant import an XIF with LonMark device-level CPs 4.2 Node self-documentation string limit smaller than LonMark limit 4.3 Device Interface Upgrade() causes unbound NetworkVariable direction change 4.4 Various dynamic network variables issues 4.5 Interface object AddNVFromString() returns an invalid object on a Lightweight client 4.6 NS#67 after obtaining 65,536 references to the System object 5. LNS 3.0 Issues Fixed in LNS 3.01 (and included in LNS 3.03) 5.1 Issues with Windows Millennium (Windows Me) 5.2 ALL Subsystem path incorrect 5.3 NS# 8 error on System.Open() 5.4 LNS 2 compatibility issue with lcaAliasForUnicast connection option 5.5 Application exits after opening third network database 5.6 Events stop working 5.7 Database conversion problem with target alias connection members 5.8 Router.GetBufferConf() returned error 5.9 Setting MsgMonitorPoint.DefaultOptions 5.10 MonitorSet object default property 5.11 LNS IP Configuration Utility name change 5.12 Exit hang when using LonWorks/IP channels 5.13 De-serialization error with multiple LNS Lightweight clients 5.14 Wrong MonitorSet opened 5.15 Memory leaks 5.16 Plug-in Wizard command table corruption 5.17 Cant commission Router object created with Routers.AddReference() 5.18 Report Generator plug-in registration and launch errors 5.19 Stale object errors 5.20 Running as a Windows NT or Windows 2000 Service 5.21 Various LNS component crashes 5.22 Language support file 5.23 NS#149 error when opening a network 5.24 Error Initializing LonTalk stack errors 5.25 Modified reserved words in the user format file 5.26 Changing MonitorPoint.DefaultOptions can cause crash 5.27 CP transfer fails with file transfer CPs 5.28 LNS Full Client open performance under heavy traffic 5.29 External Interface File (XIF) Import Performance Improvement 5.30 Data Server DLL asynchronous message send 5.31 Deadlock problem 5.32 NetworkVariableField data access 5.33 LonWorks/IP Channel default port 5.34 A