Update notes:

1. Terminal emulators: The HTTP proxy functionality was fixed.
2. 3270 Web Server: The HTTP proxy functionality was fixed. Proxy sessions are managed like Web sessions.
The Javascript files were updated to work with new browsers that removed some old functions.
The Java applet was removed from the menus for security reasons, but the files are still available.
3. The Help system was updated. More information about Registry usage is included.
4. InetVTx00 configurations were cleaned up.
5. OpenSSL 1.1.0h is supported.
6. Services don’t log Interrogate events any longer.

Update notes:

1. An old or invalid UpdateCode.txt file won’t result in displaying an error that
an invalid code has been entered.
2. Automatic license updates can now be done from a secure https web server.
3270:
3. Natural File Transfer upload: We fixed a bug and improved the speed substantially.
4. A problem with an incomplete Query reply response resulting in a blank screen
when connecting, has been fixed.
5. Inet3270 can allocate LUs from a shared pool file. Contact us for details.

For more information click here.

Update notes

1. The Winet install program has been updated to make a clear distinction between
Complete and Compact setup. Note that certain modules e.g. Inet3270Web server can
only be installed by using the Custom setup.

2. When a Custom Install (not to be confused with the Custome Setup above) is done
by having a CUSTOM folder in the same location as the install file, the current folder
will be in a temporary location. To set the current folder to the default location of
C:\Winet\custom, use the following line in CUSTOM.BAT:
cd /d %1

3. The Microsoft “Print to PDF” driver is faulty which used to crash Winet when using
this printer as the default printer. Winet now handles the problem.

4. The model number for legacy 3270 terminals (non-TN3270E) has been properly implemented.

5. The model number for 3270 terminals is now properly reported in a Partition Query command.

6. Cursor blinking has been improved. Previously a slow setting for the blink rate in
Windows could lead to the cursor not blinking at all.

Update notes.

1. Winet contains useful facilities that can lead to passwords being revealed. They are Tracing, Macros and Scripts. All of these can be protected by using registry access policies that disallow unauthorised users from misusing it.
Certain users don’t want to implement registry access policies and the following changes have been made to accommodate them:

1.1. The network traffic portion of traces are now encrypted using strong encryption with a key protected by a secret password. Only GPvNO can decrypt it for support purposes. If a user wants to view it, the trace file needs to be sent to GPvNO who will decrypt and send it back to the user after verifying the authorisation level of the user. If the user does not want GPvNO to have access to passwords, the trace
must only be started after a password has been entered.

1.2. The macro recording facility can only be used if the user license (Dontwipe.me!) allows it.

1.3. The NotifyKeyboard property is set to “disabled” when starting and can only be set to “enabled” when licensed as in 2. This ensures that the OnKeyboard event can’t be used.

1.4. The GetString method can only be used if licensed as in 2.

2. The update code to update the license file (Dontwipe.me!) can also change the number of users.

3. A number of possible vulnerabilities has been eliminated.

4. Certain malfunctioning anti-virus programs could lead to a connection being reset the first time that Winet starts up with auto connect. Winet solves this problem by re-trying the connection several times before giving an error.

5. Special (diacritical) characters can be entered by typing a key to display the Special Character dialog at a position relevant to the key e.g. typing “Ctrl e” shows all the diacritical forms of “e” like ë, é, è, ê, etc. allowing you to select the correct one. The “Ctrl e” key must be set up in the keyboard mapping dialog by selecting “Special key dialog*” as the key and adding the “e” in the Text field.

6. 3270 fixes:

6.1. If a UTF-8 file with a Byte Order Mark is uploaded using NFT the BOM is removed.
6.2. If data was received while viewing a history screen, that screen was corrupted. That has been fixed.
6.3. 3270 data stream printing is now properly implemented.

7. SSH
The SSH implementation has been updated to support more secure algorithms. This version is based on the PUTTY v 0.67 code.

Changes:

OpenSSL 1.0.2g is provided.

Facility to update license file (Dontwipe.me!) automatically from File or Web Server.

Fixes:
3270: Natural File Transfer download returning wrong status.
UTS60: Proper Unicode special symbols.
All products:
Saving most recent custom printer.
Printer overprinting for bold and underline.

Main updates:

OpenSSL 1.0.2e is provided.

Translation tables now have friendly names reflecting the associated Code Pages.

The default EBCDIC Translation tables for the old legacy fonts have been replaced with tables for a number of standard IBM Code Pages.

Web3270 script files have been updated to be compatible with the latest versions of browsers.

Various bugs have been fixed and small enhancements implemented.