Release Notes for Update 2 for RTX64 3.2

Issues Resolved

Resolved an issue where Windows security updates that prevent Meltdown-Spectre vulnerabilities for Windows 10, Windows 8.1, and Windows 7 caused the RTX64 Subsystem to crash on startup. (7131, 6608, 6514)
Resolved an issue where C Runtime function fflush returned an error when used in the RTSS environment. (7135, 6671)
Resolved an issue where the Subsystem failed to start on a Skylake i9-7900X system that included Intel® Advanced Vector Extensions 512 (AVX-512) instructions. (7130, 6573)

NOTE: This contains code that uses newer INTEL XSAVES functionality when supported, which can speed up the context switching between threads.

Resolved an issue where the Subsystem would crash on Symmetric Multiprocessing (SMP) systems when RTX64 Structured Exception Handling (SEH) logic was stressed. (7125, 6576, 6327)
Resolved an issue where file content was overwritten when fopen was used to open a file in append mode. (7129, 7127, 5951, 5745)
Resolved an issue where the Subsystem crashed on reboot when the TimeQuantum and HALTimerPeriod values were the same and the RT-TCP/IP Stack was enabled. (7126, 5995).
Resolved an issue where RtWaitForSingleObject and RtWaitForMultipleObjects did not work correctly with timeout values above 2^32 / 10000 (429496) milliseconds. (7124, 5346)
Resolved an issue where Real-Time function RtMapMemory caused a Blue Screen in Windows processes linked to RTAPI when called before RTAPI’s DLLMain. (7136)

On repeated reboots of a system the RTX64 Subsystem may fail to allocate the requested amount of local memory even when sufficient memory is available. This might manifest itself by the RT-TCP/IP Stack generating an error: Internal error: RtQueryRtssInformation failed = 0x0 or rtssrun the parameter is incorrect. (7156)

For more information, see the TechNote The RTX64 Subsystem Fails to Allocate the Requested Amount of Local Memory.