Release Notes for RTX64 2013 with Service Pack 1 Update 3

Issues Resolved

Resolves an issue where internal registry information was not properly removed on modifying or uninstalling features. Under some conditions on reinstall of the Runtime the Activation and Configuration utility incorrectly showed the subsystem was already configured. (2439, 2507)
Resolves an issue where if the Microsoft .NET Framework failed to install, the RTX64 installation would continue. (2130)

Resolves an issue where using priority promotion with a large number of mutexes could lead to large latency and undeterministic performance of the subsystem. This scalability issue was reproducible when the number of mutex objects was larger than 10,000. (2468, 2437)
Resolves an issue where EnterCriticalSection could fail silently if called with an invalid CRITICAL_SECTION structure. (2560)
Resolves an issue where under memory stress conditions pieces of the subsystem could be swapped out of memory and the launching of an RTSS process could cause a system to crash. (2629)
Resolves an issue where the subsystem was unable to correctly determine the number of available processors and would not start. This issue only occurred on systems built from ghosted images. (2639)

Resolves an issue where RtssRoute is not documented. (2461)
Resolves an issue where editing the Time Quantum value in the Control Panel has no effect. (2631)

Resolves an issue where multiple network interfaces on the same subnet could not be pinged. (2584)
Resolves an issue where repeatedly calling sendto with a non-existent IP address would cause unexpected latency within the calling RTSS application. (2622)

Resolves an issue where GetModuleHandle did not properly handle a parameter of NULL, which should return the file used to create the calling process (.rtss file). (2466)
Resolves an issue where calling RtEnumProcessModules from an RTSS process caused an access violation. (2443)