Echelon LNS - Manual (Page 323)

LNS Programmer's Guide 309
The statement, “The setup cannot continue” may be confusing to the users of your
installation, even if you ignore the return code from setup.exe and continue your
installation.
In order to avoid this dialog, you must check for this case before running setup.exe,
and avoid any attempt to install over a greater version of the LNS runtime. To do so,
your installation must read the LNS runtime version information at the following
Windows Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Echelon\<LNS Runtime 1 >\Version
The version Windows Registry key is a string value in the format Mmmbbb, where M is the
major version number, mm is the minor version number, and bbb is the build number. The
LNS Turbo Edition version number will be in the format “320bbb”, where the final build
number will be visible in the first few lines of the LNS runtime readme.htm file.
If this Windows Registry key does not exist, the PC either does not have the LNS runtime
installed, or the LNS runtime is a pre-Windows-Installer version that can be freely upgraded
by LNS Turbo Edition as a full installation. So, the absence of this Registry key is also a
signal that the setup.exe install can be run.
Step 4: Check the LNS Runtime Installation Completion Status
After setup.exe is run, you can check the completion status of the LNS Runtime
installation by reading the following Windows Registry key string value:
HKEY_LOCAL_MACHINE\SOFTWARE\Echelon\<LNS Runtime>\Install Status
The value will be set to “Success” if the LNS runtime was installed successfully, and does
not require a reboot to complete. The value will be set to “Success-RebootNeeded” if the
LNS runtime was installed successfully, but a reboot is necessary in order to finalize the
installation. Your LNS-based product installation should force a reboot upon completion
in this case, or at least inform the user that a reboot is needed to complete the
installation.
Step 5: Install the version 3 Microsoft XML Parser
The LNS Turbo Edition runtime requires the version 3 Microsoft XML Parser. While
this exists on the newer Windows operating systems that are supported by Turbo
Edition, including Windows XP and Windows Server 2003, it does not exist on Windows
2000 (unless it has been updated with Internet Explorer 6.0).
Microsoft’s licensing of this redistributable is fairly flexible. However, they do not allow
redistribution of these components by users whose customers will then redistribute them
again. This prevents Echelon from installing them in the LNS runtime installations.
Users of the LNS runtime installations have two choices. They can either install the
version 3 Microsoft XML Parser in their installations, or they can require that systems
on which their products are installed include Internet Explorer version 6.0 or greater.
1 <LNS Runtime> should be either “Echelon LNS Server” or “Echelon LNS Remote
Client”, depending on the LNS runtime installation you are using.