Release Notes for RTX64 2013

Key Features
Notes
Known Issues

Key Features

Activation and Configuration

RTX64 SDK system features and components are licensed through the RTX64 Activation and Configuration utility, which requires a valid activation key. If the Subsystem is not licensed, you cannot run RTSS applications. For more information, see the RTX64 SDK Install Guide.
RTSS applications and RTDLLs require a valid SDK license to be built. If a valid license does not exist, the RTSS applications cannot be run.

General

RTX64 SDK supports user groups. By default, all users are members of the RTX64Administrators, RTX64Users and RTX64Debuggers groups. These groups should be modified to only include necessary users. For more information, see the RTX64 SDK Install Guide.

Real-time Subsystem

Scalable from 1 to 63 real-time processors
SMP aware scheduler utilizes both priority driven and pre-emptive algorithms to ensure critical thread context switches; and yields to threads of high priority occur in the sub-microsecond range.
Configurable thread and interrupt affinity
Configurable timer period
Ability to attach to line-based and message-based (MSI/MSI-X) interrupts
Shutdown handling on Windows STOP or shutdown
Deterministic memory
Access to Windows file system and registry
Dynamic-link library support through RTDLLs, which can be loaded implicitly or explicitly

Real-time Inter-Process Communication between Windows User Processes and Real-time Processes

Native and managed interface for 32-bit or 64-bit Windows processes
Objects available: events, mutexes, and semaphores
Data sharing through shared memory

Tools and Utilities

RTX64Config utility – configure the Real-time Subsystem. Using this utility, you can start and stop the RTX64 Subsystem, set subsystem parameters, enable the RT-TCP/IP stack (if licensed), and convert device ownership.
RTX64 Server console – display print messages from RTSS processes.
SRTM – provide information on Timer latency.

RT-TCP/IP Stack

The RT-TCP/IP Stack is a separate purchasable feature of the RTX64 Subsystem, This stack is based off the Treck 6.0 stack and supports:
IPv4 and IPv6
TCP, UDP, ICMP
ARP
Raw Sockets
Ethernet layer filter
A number of Intel and Realtek Gigabit drivers. For more information, see the RTX64 Supported NIC document at IntervalZero.com.

Debugging

The RTX64 Debugger:
Allows you to launch a process for debugging in Microsoft Visual Studio 2010.
Supports the following breakpoints:
A function breakpoint causes the program to break when execution reaches a specified location within a specified function.
A file breakpoint causes the program to break when execution reaches a specified location within a specified file.
An address breakpoint causes the program to break when execution reaches a specified memory address.
A data breakpoint causes the program to break when the value of a variable changes. You can set a data breakpoint on a global variable or a local variable in the top-most scope of a function. (C++ only)

For more information on RTX64 Debugger functionality, see Debugging with Visual Studio in the product documentation.

SDK

Headers and libraries for application development
Microsoft Visual Studio 2010 Support
Wizard for application development
Microsoft Visual Studio C-Runtime support
Sample source to show basic concepts
A stamping tool (StampTool.exe) is provided to stamp binaries so they can be run. RTX64 Wizards have also been updated to include the stamping tool as a post build step. For more information, see the product documentation.

Notes

The RTX64 Subsystem will not start and RTSS/RTDLL applications will not run if the system clock on your machine is changed from the correct time by more than 25 hours in either direction (backwards or forwards). If this scenario is caused by setting the time backwards, you can resolve the issue by resetting the system clock to the correct time, rebooting the system, and waiting 30 minutes. If this scenario is caused by setting the time forwards, you will not be able to reset the system clock backwards without contacting IntervalZero Support for assistance.
Running RTSS applications do not stop when you switch Windows user accounts. No warning is provided in this instance.
Members of the RTX64Users group can run RTSS applications via RtssRun only when the subsystem is already running. These members will not be able to see the run status of the subsystem using the RTX64Config command line utility, due to the group's access restrictions.
You must configure RTX64 Subsystem after installation, and reboot the system once configuration is complete. Failure to do so will make RTX64 Runtime unstable. For configuration instructions, see the RTX64 Runtime Install Guide.
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.
DLL_PROCESS_DETACH does not support exception handling. If an exception does occur a green screen may result. (1425)
You should only specify one parameter at a time when using the RTX64Config command line utility.
To use the Intel Compiler, you must enable the C Runtime environment setting within the RTX64 Application Wizard in Visual Studio. To do this, select Multithreaded C Runtime support in the Application Settings pane. Then, verify that these linker options are included as dependencies in your project properties (Property Pages > Linker > Input > Additional Dependencies):
Libircmt.lib
Libcmt(d).lib
startupCRT.lib
If you attempt to run or link an RTX64 program without the RTX64 Runtime installed, the error message "the dynamic link library rtapi.dll could not be found" appears.

Known Issues

The function RtCreateProcess requires a whole path. Relative paths are not supported.
RT-TCP/IP interface names are case sensitive.
In this release, RTX64 does not restrict you from creating multiple interfaces with the same name. However, if you create duplicate interfaces, you will not be able to use them. To resolve this issue, delete the duplicates and create the new interface again.

If a user creates a network interface configuration and is then removed from the group RTX64Administrators, they still retain Write Access to the registry key. (810)
You must manually start the RTSS Subsystem before a debugging session. If you attempt to debug a RTSS application when the RTSS Subsystem is stopped, you will encounter an "Unable to start program" error. (1045)

Providing the wrong interface name when configuring a parameter results in the following error: "Object reference not set to an instance of an object". (1091)

There is no way to force the RTSS Subsystem to stop through the RTX4Config command line utility. You must kill all running processes before you can stop the Subsystem. (1259)