====================================================== Lantronix Secure Com Port Redirector (SCPR) for ---------------------------------------------------- x86 (32bit): Windows XP, 2003 Server, Vista, 7, 10 and 2008, Server x64 (64bit): Windows Vista, 7, 8, 10, 11 and Server 2008, 2016, 2019 and 2022 ---------------------------------------------------- Software Release Notes ---------------------------------------------------- Version 4.3.2.1 Thursday, August 1, 2019 Copyright (c) 2006-2019, Lantronix ====================================================== This document is divided into the following sections: o Description o Requirements o Installation o Upgrade Instructions o New Features o Resolved Problems o Known Problems o Technical Support Description =========== This file contains the release notes for the suite of software that collectively are known as SCPR (Secure Com Port Redirector). SCPR manages virtual Com Ports. These virtual Com Ports look like real Com Ports to the system, but "Redirects" the communication to Device Servers on the network. The files in SCPR are: ScprDrvr.sys SCPR System Driver ScprDrvr.inf SCPR INF file CprIf.dll CPR Interface DLL CprLib.dll CPR .NET Framework 4.0 library DLL LtxLib.dll CPR miscellaneous library DLL Products.dll CPR Device Server products library DLL CprManager.exe CPR Manager, GUI version using .NET Framework 4.0 CprMonitor.exe CPR Monitor, GUI using .NET Framework 4.0 CprMgrCmd.exe CPR Manager, Command Line version (.NET not needed) CprMonCmd.exe CPR Monitor, Command Line version (.NET not needed) (No control over filtering, all events are processed) CprStatusCmd.exe CPR Status, Command Line (.NET not needed) Requirements ============ The following items are required to run SCPR: 1. x86 (32bit): Windows XP, 2003 Server, Vista, 7,10 and 2008 Server 2. x64 (64bit): Windows Vista, 7,10 and 2008 Server 3. Microsoft .NET Framework v4.0. For CprManager.exe and CprMonitor.exe only. 4. 30MB free hard drive space. 5. Device Servers must have firmware version 6.5.0.6 or greater to use RFC2217 (TruPort) capability. Windows XP: The "Internet Connection Firewall" must be disabled, or else UDP Ports 30718, 43282, 43283 must be available. Otherwise, you will not be able to detect or communicate with any devices on the network. To configure, go to the Control Panel, go to Network Settings, select the corresponding network adapter, choose Properties, and go to the Advanced tab. You may need to allow these ports access through the corporate firewall as well. Installation ============ SCPR is distributed in a single image as a self-extracting executable. It is included on the CD packaged with the device server. 1. The application installation directory defaults to C:\Program Files\SCPR, unless another folder is selected during the installation process. 2. A shortcut to this application is created on the Start/Programs menu for CprManager and CprMonitor. 3. Two installation files exist. One for Management and Monitoring from a GUI using .NET Framework 4.0. The other for that uses a command line interface. The .NET Framework 4.0 is not needed for the command line version CprMgrCmd.exe. NOTE: If the Microsoft .NET Framework 4.0 must be installed. If for some reason you received this setup utility without the .NET Framework, you can download it at the following URL: http://www.microsoft.com/downloads/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaylang=en Upgrade Instructions ==================== 1. Any installations performed over SCPR will automatically uninstall the previous version before installing the new version. To uninstall SCPR manually, follow these steps: 1. Select Settings->Control Panel from the taskbar Start menu. 2. Double click on the Add/Remove Programs icon. 3. Under the Install/Uninstall tab, select SCPR in the Software list and then click Add/Remove. Follow the prompts. New Features ============ Version 4.0.0.1 1. Initial version. Version 4.0.0.2 1. Com port errors that occur on the serial side of a device server are not report via RFC2217. Version 4.1.0.0 1. TCP Listen mode added. Device Servers must have firmware version 6.5.0.1 or greater to use Listen Mode with RFC2217 (TruPort). 2. Write Buffering added. 3. TCP KeepAlive mode added. 4. Wait on Write removed. 5. No Net Close mode added. When an application opens a port the connection to the Device Server is also made. When the application closes the port the connection to the Device Server is not disconnected. Disconnect by using CprManager. 6. CprManager shows the Com Status, which is the status from the perspective of an application that opens the Com Port. CprManager now shows the Network Status, which is the connection status between CPR and the Device Server. 7. Menu items were added to Close the Port from CprManager. 8. Menu items were added to allow the user to break the connection between CPR and the Device Server. This can be done only in Listen Mode and No Net Close mode. In No Net Close Mode the disconnect is possible only when the port is closed but CPR is connected to the Device Server. 9. Support for adding and removing ports to the local firewall added. 10. Support for Windows Vista added. 11. The term "Idle" to referred to a Com Port that is closed has been changed to "Closed". Version 4.2.2.0 1. Evolution device port numbers are now retrieved during device Search. 2. The web configuration page for the device can now be accessed from the settings tab and the device list. 3. AES encryption has been added to the encrypted version of CPR v4.2.2.0. Version 4.2.2.1 1. Added a Release Port menu item in the Com Port menu and the context menu for a com port. This menu item is only enabled when an entry for a com port is in the Microsoft Com Port Database, but there is no information for such a com port in the registry. Either real or virtual. By selecting this menu item, the reservation made in the com port database is released. Version 4.2.2.2 1. Drag and drop from the device list to the device settings page did not work correctly. The IP Address and Port would disappear upon saving. This is now fixed. 2. DSR and CTS now default to Active when RFC 2217 is not used. Version 4.3.2.0 1. Added support for 64 bit OSes. Supported 64 bit OSes are: Windows Vista x64, Windows 7 x64, and Windows 2008 Server x64. 2. Support of Windows 2000 has been dropped. Version 4.3.2.1 1. Added support for Windows 10, both 32 and 64 bit OSes. Resolved Problems ================= Version 4.1.0.0 1. Fixed a memory leak due to the write buffer. Version 4.0.0.2 1. Test tabs in the com port view are now disabled if the com port is opened. 2. Fixed an error in TestRS232 plugin when updating the combo boxes. 3. Fixed issue where an application can hang when it opens a com port that has the wait for write feature enabled. 4. Fixed an error that occurred on some systems when discovering the current com ports on the system. 5. CprAddPort tests if port exists before adding. Version 4.1.0.0 1. Closing a port which causes a cancellation of a wait mask event sometimes caused a BSOD. Version 4.1.0.1 1. Fixed CprManager start up issue when Blackberry RIM software is installed on the PC. Version 4.2.2.1 1. Cleanup after a failed com port addition has been improved. Some registry entries were not removed and the reservation in the Microsoft Com Port Database was not released. This happened only under certain addition failures. Version 4.2.2.2 1. Drag and drop from the device list to the device settings page did not work correctly. The IP Address and Port would disappear upon saving. This is now fixed. Version 4.3.2.1 1. Fixed issue where data was sent out the network side repeatedly under certain conditions. Known Problems ============== Version 4.0.0.1 1. For some legacy devices to be used when Microsoft FireWall is installed. Add UDP ports 43282 and 43283 as exceptions. 2. Some legacy devices may not work if they are on the other side of a router. These legacy devices respond with a broadcast when they are queried. If the router ignores broadcasts then the response will not get to CPR. Version 4.1.0.0 1. If a service has an address in the Host field on the Settings Tab that is valid for the subnet, but is not actually on the network, and is not in the local PCs ARP table, then the actually connection timeout value will be in the neighborhood of 3 seconds no matter what the Connection Timeout value is. 2. You can only have one Status event or Event Log event active at any one time. For example, you can not have CprManager and CprStatusCmd running at the same time. Both applications are requesting status information from the CPR driver. If you are using the CPR SDK, you can circumvent this issue by issuing a status request without a wait. This issue will be fixed in a future version. Version 4.2.2.0 1. AES and RFC2217 cannot be enabled at the same time. This is because none of the current device server's firmware support this. This capability will be supported in a future release. Version 4.3.2.1 1. An error occurs when upgrading from CPR 4.3.0.0 on 64 PCs. Please completely uninstall 4.3.0.0 before installing 4.3.0.1. A fix will be issued as soon as a third-party installer fixes the issue. Technical Support ================= If you have a question about SCPR, first look in the online Help file. When the program is running, press the F1 key to automatically display Help, or select Contents in the Help pull-down menu. Windows, .NET are trademarks of Microsoft Corporation.