Release Notes for RTX64 3.2
Key Features
General
- Added support for the Intel® Apollo Lake platform. (5493)
- Added support for Windows 10 Creators Update Version 1703.
RT-TCP/IP Stack and Drivers
- Added support for multiple (up to 12) IPv4 Addresses and Netmasks for a single physical interface. You can now configure multiple IPv4 Address/Netmask pairings in the RTX64 Control Panel on the Manage Interfaces and Filters page. (5471)
- Incorporated the RTX64 Intel® PCH Network Interface (RtIPCH) driver, which provides support for the Intel i219 Network Interface Cards (NICs), as well as updated support for several Intel ICH8, ICH9, ICH10, and PCH controllers. This driver was previously released as a BETA on the Support site. See the RTX64 Supported NICs document for a list of supported devices: https://www.intervalzero.com/technical-support/guides-and-minitutorials/
Tools and Utilities
- Added new options to the Configure RT-TCP/IP Stack Behavior page in the RTX64 Control Panel:
- Set the time-out on IP fragmentation
- Set the maximum number of ARP entries allowed for the RT-TCP/IP Stack
Previously, these values could only be changed in the Windows registry.
Samples
- Added new options to the RtTcpipClient and RtTcpipServer program samples to support multiple IPv4 addresses. (5600)
- RtTcpipClient: a=<ip> switch – Specify the IP to bind the client socket to.
- RtTcpipServer: /m – Run multiple instances of the server.
Issues Resolved
Subsystem
- Resolved an issue where the RTSS processor cache would sometimes become polluted, causing page faults or other exceptions. (5647)
RT-TCP/IP Stack and Drivers
- Resolved an issue where several Realtek device entries were missing from the RTX64 driver list and INF file. (5596, 5597)
- Resolved an issue where the RtI10GB driver source redistributable used the wrong version of ToolsVersion, which resulted in a warning. (5437)
- Resolved an issue where RtssPing did not work with the Intel 82579LM Network Interface Card on certain systems. (5163)
- Resolved an issue where the timeout interval in select was incorrect. (3988)
- Resolved an issue where changing the Link Status Thread Priority to a nonzero value caused a RtE1000 NIC to not initialize properly. (5226)
- Added device friendly names to IP configuration messages printed to the Server Console. (5669)
Tools and Utilities
- Resolved an issue where the RTX64 Analyzer did not output the installed extensions for Visual Studio 2017. (5616)
- Resolved an issue where the RTX64 Analyzer did not detect Visual Studio 2017 Community Edition. (5617)
- Ensured that the RTX64 Task Manager does not show the RTX64Nal.rtss process. (5559)
- Resolved an issue where the Location of session logs field in the Change Monitoring Settings page of the RTX64 Control Panel was not editable. (5018)
- Resolved an issue where the RTX64 Control Panel did not display the correct status of the RT-TCP/IP Stack when the Subsystem was started by running an application. (5708)
Samples
- Resolved an issue where the RtRtl8168 driver source was missing several header files, which prevented the project from being built. (5735)
Notes
RT-TCP/IP Stack and Drivers
- The following Intel 82579 controllers are now supported by both the RtE1000 and RtIPCH drivers:
- Intel® 82579 Ethernet Controller Integrated with the Intel C202 PCH, C216 PCH, or C220 PCH (0x1502)
- Intel® 82579V Gigabit Network Adapter
See the RTX64 Supported NICs document for the minimum supported RTX64 version for each driver and device:
https://www.intervalzero.com/technical-support/guides-and-minitutorials/ (RTX64 Documentation tab)
SDK
- API function HeapAlloc causes an access violation when it is passed an invalid heap handle. In previous versions, HeapAlloc failed with ERROR_INVALID_PARAMETER. (5349)
- The RTX64 SDK requires the following Visual Studio 2017 workload:
- Desktop development with C++
If this workload is not currently installed for Visual Studio 2017, you must manually install it using the appropriate Visual Studio installer file (vs_<edition>.exe). For example, vs_professional.exe. To do this, follow the steps below:
- Browse for and open the Visual Studio 2017 installer file (
vs_<edition>.exe). - Under Workloads / Windows, select Desktop development with C++.
- Under Summary, make sure that the optional feature of this workload MFC and ATL support (x86 and x64) is selected.
NOTE: This ensures that all RTX64 samples can be built out-of-the-box.
- Click Install.
- After the new workload is installed, click Launch.
NOTE: If the above workload is not installed, projects and samples created with the RTX64 application templates will not build.
Samples
-
Installing the Win10 SDK through the Visual Studio installer may result in errors when building RTK drivers. Errors include: C1083: Cannot open include file: 'C:\Program Files (x86)\Windows Kits\10\Include\10.0.15063.0\shared\warning.h', To resolve this issue, use the Windows 10 SDK available from https://developer.microsoft.com/en-us/windows/hardware/windows-driver-kit (5830)
Known Issues
General
- The Microsoft version detection DLL does not make it obvious that Visual Studio 2017 15.1 is detected when both the 15.0 Community and 15.1 Professional editions are installed. In such a scenario...
Visual Studio 2017 15.0 is displayed as:
InstanceId: e9d9d200 (Complete)
InstallationVersion: 15.0.26228.10 (4222126369538058)
Visual Studio 2017 15.1 is displayed as:
InstanceId: 53f47098 (Complete)
InstallationVersion: 15.0.26403.0 (4222126381006848)
(5717)
Installation
- The RTX64 SDK installer does not install the
RTX64VSSupport.vsixVisual Studio extension on machines where Visual Studio 2017 Community Edition is installed. As a result, important features, such as the RTX64 Project Templates, are not available. To work around this issue, manually install theRTX64VSSupport.vsixfile:
- Open Windows Explorer and navigate to
%RTX64SDKDir3%\VSExtensions\ - Double-click the file
RTX64VSSupport.vsix.
(5793)
RT-TCP/IP Stack and Drivers
- Basic Network Interface Card (NIC) functionality does not persist when the RTX64 Runtime is upgraded to version 3.2. If you have converted a NIC to RTX64 control, you must update the device with the latest RTX64 driver following the upgrade to RTX64 3.2. See Converting a Windows Device to an RTX64 Device for information on updating driver software. (5766)
- The Client/Server transmission rate drops when running large packets with the RtIPCH driver. When running with UDP, a timeout occurs with function select. (5815)
- RtssIPConfig displays the same netmask for all IPs configured for a single NIC, even when multiple, unique IPv4 address and netmask pairs have been configured. (5831)
Tools and Utilities
- Monitoring fails when the location of monitor logs is changed to a location in the Public Documents folder other than the default location (
C:\Users\Public\Documents\IntervalZero\Monitoring). (5832) -
On the German language edition of Windows 10, an exception occurs when a user that is not in either the RTX64Administrators or RTX64Users group, and also has not been elevated to Windows Administrator, attempts to open the RTX64 Control Panel. (5883)
Debugging
- The Visual Studio debugger Modules window does not display the RTDLL module type or breakpoints during an active debug session when the debugger is attached to a running RTSS process that has already been debugged with Attach to RTSS Process. (5802)
