Known Issues

Reported as of Update 1 for RTX 2016

• Running RTX Demo with the sound enabled will cause Intel® Skylake systems to hang.
• The default starvation behavior, Yield to Windows, causes machines to hang. To avoid this, change the starvation behavior in the Starvation tab of the RTX Control Panel. (2624)

Reported as of RTX 2016

• Running multiple instances of Pppd simultaneously can cause RTSS exceptions. Running a single instance yields the expected output. (2222)
• RTX does not correctly handle Unicode strings that contain non-English characters. (1880)
• A RTSS process requires a valid license to start. When an RTSS process is scheduled to load at boot-time it is dependent on the RTSS Subsystem being able to check for a valid license. This process might take several seconds, especially if a previously unseen dongle is required for license validation. Because of this delay, during boot-time start the RTSS subsystem will use the first license it finds that will successfully validate a license request. The first valid license found may not be the same license used once the Subsystem has had the opportunity to confirm all licenses and dongles found on the system and determine which is the most-recently-installed and best choice. The Subsystem will wait up to 2 minutes for a valid license to be found. If none are found, the license validation request will fail and the Subsystem will not load the registered boot-time process. Note that you will see a blank screen during the license check if you boot up a machine with boot-time processes registered without a valid license. Information on a boot-time process load failure will be added to the Windows Event Viewer to help users diagnose the cause of a boot-time load failures.
• The RTSS Subsystem’s access to memory is limited by the amount of non-paged pool memory available on the system. Because of this, it is recommended that RTSS processes that require large amounts of contiguous memory be registered to run at boot-time. This allows memory allocation to happen early in the Windows boot process, before it becomes too fragmented or allocated to other Windows drivers. If as a boot-time process your RTSS application is still unable to allocate enough memory, you can create a Windows driver that can allocate memory earlier in the Windows boot process than a RTSS registered boot-time application. After the Windows driver allocates the memory needed, it can use the Real-Time Kernel API (RTK) to provide that memory to RTSS applications for use. For more information, see the related sample available from the IntervalZero Support site.
• The IntervalZero Real-Time Debugger does not display the Process ID (PID) for RTSS processes being debugged. A GUID is displayed instead. This is expected behavior when Visual Studio is used to debug a non-Windows process. The PID is displayed in the Output window.
• The RTSS thread priority shown in the Visual Studio Debugger Threads window will display Unknown if the real-time priority value does not correspond to a Windows thread priority. RTSS thread priority values range from 0 to 127 and Windows thread priorities range from -15 to 15. If a real-time priority value matches a Windows value, the priority text displayed in the debugger Threads window will not be meaningful.
• You must close the Visual Studio debugging session before you stop the RTX Subsystem. A Green Screen may occur if you use the IntervalZero Real-Time Debugger while the Subsystem is in the process of shutting down.
• Hard-coded (embedded) and data breakpoints are not supported. Hard-coded breakpoints will cause Visual Studio to crash. (2379)
• The IntervalZero Real-Time Debugger does not support Single-Step after Break All is used. To work around this, set a breakpoint in the application and press F5.
• Using RtssKill may still list the process under debug running even after process under debug was killed.
• When you hit Break All on a CPU-intensive running RTSS application and then stop debugging, Visual Studio can lose the context. When this occurs, Visual Studio displays a dialog indicating Microsoft Visual Studio has stopped working. To continue, close the program and restart the debug session.
• When you place an instruction pointer on a breakpoint, you need to step twice to move beyond the breakpoint.
• The API call RaiseException, which raises an exception in the calling thread, doesn't work with the IntervalZero Real-Time Debugger.
• Execution cannot continue after Visual Studio breaks on first chance exception within a process. You must stop debugging.
• Boot-time processes cannot be used in combination with RTX 2016 Runtime or TCP/IP Stack licenses that are node-locked to a standard (non-small-form-factor) dongle. (2343)
• Uninstall of RTX fails to remove two files from the system (2273):
• C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\kb2cennn.rlw\IntervalZero\IntervalZero.pkgdef.deleteme
• C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\kb2cennn.rlw\IntervalZero\RTX.snippet
• To build samples with Intel Compiler 15 and Visual Studio 2015 in a RTSSRelease configuration, you must add the following libraries in Properties > Input:
• legacy_stdio_definitions.lib
• legacy_stdio_wide_specifiers.lib
• The Subsystem occasionally fails to stop after RT-TCP/IP Stack applications are prematurely terminated using RtssKill. (2381)
• Performance may be negatively impacted when a high number of mutex objects or critical section objects are used. To avoid a performance hit in these scenarios, we recommend that you select the Priority inversion protocol option Priority promotion with limited demotion. You can set this in the System tab of the RTX Properties Control Panel.
• If a non-deterministic call such as RtPrintf is made to Windows, and the Windows side crashes while the thread is within the Windows domain, the thread freezes.
• The Debugger to Launch drop-down menu in Visual Studio is empty in RtssRelease and RtssDebug configurations of RTSS applications that were created with the RTX Application Template. (2363)
• The RTX boot line is not removed following uninstall of the Subsystem merge module. To remove the RTX boot line manually, use the following command before uninstalling the MSISample product (1361):

