Issues Resolved

Issues Resolved in RTX 2016 with Update 3

Issues Resolved in Update 2 for RTX 2016

General

• Resolved an issue where the Windows security updates after January 2018 that prevent the Meltdown-Spectre vulnerabilities for Windows 7 caused the RTX Subsystem to crash on startup. (2656)

Issues Resolved in Update 1 for RTX 2016

Subsystem

• Resolved an issue where the Structured Exception Handling (SEH) function SetUnHandledExceptionFilter would not get called, which caused SEH to not work as expected for applications built with Visual Studio 2013 and 2015. (2591)
• For Intel® multi-core systems with Skylake architecture, the Port I/O address for speaker (61h) is reserved. The SRTM and KSRTM tools have been updated accordingly.

Issues Resolved in RTX 2016

Installation

• Resolved an issue where the RTX installer would display an error and roll back following installation of .NET 4.0. (2003)
• Resolved an issue which required RTX to be re-activated following a modify of the install or following a full re-install. (1859)

Activation and Configuration

• Resolved an issue where the RTX licensing system would not start on RAID systems, which prohibited the Subsystem from starting. (2289)
• Ensured that an appropriate error message appears when RTX is licensed to an IntervalZero-provided dongle and that dongle is removed from the machine. (1956)
• Resolved various display issues with the Activation and Configuration dialog. (1865, 1933)
• Resolved an issue where a license key included an extra space when it was copied and then pasted into the Activation and Configuration dialog. (1897)
• Resolved an issue where the Activation and Configuration dialog was truncated on Japanese versions of Windows 7. (1889)
• Improved the error messages returned by RtxActivationGUI.exe and RtxActivationUtil.exe to be more accurate. (1704)
• Resolved an issue where the serial number of the connected dongle did not appear when the cursor hovered over the dongle icon in the Activation and Configuration dialog. (1697)
• Resolved an issue where a license was erroneously reported as expired when its corresponding dongle was disconnected from the machine. (1667)
• Ensured that RTXActivationGUI.exe provides positive confirmation when processors are configured successfully. (2344)

Subsystem

• Resolved an issue where the RtssRun affinity mask setting did not override the default Ideal Processor. (2286)
• Resolved inconsistent behavior with shutdown handling on systems using non-VGA video drivers. (1848)
• Resolved a significant time difference between GetSystemTimeAsFileTime and RtGetRtssTimeAsFileTime. (2532)
• Resolved an issue where crash dump files were not generated when Blue Screens or Green Screens occurred at Subsystem start. (1632)

RT-TCP/IP Stack and Drivers

• Resolved an issue where freeaddrinfo crashed when getaddrinfo was called with the AI_CANONNAME flag. (2188)
• Ensured Jumbo packet support for the Rt82580 and Rt8257x Network Interface Cards (NICs). (1947, 1948)
• Resolved an issue where an inconsequential message appeared when the RT-TCP/IP Stack was initialized for the RtIGB driver. (1941)
• Resolved an issue where the RT-TCP/IP Stack produced error output when in non-Verbose mode. (1281)

Tools and Utilities

• Ensured that RtssRun does not allow the /y parameter to be used with the parameter /b (create boot-time process), since a boot-time process cannot be a dynamic process. (1001)
• Removed support for the RtssRun parameter /t, which could previously be used to test registration by loading and unloading a RTDLL. This is no longer needed. (1043)
• Resolved an issue where the RT-TCP/IP Stack would start at boot time when the Subsystem was configured to do the same, even when the Stack was disabled in the RTX Properties control panel. (2181)
• Resolved an issue where the RTSS Object Viewer displayed a Stack size of 0 (zero) while in compact view. (1959)
• Resolved an issue where RtssRun would not find RTSS files if the pathname included a "." and the .rtss extension was not included. (1854)
• Resolved an issue where a Blue Screen would occur when the Control Panel option Automatically expand local memory pool was cleared and the default initial local memory size was used. (1927)

Application Development

• Resolved an issue where if the RTX Application Wizards for both RTX and RTX64 were installed on the system, the wizard that was installed first would be the one launched. (2177)
• Resolved an issue where if a binary contained a tls-dir that was not NULL, RTX de-referenced it, which caused an exception. (2101)

Debugging

• Resolved an issue where the Subsystem could not be stopped after an active debug session ended. (2198)

SDK

