Release Notes for RTX64 4.1

• Key Features
• Issues Resolved
• Notes
• Known Issues
• API Changes Between RTX64 3.x and RTX64 4.x

 

---

Key Features

RTX64 Runtime

General

• Improved the performance of RTSS-to-Windows communication on Windows 10 Feature Update Version 2004 from the initial implementation in the RTX64 4.0.1 patch release. (9578)

Subsystem

• Implemented RTSS Timer Tick Compensation to account for SMI and other non-maskable system behaviors that impact latency and cause jitter. (8967)

Tools and Utilities

• Added RTX64 Console, an output display console window that can be configured to display for each real-time application or as a single instance for all real-time applications, similar to previous releases.
• Added functionality to the Control Panel to support configuration of RTX64 Console (one or per process) and logging of real-time application output.
• Added functionality to the Control Panel to support configuration of remote debugging connections.
• Improved RTX64 Analyzer to display a more complete installation history. (7898)
• Added functionality to RtssRun and Task Manager that allows you to specify the time-of-allocation for the process external MSpace. (9640)
• Added the ability to reset default values for the memory profile settings Available system memory and Percentage expected to be used by Windows. (8844)

 

---

Issues Resolved

RTX64 Runtime

Help

• Resolved issues where some Help links in Tracealyzer targeted the wrong RTX64 Help system. (9574)

General

• Resolved an issue where RTX64 would sometimes change the system power scheme during Windows shutdown, resulting in a system hang. (9403)
• Resolved an issue where FPU/SSE/PT states on the Intel® Celeron G3900E processor were not properly saved and restored on a thread context switch. (9680)

Licensing

• Improved the warning message that appears after a change is made to the RTSS boot configuration via command line. (9203)

Subsystem

• Resolved an issue where the Subsystem could not be stopped following a call to the Managed Framework Intervalzero.RTX64.RTAPI Namespace. (9306)

Network and Drivers

• Resolved an issue where the X550T Network Interface Card would output error EEPROM Checksum Is Not Valid to the RTX64 Server console window. (9438)
• Resolved iPerf TCP transmit performance issues with the RtNalI10GB driver. (9619)

Tools and Utilities

• Resolved an issue where RTX64 System Tray would not display a toast notification when the RTX64 boot configuration was not available. (7851)
• Resolved an issue where RtssRun did not display an error code when RtCreateProcess failed to launch a real-time application. (9583)
• Fixed alignment issues in the RTX64 Activation and Configuration utility. (9750)
• Resolved these issues with RTX64 Task Manager:
• Resolved an issue where RTX64 Task Manager sometimes displayed an unusually large value for CPU usage. (8625)
• Resolved an issue where RTX64 Task Manager didn’t accurately report CPU usage for system configurations where only one processor was assigned to Windows. (9921)
• Resolved an issue where scheduled tasks added via the Add as scheduled task option in Task Manager did not include process arguments. (9266)

 

---

Notes

RTX64 Runtime

Compatibility

• Unlike with previous versions, RTX64 4.0 is not always compatible with RTSS processes built with a prior version of RTX64 (RTX64 4.1 and 4.0 are compatible). See API Changes Between RTX64 3.x and RTX64 4.x for a list of deprecated and modified API calls. You can use the new RtssRun flag /c to check if an existing RTSS binary will run on RTX64 4.0.

Licensing

• Licenses for RTX64 3.x and previous versions will not work with RTX64 4.1.
• RTX64 4.0 and above only support small form factor dongles. The standard dongles supported by previous versions are no longer supported. If RTX64 4.1 is installed on a system, standard dongles will no longer work for previous versions installed on the same system.

General

• Upgrading to a new Windows 10 feature update on a machine where the RTX64 Runtime is already installed results in deletion of the RTSS boot configuration. To work around this issue, set the RTSS boot configuration through the RTX64 Activation and Configuration utility. See the topic Setting the RTSS Boot Configuration for more information.
• The RTX64 installers no longer install Software Identification (SWID) tags.

• When Intel® TurboBoost is enabled in the BIOS, Windows core frequency is boosted when the RTX64 Subsystem starts. This is because RTSS cores are in an idle loop for pooling those SRIs from Windows to RTSS cores. On Coffee Lake systems, specifically, whenever there is a core in the idle loop, the remaining cores' frequency is boosted. To avoid this, we recommend you disable Intel® TurboBoost in the BIOS.

Network and Drivers

• When creating a custom NIC driver, we recommend that the driver binary name not match the default NIC driver names provided by RTX64. The default driver names are used by the Control Panel to set up interfaces with the optimal defaults based on the provided drivers logic. (8318)
• All NIC driver source now generates RTDLLs with the suffix _custom (e.g. RtNalIPCH_custom.rtdll). (8319)
• Custom NIC drivers should not use the C Runtime library, and must not call printf. (6438)
• A Windows 10 feature update may cause devices previously converted to RTX64 control to convert back to Windows control. Following a Windows feature update, verify that all converted devices remain under RTX64 control, and re-convert any that were reset to Windows control using the steps documented in the topic Converting a Windows Device to an RTX64 Device.
• The maximum value for the TCP/IP Stack's maximum concurrency setting is now 10340. (9151)

 

---

Known Issues

RTX64 Runtime

General

• The RTX64 power plan and RTX64 user groups are not removed when the RTX64 Runtime is uninstalled. (9918)
• When multiple RTX64 SDK versions are installed on the same machine, only one shortcut to the Activation and Configuration utility will appear in the Start menu. This shortcut might not always be listed under the most recent SDK version. (8359)
• If you install the RTX64 3.7 Runtime on a machine on which the RTX64 4.x SDK is already installed and then activate both products, the Activation and Configuration utility does not allow you to set the RTSS boot configuration. (8647)
• The Activation and Configuration and command line utilities fail silently (do not display an error) when an attempt is made to activate an RTX64 component on a Virtual Machine when a dongle is not present. (9225)
• Licenses cannot be activated to a small form factor dongle, either from the Activation and Configuration utility or command line, on a remote system accessed via Windows Remote Desktop. This is due to a security limitation with the third party dongle software. Attempts to activate to the dongle in this scenario will result in an error such as Error 19 (Unable to read dongle memory). Note that this issue does not happen when other remote connections, such as VNC or Team Viewer, are used.

Subsystem

• When the RTX64 Watchdog timer is configured to monitor for runaway threads, debugging an RTSS process may cause the Subsystem to become unresponsive. (9937)
• When real-time process output is configured to display in a separate console window for each real-time process (default), output for the Network Abstraction Layer (NAL) and RT-TCP/IP Stack appears in separate consoles, when such output should appear in a single console that closes when the Subsystem stops. This will be fixed in a future release. (9884)

Network and Drivers

• Real-time API RtnGetArpTable() and the RtssArp.rtss utility display device names truncated to 15 characters. The full case-sensitive device name must be used when adding or deleting an ARP entry. (9222)

Tools and Utilities

• The keyboard shortcuts used to scroll the RTX64 Console window do not work in the current version of RTX64. This issue will be fixed in a later release. (9436)
• Tools in RTX64 4.0 and above exhibit various issues on systems running Windows 10 2016 LTSB (Long Term Servicing Branch). Due to these issues, we have performed limited testing and will not be claiming support for such systems. If you require Windows 10 2016 LTSB support, please contact your Sales representative. (9206)