\bin\RTXActivationUtil.exe –rbcd

• The managed code version of RTXDemo outputs the binary to the incorrect location in Visual Studio 2015 and Visual Studio 2013:
• Visual Studio 2013: the output path is set to ..\..\..\..\..\..\bin\. The correct path is bin\
• Visual Studio 2015: the output paths are set to $(ProjectDir)\bin\ for Release and $(ProjectDir)\bin\debug for Debug. The correct path for both is bin\
• Attempts to stop debugging after Break All is used causes Visual Studio to crash. (2511)
• The IntelProE1000Managed sample doesn't run to completion. The application sclient.rtss never fully executes when launched. (2502)
• The real-time functions RtGetLicenseFeatureStatus and RtGetLicenseFeatureStatusEx, which obtain the status of the license for a product feature, will not map the RTX feature names from previous versions (rtx, sdk, tcp) to the new feature names in RTX 2016 (izrtx, izsdk, iztcp). As a result, applications that contain code to check for the previous feature names will need to be updated to include the new feature names. (2428)
• An erroneous activation message may appear after a standard-dongle-based license (.lic) file is imported via command line, and the dongle is connected to the machine:  ...license(s) imported. No Dongle Detected (2550)
• Devices supported by the Intel 82579 driver may drop received packets when configured for Jumbo packets. (2554)

Reported as of RTX 2012 with Update 5

• Processor configuration values are not preserved in the registry when upgrading versions of RTX 2012. As a result, you must configure your system before you can use the Subsystem and RTX tools. A reboot of the machine is not required. The RTX Control Panel will not open following an upgrade until the system is configured, reporting this error: The system must be licensed and configured before running the control panel.
• Multiple RTX boot configurations are created when an RTX 2012 update version is upgraded (for example, from RTX 2012 with Update 4 to RTX 2012 with Update 5). Only one of these boot configurations is removed during uninstall, leaving an extra boot entry behind. You can manually remove the extra boot entry using this command line syntax:

bcdedit /delete ID

(2607)

Reported as of RTX 2012 with Update 4

• To install RTX 2012 with Update 4 on a Windows 7 machine, Windows 7 Service Pack 1 must be installed. If Service Pack 1 is not installed, the RTX installation will fail with an error. (2123)

Reported as of RTX 2012 with Update 3

• The RTSS Object Viewer displays the wrong stack value when viewed in Compact style. (1974)
• RTX licensing does not support running the RTSS Subsystem on a Virtual Hard Drive (VHD). (1975)
• A Blue Screen may occur when the C Runtime API calls fopen or fopen_s are called with an invalid parameter while RTX is configured to use Windows memory. (1973)
• There is a known memory leak in one of the third-party libraries RTX uses in one of its internal services, RTXLVS. If you run your system for extended periods of time you will see the handles within the RTXLVS service slowly increase. If necessary, you can stop and restart this service to free the memory. (1986)
• RegCreateKeyEx will fail to create or open a registry key if the parameter hkey is not one of the following two standard pre-defined registry hive keys: HKEY_LOCAL_MACHINE or HKEY_USERS. (1420)
• The Real-time API call RtAttachInterrupt is not able to detect if a Network Interface Card (NIC) device has been converted to RTX control. If the card is not under RTX control, unexpected behavior may result. (2002)