• Resolved an issue where a crash occurred when RegCreateKeyEx was called in a RTSS application with parameter lpdwDisposition set to NULL. (2111)
• Resolved an issue where RtCreateProcess could sometimes cause a system hang. (2107)
• Resolved an issue where RtkCreateEvent failed intermittently. (1890)
• Resolved an issue where calls to RtAttachInterrupt intermittently resulted in a crash. (1634)
• Resolved an issue where the function Select would return an incorrect error or cause an exception when it was passed an empty fd set, or an fd set with invalid sockets. (1355)
• Resolved an issue where the Managed Code library displayed an invalid error code upon license failure. (1224)
• Added support for SetFilePointerEx, which resolved an issue where the function ftell was not working properly. (2380)
• Resolved an issue where RemoveDirectory returned an incorrect value when the directory was not empty. (2017)
• Resolved an issue where supported socket option SO_REUSEADDR did not work when used with RTX. (1879)

Issues Resolved in Update 2 to RTX 2012 with Update 5

• Resolved an issue where Windows 7 update KB4088875 caused Windows to start power cycling automatically when RTX 2012 was installed, prohibiting the user from booting into RTX. (2699)

Issues Resolved in Update to RTX 2012 with Update 5

• Resolved an issue where the Windows security update that prevents the Meltdown-Spectre vulnerabilities caused the RTX Subsystem to crash on startup. (2686)

Issues Resolved in RTX 2012 with Update 5

Product Activation

• Resolved an issue where the RTX licensing service did not recognize a valid license at startup. (2586)

Subsystem

• Resolved an issue where the Structured Exception Handling (SEH) function SetUnHandledExceptionFilter would not get called, which caused SEH to not work as expected for applications built with Visual Studio 2008, 2010, and 2012. (2588)
• Resolved an issue where GetSystemTimeAsFileTime and RtGetRtssTimeAsFileTime returned significantly different values. (2595)
• Resolved an issue where the Real-Time Subsystem failed to start on Intel® 6th Generation Skylake machines. (2596)

Issues Resolved in RTX 2012 with Update 4

Subsystem

• Resolved an issue where the subsystem did not handle an exception when there was a failure to acquire memory from Windows during object creation. (2114)

RT-TCP/IP Stack and Drivers

• Resolved an issue where a logic error in the function RtEnumPciCards caused the RT-TCP/IP Stack to not recognize some installed Network Interface Cards (NICs). This issue appeared when NICs were installed in PCI locations that had a non-sequential PCI function number. (2102, 2116)
• Resolved performance issues with the RtIGB driver. (2125, 2127)

Samples

• Resolved an issue where the PCI Scanbus sample did not properly enumerate devices. This issue appeared when devices were installed in PCI locations that had a non-sequential PCI function number. (2117)

Issues Resolved in RTX 2012 with Update 3

Subsystem

• Resolved multiple issues with dongle licensing:
• The Subsystem could not be started if the dongle to which the component was licensed was not plugged in during system startup. (1966)
• A valid RTX component license was not recognized if the dongle to which it was activated was not plugged in during system startup. (1971)

Tools and Utilities

• Resolved an issue where build errors resulted from a RTSS application that was built using the RTX Application Wizard and that included RT-TCP/IP support. (1400)

Issues Resolved in RTX 2012 with Update 2

Installation

• Ensured that the RTX Documentation link under Start > All Programs > IntervalZero > RTX 2012 launches the appropriate Help system. (1770)
• Resolved an issue where the RTX installer was not installing the Managed Code DLL or the Managed Code Help file. (1198)

Licensing

• Resolved multiple race conditions related to the License Validation Service. (1776, 1953, 1954)

Subsystem

• Resolved an issue where RtssRun experienced a delay in launching an application when the dongle to which the Runtime and SDK were licensed was not inserted at boot time. (1422)

RT-TCP/IP Stack and Drivers

• Resolved an issue where Jumbo Packets could not be sent or received by the RtE1000 driver. For a list of the supported devices that support Jumbo Packets, see the RTX Supported Network Cards document available online at http://www.intervalzero.com/technical-support/guides-and-minitutorials/. (1935)
• Resolved an issue where the Intel 82580 Network Interface Card performed inconsistently with a RTSSRelease version of the Rt82580 driver on certain systems. (1946)

Issues Resolved in RTX 2012 with Update 1

Installation

• Resolved an issue where the RTX installer was creating extra directories in the Windows root directories (RTX-1178)
• Resolved an issue where the RTX subsystem merge module did not remove the RTX boot line (RTX-1361)

Activation and Configuration

• Resolved issues around how the RTX Activation and Configuration utility provides license information (RTX-1606, 1473, 1348, 1333, 1299, 1260, 1175, 1114, 1005, 968, 621)

