Release Notes for RTX64 4.3

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

 

---

Key Features

RTX64 Runtime

General

• Added support for Windows 11 version 22H2.
• Added support for Windows 10 version 22H2.
• Added support for 12th Gen Intel® Core™ processors. (10522)
• Added support for Intel® Thread Director (ITD) in the Subsystem to capture a thread’s ideal core.
• Added APIs for querying a system’s core class as well as a thread’s ideal core.
• Added a new HFIClassID field to the text output for the Thread Destroy monitoring event. This field holds the Intel® Hardware Feedback Interface (HFI) Class ID of the associated real-time thread at the time the thread terminated. (10544)
• Added two new fields to the text output for the Context Switch monitoring event: (10544)
• Field NewHFIClassID holds the Intel® Hardware Feedback Interface (HFI) Class ID of the associated real-time thread at the time the thread was context-switched TO a processor.
• Field OldHFIClassID holds the Intel® Hardware Feedback Interface (HFI) Class ID of the associated real-time thread at the time the thread was context-switched AWAY from a processor.

NOTE: You can run the standalone HybridInfo utility, available from the IntervalZero Support Site, on 12th Gen processor systems to output Intel Hybrid Core information, including Intel Thread Director (ITD) and software Thread Class ID, for different sets of Intel® assembly instructions.

Subsystem

• Added a new Object Name field to the text output for the Handle Close monitoring event, which holds the name of the object whose handle is being closed. (10358)

Network and Drivers

• Incorporated the RTX64 Intel 2.5 Gigabit Ethernet Controller I225/I226 Network Interface driver (RtNalIGC), which provides support for Intel 2.5 Gigabit Ethernet Controller I225/I226 devices. See the RTX64 Supported NICs document, available from the Customer Center, for a list of supported devices.

Tools and Utilities

• RTX64 Analyzer now detects Visual Studio 2022.
• Added functionality to RTX64 Console that allows you to search console output through a Find dialog. (10314)
• Redesigned the RTX64 Monitor utility to add functionality and improve usability:
• Monitoring session controls (play, pause, stop) are now always accessible (these were previously only available on one screen).
• Monitoring status is always visible (status was previously only visible on one screen).
• You can now choose which events to monitor and create session triggers from events on the same screen.
• Session triggers can now be created through drag-and-drop.
• Added support for stop triggers (triggers that automatically stop a monitoring session).
• Added predefined sets of monitor events to the Change monitoring settings page in the Control Panel. You can choose one of the sets of events, such as Collect memory events, to only collect events specific to that area of focus. (10461)
• Resolved an issue where the Memory Heap Utilization Graph in Tracealyzer sometimes displayed a 'double-counting' of Local Memory allocations, reflecting both the user applications’ memory requests (such as calls to RtAllocateLocalMemory) and the creation of the Local Memory Pools from which memory is allocated to user applications. See the topic Allocation Spaces in Local Memory for more information about real-time process memory usage. (10356)

 

---

Issues Resolved

RTX64 Runtime

Installation

• Resolved an issue where the Advanced Installer Sample would not automatically load the RTX64 Merge Modules when they were installed to a non-default directory. (10251)

Tools and Utilities

• Resolved an issue where RTX64 Analyzer did not accurately report Windows 11/10 feature versions. (10510)
• Resolved an issue in the RTX64 Monitor utility where the Number of pre-trigger events to collect entry field remained configurable even when no session triggers were selected. (10435)
• Resolved a user experience issue with the RTX64 Monitor utility where session triggers appeared to be set when in fact they were not. (10422)
• Made improvements to the control for setting the RTX64 Console window buffer size on the Configure Real-Time Application Output page in the Control Panel, including improved error checking when a non-valid value is entered. (10465)
• Resolved issues where starting and stopping a monitoring session repeatedly would cause unexpected exceptions. (10239)
• Resolved an issue where the RTX64 Console would not output any data if the Real-Time Subsystem was configured to auto-start. (10345)
• Resolved an issue where monitoring session folder names included a time stamp in Greenwich Mean Time (GMT) instead of the user's local time zone. (10518)
• Improved the KSRTM (Kernel System Response Time Measurement) utility to display CPU data in decimal format rather than hex. This is consistent with SRTM (System Response Time Measurement) output. (10484)
• Resolved an issue where the Memory Heap Utilization Graph in Tracealyzer sometimes displayed a 'double-counting' of Local Memory allocations, reflecting both the user applications’ memory requests (such as calls to RtAllocateLocalMemory) and the creation of the Local Memory Pools from which memory is allocated to user applications. See the topic Allocation Spaces in Local Memory for more information about real-time process memory usage. (10356)
• Resolved an issue where monitoring events SRI to Windows and SRI to Windows Return were missing from the list of events to collect in the Control Panel and RTX64 Monitor Utility. (10705)

 