Reported as of RTX 2012 with Update 2

• When RTX components are licensed to an IntervalZero-provided dongle, and that dongle is removed from the machine, the RTX Activation and Configuration utility reports that those components are expired even though the license is still valid. (1956)
• When the RT-TCP/IP Stack is initialized for the RtIGB driver, the following message is displayed: RtIGB: AdapterStop Port Reset only! This message can be ignored. (1941)

Reported as of RTX 2012 with Update 1

• The API function RtcplStopSubsystemComponent doesn't reliably stop the RTSS Subsystem. (RTX-1476)
• On certain machines, Visual Studio 2005 does not allow local or remote debugging with RTX 2012. To resolve this issue, install Visual Studio 2005 Service Pack 1. (RTX-1275)
• RTX Demo only launches RTSS processes on the first RTX processor in a multiprocessor configuration. (RTX-1729)
• Filter names in the RtxTcpIp.ini file cannot be longer than 19 characters. This limitation will be removed in a future release. (RTX-1784)
• Changing the Network Address property setting for the RTX Virtual Network Add-On does not change the MAC address. (RTX-1801)
• When installing RTX 2012 with Update 1 on virtual machines, TCP connections may become disconnected temporarily during installation of the RTX Virtual Network Add-On component. When this occurs, connectivity should resume within 15-30 seconds. (RTX-1814)
• The Shutdown sample packaged with the product does not build a functional binary. To work around this issue, import the source code for the sample into project files created with the new RTX Application Wizard (Visual Studio 2010 or 2012), and then build the binary. (RTX-1819)
• An exception occurs when more than two interfaces are configured to use the default MemoryInK value (256) in the RtxTcpIp.ini file. To work around this issue, increase the MemoryInK value. (RTX-1231)
• Jumbo Packets do not work with the Virtual RTX Ethernet Adapter on Windows XP or Windows XP Embedded. (RTX-1824)
• The RT-TCP/IP Stack will encounter an error and terminate if required parameters, such as StackMTU or MTU, are missing from the RtxTcpIp.ini file, or if the file contains a typo. For information on the optional and required parameters, see RTX-TCP/IP Stack and Driver Configuration. (RTX-1825)
• Shutdown handler functions that are registered using RtAttachShutdownHandler should not call RtPrintf excessively, or they risk preventing Windows from shutting down when the user initiates a normal Windows shutdown or restart. During a normal Windows shutdown or restart, the RTX Server Console window is not visible, so output produced by RtPrintf is not visible, which further reduces the value of using RtPrintf in a shutdown handler function. However, when Windows crashes, RtPrintf can safely be used to write text to the blue screen from a shutdown handler without risk of preventing Windows from rebooting. (RTX-1844)
• RtssRun fails to locate .rtss files if the folder path includes a period and the extension .rtss is not specified. (RTX-1852)

Reported as of RTX 2012