Subsystem

• Resolved an issue where a lock-release violation could occur with the RTX subsystem under certain SMP conditions (RTX-1220)
• Improved our Intel® SpeedStep prevention logic for Vista and Windows 7 systems to allow Windows to properly load balance (RTX-615)
• Resolved an issue where during shutdown of the system, RTSS processors where not properly put in the halt state, causing some systems to not fully power down (RTX-1295)
• Resolved an issue where setting too large of a local memory size would cause the subsystem to hang when stopped (RTX-1486)
• Resolved an issue where RTX prevents a Windows Mini or Kernel dump from happening (RTX-1629)

Debugging

• Resolved an issue where an exception was thrown by the Visual Studio debugger when RtTraceEvent was called within a debug session (RTX-802)
• Resolved issues with debugging multiple RTSS processes within Visual Studio (RTX-1297)

RT-TCP/IP Stack and Drivers

• Resolved an issue where the system would hang while sending and receiving IP packets to/from the RT-TCP/IP Stack (RTX-1475)
• Resolved an issue where threads created by the RT-TCP/IP stack and real-time device drivers did not exit gracefully (RTX-1129)
• Resolved an issue where max socket descriptor failed when more than 64 sockets were used (RTX-1360)
• Resolved an issue where stopping the RTX subsystem when the subsystem was set for automatic start would cause the RT-TCP/IP stack to be the wrong type (RTX-228)

Development Tools

• Resolved an issue where RTX Analyzer reported an error “Unable to create an internal directory.” (RTX-1389)
• Resolved an issue where RTX Server console did not behave correctly if a user was not logged into the system (RTX-1432)
• Resolved an issue where Platform Evaluator failed for Resume/Suspend Thread API tests when the test was configured to use more than one core (RTX-1429)
• Resolved an issue where RTSS Task Manager would generate an exception or fail to start when an RTSS process was run on certain systems (RTX-1326)
• Resolved an issue where RtssKIll and RTSS Task Manager were not displaying all currently running processes or boot time processes (RTX-1587, 1349)

SDK

• Resolved and issue where the function RtExpandLocalMemory returned success when the call failed to expand the local memory pool (RTX-1485)
• Resolved issues where the functions RegCreateKeyEx, RegSetValueEx were not properly writing data to the windows registry (RTX-1420)
• Resolved an issue where the function RegQueryValueEx was returning extra data at the end (RTX-1364, 1388)
• Resolved an issue where the function RtCreateProcess did not default to the global local memory setting when no flags were provided (RTX-1438)
• Resolved an issue where the function RtAttachInterrupt failed when used with shared line-based interrupts (RTX-1272)
• Resolved compiler and linker errors when using RtInitializeProcThreadAttributeList, RtUpdateProcThreadAttribute, and RtDeleteProcThreadAttributeList (RTX-1169)
• Resolved an issue where real-time kernel (RTK) API calls were being called at IRQ_DISPATCH instead of IRQ_PASSIVE (RTX-1270)
• Resolved an issue where the real-time kernel (RTK) creation API calls would not fail correctly when the real-time subsystem was not running (RTX-1381)

Issues Resolved in RTX 2012

Installation

• Resolved an issue where RTX Runtime for Embedded could not be installed on a system on which the full version of RTX was already installed.
• Resolved an issue where the Silent installer ignored the DT_ICONS and SM_ICONS options during install. (RTX-18)

Subsystem

• Resolved an issue where loading and unloading of Rtdlls caused the RTX Subsystem to become unresponsive. (RTX-119)
• Resolved an issue where freeing shared memory in a Windows process linked to RTX could sometimes cause a STOP message on Windows 7. (RTX-748)

Debugging

• Resolved an issue where the RTX Debugger could not launch a process if the path was greater than 128 characters. (RTX-530)

RT-TCP/IP Stack and Drivers

• Resolved an issue where enabling LinkStatus functionality on a stack with a filter driver caused a configuration error. (RTX-242)
• Resolved an issue where communication problems occurred between Windows and RTX when a permanent ARP entry was created on the stack. (RTX-623)
• Resolved an issue where RtssArp did not handle the ARP table correctly when it was updated with a new TTL value (RTX-507)

Development Tools