---

Notes

RTX64 Runtime

Compatibility

• RTX64 Vision 4.1 is compatible with RTX64 4.3.
• Unlike with previous versions, RTX64 4.5 is not always compatible with RTSS processes built with a prior version of RTX64 (though all 4.x versions 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.x.

Licensing

• Licenses for RTX64 3.x and previous versions will not work with RTX64 4.5.
• 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 11 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)
• The advanced NAL interface properties Number of receive buffers and Number of transmit buffers must be a multiple of 8. (8159)

Tools and Utilities

 

---

Known Issues

RTX64 Runtime

General

• RTX64 is incompatible with the Windows Memory integrity security feature, which uses hardware virtualization not supported by RTX64. This security feature is turned off by default on Windows 10, but it's enabled by default on some Windows 11 systems. This feature must be turned off before you install RTX64 Runtime. See the TechNote RTX64 Runtime is Incompatible with Windows Memory integrity, available on the Support Site, for more information. (10893)
• The RTX64 Subsystem cannot be stopped after a process that used _beginthread or _beginthreadex to spawn child threads is forcefully terminated while those child threads are still running. To work around this issue, you must restart the system. To avoid this issue, use CreateThread to spawn child threads, or avoid forcefully terminating a process (using RtssKill or some other means) that used _beginthread or _beginthreadex to spawn child threads that have not exited. (10894, 10700)
• Windows shutdown handling does not function properly on some Intel® 12^th Gen systems running Windows 11. When this occurs, RTX64 cannot perform its own shutdown handling. (10673)
• When the RTX64 Help is launched from the RTX64 CD welcome screen and viewed in Internet Explorer 11, clicking links in the Help may cause script errors such as Error: Object doesn't support property or method 'startsWith'. (10126)
• RTX64 user groups are not removed when the RTX64 Runtime is uninstalled. (9911)
• The Activation and Configuration and command line utilities fail silently (do not display an error) when an attempt is made to activate an RTX64 Runtime component on a Virtual Machine when a dongle is not present. (9225)
• 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)
• 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)
• 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.
• Running the command to create a custom response file (RTX64_<version number>_Runtime_Setup.exe /r /f1 <file location>) using either the RTX64 Runtime or SDK Installer results in a blank error dialog if the specified <file location> is not valid. (10662)

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

• Tracealyzer displays the wrong core number for custom events generated from a Windows application. However, the process ID (PID) and thread ID (TID) in the custom event do correctly identify the proxy process and thread that generated the event. (10788, 10873)
• An application warning appears when you use the keyboard shortcut Ctrl+N to open a new window in Tracealyzer: Unable to create new window: Object reference not set to an instance of an object. To work around this issue, open a new instance of Tracealyzer. (10753)
• The Heap Allocation Fail event does not appear in monitoring log files or Tracealyzer. (10822)
• When the amount of generated monitoring data exceeds the amount of memory dedicated to monitoring, automatic stop conditions such as Maximum number of events to collect or Maximum session log size may cause the active monitoring session to enter a false-stopped state. To resolve this, start a new monitoring session using RTX64 Monitor and make sure the tool shows the new session as running. (10797)
• If the system is shut down while the Subsystem is running and monitoring is enabled but not started, a hidden, locked monitoring session file might remain when the system is rebooted. Note that this file consumes memory associated with the configured maximum session log sizes. (10787)
• The Memory Heap Utilization Graph in Tracealyzer may display a 'double-counting' of Local Memory allocations, reflecting both the user applications’ memory requests (such as calls to RtAllocateLocalMemory) and the creation of the Local Memory Pools from which memory is allocated to user applications. See the topic Allocation Spaces in Local Memory for more information about real-time process memory usage. (10296)
• Tools in RTX64 4.0 and later 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)