Release Notes for Update 4 for RTX64 3.7

This update resolves various issues as detailed below. This is a cumulative update that contains all of the fixes included in Update 1, Update 2, and Update 3 for RTX64 3.7.

Issues Resolved

• Improves the performance of RTSS-to-Windows communication on Windows 10 Feature Update Version 2004. (9804)
• Resolves an issue where FPU/SSE/PT states on the Intel® Celeron G3900E processor were not properly saved and restored on a thread context switch. (9707)
• Resolves an issue where running RtTcpipServer, RtTcpipClient, and stopping server with another client would cause RT-TCP/IP Stack heap corruption. (9699)
• Resolves an issue where function RtGetProcessIdealProcessor failed with last error ERROR_INVALID_HANDLE under the RTSS configuration when it contained an invalid process handle. (9672)
• Resolves an issue where RtIsAppRunnable returned an unexpected error when given invalid parameters in a Windows build configuration. (9669)
• Resolves an issue where HeapAlloc did not honor the HEAP_ZERO_MEMORY_FLAG. (9663)
• Resolves build errors with STL code in Visual Studio 2019 version 16.6.x (9662)
• Resolves an issue where RtGetDongle sometimes failed when used in a 32bit Windows binary. (9661)
• Resolves an issue where the Monitor utility incorrectly converted event timestamps. (9659)
• Resolves an issue where attempts to start the RTX64 Subsystem on a VirtualBox 6.1.2 virtual machine would result in a Blue Screen. (9657)
• Resolves an issue where RegQueryValueEx returned garbage data when called within a Multi-Byte project. (9655)
• Resolves an issue where RtCreateSharedMemory crashed when the asking size was larger than the existing shared memory region size. (9654)
• Resolved an issue where multiple threads using TLS could cause the RTX64 Subsystem to hang. (9653)
• Resolves an issue where a Blue Screen resulted when parameter IpApplicationName in Real-time function RtCreateProcess was set to a path name that contained spaces surrounding double-quotation marks. (9650)
• Resolves an issue where Real-time API RtGetModuleFileNameEx did not return full path. (9649)
• Resolved an issue where RTX64 could not be run on VMware Workstation 15.x. (9648)
• Resolves an issue where a NIC would sometimes fail to initialize properly after its IP addresses were added and removed. (9373)
• Resolves and issue where having more than 12 IP addresses for an interface would cause the Stack to throw an exception. (9372)

Known Issues

• During device conversion, you may encounter an error prompt that the driver is not digitally signed. This is due to issues with the Rtx64PnPNet.cat file. If you experience issues while attempting to convert a device, contact support@intervalzero.com for updated versions of the Rtx64PnPNet.cat and Rtx64PnPNet.inf files digitally signed by IntervalZero.
• RTDLL projects created by the RTX64 RTDLL template do not build when the configuration is set to RTSSRelease. This issue is fixed in RTX64 4.0.
• Uninstalling the RTX64 SDK from a machine running Update 4 for RTX64 3.7 on Windows 10 Update Version 2004 might cause the HASP driver to become corrupted. One symptom of HASP driver corruption is a lag in Control Panel responsiveness. If HASP corruption occurs, reinstall Update 4 for RTX64 3.7. (9587, 9582)