• Resolved multiple issues with RTX Demo:
• RTX Demo (Managed) crashed on systems with more than one processor assigned to RTX. (RTX-50)
• RTX Demo (Native) crashed when the number of processors was changed after a running RTX Demo instance was stopped. (RTX-56)
• RTX Demo (Native) caused an exception when stopped. (RTX-67)
• RTX Demo (Native) became unresponsive when running the maximum latency test. (RTX-84)
• RTX Demo (Native) caused sclient.exe to crash. (RTX-833)
• Resolved multiple issues with TimeView:
• TimeView only reported data for the processor on which it was running. (RTX-451)
• TimeView did not capture certain events. (RTX-455, RTX-456)

SDK

• Transport Dlls are no longer necessary in RTX 2016. As a result, we have removed the RTX Debug Transport Interface. In addition, the corresponding Properties API functions have been removed from the RTX SDK:
• RtcplGetRemoteDebuggerTransportDllList – retrieved the list of Transport DLLs that the RTX Debug Manager will load on startup.
• RtcplSetRemoteDebuggerTransportDllList – specified the list of Transport DLLs that the RTX Debug Manager will load on startup.

NOTE:  If you run a binary that includes these functions using RtxProp.dll in RTX 2016, you will encounter the error Entry Point Not Found.

• As a result of the licensing improvements made for RTX 2016, the following Properties API function and structure are obsolete and no longer supported:
• RtcplGetLicensedUser – retrieved information about the currently installed copy of RTX, including user name, company name, and PAC license key.
• RTXLICENSEDUSERINFO – retrieved RTX user information.
• Resolved an issue where a blue screen would result from calling CreateFile with a long directory name. (RTX-466)
• Resolved an issue where the file version was not displayed in the file properties for RTSS applications and RTDLLs. (RTX-8)
• Resolved an issue where the function RTKWaitForSingleObject would periodically return WAIT-FAIL. (RTX-94)
• Resolved an issue where the function Select timed out after 64 sockets. (RTX-122)

Issues Resolved in RTX 2011 with Service Pack 1 Updates 1 and 2

The following issues were addressed in RTX 2011 with Service Pack 1 Update 1 and RTX 2011 with Service Pack 1 Update 2:

Issues Resolved in RTX 2011 with Service Pack 1 Update 2

• Resolved an issue where RtWaitForSingleObject returned STATUS_PENDING (RTX-49)
• Resolved an issue where RTX Time View was not logging all object calls (RTX-71)
• Resolved an issue where calling select() after send() would time out and result in an exception (RTX-44)
• Fixed a typo in the API calls RtnIsStackOnline (was RtnIfStackOnline) and RtnIsDeviceOnline (was RtnIfDeviceOnline) (RTX-81)

Issues Resolved in RTX 2011 with Service Pack 1 Update 1

• Resolved an issue where, on machines with multiple network device interfaces, a network device interface experienced latency in sending and receiving data using Broadcast while the other network device interface was disconnected (see Link Status Monitoring above) (RTX-1, 4, 5, 7)
• Resolved an issue where the RtcplAddDeviceToPNPINFFile function failed and returned a 0 (RTX-10)
• Resolved an issue where an exception is thrown due to timeout on select call (RTX-44)
• Ensured that the Control Panel popup menu provides the correct feature options “Add RTX INF Support” or “Remove RTX INF Support” during conversion of a NIC device to or from RTX control (RTX-15)
• Resolved an issue where RtssRun and RtssKill did not handle instances where non-RTDLL files existed in the internal registered RTDLL directory (RTX-16)
• Resolved an issue where RtxRegEnumKeyEx and RtxRegEnumKey caused a crash in ANSI enabled RTSS applications (RTX-14)
• Resolved an issue where RegQueryValueEx returned wide when Unicode was disabled in project settings (RTX-9)
• Resolved an issue where ReadFile did not return the correct error information under certain conditions (RTX-20)
• Resolved an issue where the RTX.Threading.RTWaitHandle.WaitOne() method in the Managed Code library incorrectly computed whether or not it successfully obtained the lock (RTX-35)
• Resolved an issue where an exception resulted when a Windows application using the Managed Code library uses a mutex to communicate with an RTSS application (RTX-21)
• Resolved an issue where the Managed Code library uses method SafeHandle.DanerousGetHandle in an unsafe way that could cause unexpected exceptions (RTX-33)
• Resolved an issue where attempts to debug into a multithreaded section of a sample application in Visual Studio and selecting the Break All option resulted in a system crash (RTX-22)
• Resolved an issue where RTX Demo fails on machines where not all processors are used (RTX-27, 50)
• Resolved an issue where changes to the file RtTcpip.ini were not retained after system restart (RTX-36)

 

See Also