• When a user who is only a member of the RTXUsers group attempts to add a Load in RTX Demo, an error appears: "Cannot open RTXDemoLoadFile". (RTX-989)
• When the RTSS thread priority is within the range of the Microsoft thread priority, the Microsoft Visual Studio Threads Window displays the thread name. When the RTSS thread priority is out of range, the number is displayed. (RTX-707)
• RTX Demo (Native) intermittently stops responding when you stop the maximum latency test while running the timer as a Win32 process. (RTX-974)
• RTX currently does not allow you to attach to an RTSS process that was started at boot-time. You cannot use the RtssRun /y (dynamic process) and /b (register boot time process) flags together. (RTX-1001)
• Using the /t flag with RtssRun results in an error. (RTX-1043)
• RtssRun does not provide an error when you use the flags /d and /y together when registering a RTDLL. The /y flag is not needed for RTDLLs and is ignored as a result.
• Activation of RTX via fingerprint file fails on Virtual Box 4.1.10. (RTX-621)
• RTSS Task Manager crashes when a RTSS process is started on Dell Precision T5500 machines running Windows 7 with Service Pack 1. (RTX-198)
• You cannot attach to a Windows process in Visual Studio if RTX isn't licensed. To resolve this issue, either license RTX or disable the RTX Debugger Add-In from Visual Studio: Tools > Add-in Manager > de-select both RTX Debugger Extension and Startup. (RTX-1085)
• The Help button and F1 Help do not work in the RTX Platform Evaluator. You can access the RTX Product Documentation from Start > All Programs > IntervalZero > RTX 2016 > RTX Documentation. (RTX-899)
• You cannot load more than 79 unique, registered RTDLLs using LoadLibrary. (RTX-1608)
• The Target Designer for RTX 2012 Embedded only provides a single entry for the RtIGB driver, where there should be entries for both the .INF and .RTDLL. (RTX-1723)
• The DriverLib sample for Visual Studio 2012 fails to build. (RTX-1741)

Reported Previous to 2012

These known issues were reported previously but still apply to RTX 2012.

• The function RtGetBusDataByOffset does not work as expected on the Intel compiler when the linker stack reserve size (/STACK:reserve) is set to the default value of 0. If this value is changed (in Visual Studio, using Project Properties > Linker > System > Stack Reserver Size) to 512, the call works correctly. (1823)
• RT-TCP/IP crashes when a large volume of fragmented TCP packets are sent using the RTTCP.rtss utility. (2575)
• On machines running Windows XP Service Pack 3, the ATIFirePro2260 video adapter causes jitter and intermittent blue screens when RTX is running. (2715)
• When Windows XP is running on single physical processor system that includes Hyper-Threading (HT), enabling HT in the BIOS will provide two logical processors to Windows, causing it to use a Multiprocessor HAL. If RTX is installed on this system, do not disable HT without uninstalling RTX first. Disabling HT causes Windows to replace the Multiprocessor HAL with a Uniprocessor HAL. Starting RTX with the replaced HAL can cause the system to bug check. This restriction is not applicable to Windows Vista or Windows 7, as they provide a single HAL for all configurations.
• RTX utilities located under Program Files\IntervalZero\RTX\Bin will not run properly unless they are launched from within that directory. If you attempt to launch a utility from another location, you will encounter an error. (2247)
• RTX versions after 8.1 do not correctly support hardware that does not support extended registers and the use of FXSAVE/FXRSTOR. (7128)
• Sometimes, update driver functionality does not work correctly on Vista, so you may need to completely uninstall the offending driver before installing the RTX supported driver or the correct Windows driver. (5979)
1. Click the Start menu, then right-click Computer and choose Manage.
2. Click Device Manager.
3. Locate the driver, right-click it, and choose Uninstall.
4. Click OK to confirm the uninstall.
5. From the Action menu, choose Scan for hardware changes to locate and load the new driver.
• If RTX generates a starvation exception, some RTX tools will need to be restarted. The exceptions are RTX Properties control panel, Object Viewer, and RTSS Task Manager. These three tools should function correctly if a starvation exception occurs. (4442)
• DeviceIoControl FSCTL opcodes have not been tested or documented. (1931)
• In Silent Uninstallation Mode, StopRtss does not alert the user when it fails to stop the subsystem. (1824)

SDK

• RTSS applications generate a System Integrity Audit Failure when executed unless they are cross-signed with Sign Tool. (2604)
• Under stress test conditions, the RtTerminateProcess function can cause a Windows STOP message to occur. (7103)
• The RTX WinDbg extension displays incorrect data for the RTSS system process. (6237)
• NIC drivers built with versions of RTX prior to 7.1 may not work with the new TCP/IP IPv6 Stack. Custom NIC drivers must be updated if ioctl for IPv6 multicast neighborhood solicitation fails. ioctl is called before RtndUpDown, following RtndConfigure codes from RtndUpDown. The codes for the up portion may need to be run before ioctl ENIOADDMULTI.