Serial data to TCP/IP

  1. Notes
    
 - Use the "setup -wauto -s" command line (instead of "setup -auto") 
   to start the "Silent Installation"!

  2. Major differences datAxe 2.0
  
2.1. The following enhancements have been made:

  1. COM Port Redirector and COM Port Redirector Service:
   - Implemented the "Disconnecting with the current client and connecting
    to a new client" mode and setting.


2.2. The following bugs have been fixed :

  1. COM Port Redirector and COM Port Redirector Service:
   - fixed the hang-up which may take place if the
    "Connect if the virtual COM-port is use by another task"
    setting is enabled.

  3. Major differences datAxe 2.0 from datAxe 2.0b
  
3.1. The following enhancements have been made:

  1. Virtual COM Port Driver:
    - Implemented the Data Carrier Detect (DCD) virtual serial port "state".

  2. COM Port Redirector and COM Port Redirector Service:
    - The "SYNC"/"ASYNC" modes are controlled by the new "Record synchronization mode"
     setting from the "Configure" dialog.
    - The DCD virtual serial port "state" is implemented as follows:
       a) DCD is Off (as was before this version);
       b) DCD is On (Default);
       c) DCD is controlled by DTR (as in NULL Modem Cable).
         Available only in the RFC2217 mode;
       d) DCD is turned On when client connects to server, and
          DCD is turned Off after client disconnects from server.

  3. COM Port Redirector Service:
    - Improved the log file output;


3.2. The following bugs have been fixed :

  1. Virtual COM Port Driver:
    - Abnormal termination of the executable prevented correct
     closing of opened Virtual COM-ports.

  2. COM Port Redirector and COM Port Redirector Service:
    - Executables may crash when the TCP/IP Client is in the Telnet RFC2217 mode;
    - Executables may crash when heavy traffic (with very often
     connect/disconnect events) took place.
    - The "Enable Reconnection" left out of account sometimes
     that prevented reconnection.

  4. Undocumented Features

  1. COM Port Redirector and COM Port Redirector Service:
    - Add manually the "DCD=..." line into the "[VPORTPRO]" section
     of the "XWP.INI" file to set up the DCD Virtual serial port "state" :
       a) "DCD=0" - DCD is Off (as was before this version);
       b) "DCD=1" - DCD is On (Default);
       c) "DCD=2" - DCD is controlled by DTR (as in NULL Modem Cable).
                   Available only in the RFC2217 mode;
       d) "DCD=4" - DCD is turned On when client connects to server and
                    DCD is turned Off after client disconnects from server.

  2. Uninhalf.exe utility:
    - The "uninhalf.exe -s" command line uninstalls the NT service only.

  5. Known problems
       
  1. The package has been tested under the following
    operating systems:
    - Microsoft Windows 2003 Server
    - Microsoft Windows 2000 Pro
    - Microsoft Windows XP Pro
    - Microsoft Windows XP Home

  2. 32-bit software programs (developed for the Win32 platform)
     have only been tested.
     16-bit software programs for MS-DOS have not been tested.

  3. In the Telnet RFC2217 mode, the Client mode supports the following
    "usual" Telnet-protocol commands:
    - TN_TRANSMIT_BINARY;
    - TN_ECHO;
    - TN_SUPPRESS_GO_AHEAD.

  4. To test the COM Port Control protocol (RFC 2217) commands,
     the ACORP 56000 Data/Fax/Voice modem and the DIGI One IA server
     have been used.

  5. VCOM-TCP Primary Client:
    - Allows creating up to 10 Virtual COM Ports.
    - Additional Virtual Com Ports can be adding by purchasing drivers from our sales team.

  6. COM Port Redirector and COM Port Redirector Service:
    - Allows (together) creating up to 10 Virtual COM Ports.
    - Provide the TCP-Client and RFC2217-Client mode only in pairs so far
     (as well as the TCP-Server and the RFC2217-Server).

    
      
------------
PLEASE NOTE:
------------
The programs associated in this package may send and/or receive broadcast IP
requests. Since such packets cannot cross the nearest firewall/gateway/router,
please be sure that these IP requests are invisible from outside your network.
We assume that such behavior cannot be considered as "Hacking"
or "Trojan horse's action".