Serial to Ethernet Connector

What's new in this version:

Serial to Ethernet Connector 9.0.1253
- Added: new software drivers signed by Microsoft
- Added: color indication that the maximum number of client connections allowed for a remote server has been reached
- Improved: Spanish, French, and German localizations
- Fixed: compatibility issues with 12th Gen Intel® Core™ processors
- Fixed: issues with displaying long port names
- Lots of minor fixes and improvements


Serial to Ethernet Connector 8.0.1173
- Lots of minor fixes and improvements


Serial to Ethernet Connector 8.0.1113
Added:
- a new improved user interface
- the list of remote connections available on the network
- the ability to pause active network connections
- the ability to break a specific connection
- the ability to reset the connection statistics
- the menu “For developers” with the options to open the OEM user manual, view code samples, and generate the OEM Redistribution Package. (In the OEM version only.)

- Discontinued: support for Windows XP, Windows Vista, Windows 2003, and Windows 2008 and Windows 7 versions. Serial to Ethernet Connector versions for Windows 7 SP1 and Windows 2008 R2 SP1 are still supported.


Serial to Ethernet Connector 7.1.876
- Improved: the drivers have passed WHQL certification and are now digitally signed by Microsoft
- Fixed: a crash of the service on creating a client Telnet connection on a real COM port
- Fixed: when creating a connection, changing the port number did not change the connection name
- Fixed: when creating a connection, the “Create as virtual port” option ignored the port type
- Fixed: virtual ports might not work after the system was woken up from sleep mode or booted with Fast Startup
- Fixed: if the system went to sleep while data transfer was in progress, the communication was not resumed after waking up
- Fixed: enabling the “Break connection if no activity for” option could cause an error on the server side

Serial to Ethernet Connector 7.0.815
- Fixed: a crash of the GUI when creating a connection on Windows 10 build 1607
- Fixed: a crash of the service when creating identical Telnet connections via mirroring
- Fixed: after editing the connection settings, the changes were occasionally not saved
- Fixed: for client connections on Windows 10, adding a large number of remote hosts could result in high CPU load
- Fixed: a crash of the GUI when rapidly toggling the “Turn On/Off SEC” button
- Fixed: when a connection was lost, its status in the connection tree might not be updated
- Fixed: reading of the connection list could sometimes fail with an error (OEM version)
- Fixed: a memory leak in the OEM usage samples

Serial to Ethernet Connector 7.0.609
- Added: a redesigned interface
- Added: the ability to export/import the connections configuration (from the GUI as well as the command line)
- Added: the ability to set the size of the buffer or disable buffering altogether
- Improved: performance when creating multiple virtual COM ports at a time
- Improved: conditional data sending: you can now specify multiple conditions; the “Send data when received char with code” condition now accepts characters with ASCII codes above 127
- Improved: on removing a connection, the virtual COM port is now deleted even when opened
- Fixed: an issue where the GUI failed to connect to the service after reopening
- Fixed: incorrect behavior of strict baud rate emulation
- Fixed: some activation issues
- Fixed: a crash of the service on attempt to create a virtual COM port with a long name
- Fixed: a condition where a client connection set to communicate with a large number of servers could disappear after a reboot
- Fixed: a crash of the GUI on attempt to send a mirror request
- Fixed: a condition where a server would sometimes start listening for connections when not supposed to (i.e. when configured to start listening only when the COM port is opened, and the port was closed)
- Fixed: the service could become unresponsive on startup on some older processors
- Fixed: with delayed sending enabled, the data could get split across multiple network packets
- Fixed: the “Break connection if no activity” option was not functional
- Fixed: a break signal from a device was not transmitted when using the Telnet protocol
- Fixed: a few minor bugs related to flow control negotiation