Release Notes for RTX64 2013 with Service Pack 1 Update 1
Key Features
RT-TCP/IP Stack and Drivers
- Incorporated the updated RtIGB driver, which supports the Intel® i350 controller.
Issues Resolved
Installation
- The Runtime Installation was improved to retain real-time subsystem configuration settings during an upgrade. (2191)
- Ensured that a Windows boot configuration remains in the scenario where the RTX64 boot configuration is the only boot option and RTX64 is uninstalled. (2351)
Activation and Configuration
- Resolved an issue regarding the Activation and Configuration utility returning success when failing to write to the license file or importing a license. (2158, 2162)
- Resolved an issue regarding multiple licenses. Previously, when more than six different features were licensed on a system, all licenses showed up as expired. (2312)
- Resolved an issue regarding the Activation and Configuration utility allowing for the user to set an invalid Windows-RTSS processor configuration. (1567)
- Improved the Activation and Configuration utility to display the associated dongle serial number when hovering over components licensed to dongles. (2237)
- Improved license file logic to prohibit duplicate licenses. (2396)
Tools and Utilities
- Improved permission checking within the RTX64 Control Panel. A user is no longer required to have Administrator permissions to launch the Control Panel. (2276, 2330)
- Resolved an issue where the RT-TCP/IP stack was required to be installed to launch the RTX64 Control Panel. (2328)
- Resolved an issue where the RTX64 Control Panel did not display products licensed to dongles when the dongle was not connected to the system. (2091)
- Resolved an issue where the RTX64 Control Panel did not refresh information when a network interface filter was deleted. (2137)
- Resolved an issue where the RTX64 Control Panel did not correctly remove multiple network interfaces. (2299)
- Resolved issues where the RTX64 Control Panel did not provide correct information regarding the state of subsystem components and the need for a restart of the real-time RT-TCP/IP stack, real-time subsystem or the operating system. (2261, 2217, 2266, 2291)
- Resolved an issue where the RTX64 Control Panel did not automatically select the correct driver for the Intel i210, i350, and the Realtek controllers. (2178, 2391)
- Resolved an issue where the RTX64 Control Panel showed non-Network devices in the Add Interface drop down menu for the device name field. (2243)
- Resolved an issue where the RTX64 Control Panel did not respond to the Enter key while editing a field (2218)
- Resolved an issue where the RTX64 Control Panel and Rtx64Config command line utility did not properly handle configuration of the Auto Shrink field. (2324)
- Resolved an issue where Rtx64Analyzer did not gather timer response information. (2366)
- Resolved an issue where the Device Manger’s RTX64 properties page did not persist the information for a need to restart the real-time RT-TCP/IP stack, real-time subsystem or the operating system. (1803)
RT-TCP/IP Stack and Drivers
- Incorporated the updated RtIGB driver, which supports the Intel® i350 controller. Resolved an issue where one port of a dual port i350 controller would not work if both ports were simultaneously enabled. Also resolved an issue where jumbo frames would not work correctly. (1957, 2260, 2321)
- Improved the RtssArp command line utility to return a valid error message in the event of an invalid address. (2282)
- Resolved an issue where the RT-TCP/IP stack’s shutdown handler prevented Windows from stopping and dumping memory. (2145)
- Removed unsupported build configurations from the provided real-time network driver source. (2254)
SDK
- Fully implemented Windows side RTAPI calls for RtGetBusDataByOffset, RtSetBusDataByOffset and RtTranslateBusAddress. (2155, 2340)
- Resolved an issue regarding API call RegQueryValueEx returning ERROR_INSUFFICIENT_BUFFER instead of ERROR_MORE_DATA when the user-supplied buffer was too small. (2214, 2334)
- Resolved an issue where API call RegEnumValue did not properly handle buffer overruns and returned the wrong error code when filling a user supplied buffer. (2215, 2332)
- Resolved an issue where Windows side RTAPI calls set incorrect error codes, causing GetLastError to return invalid information. (2335, 2353)
- Resolved an issue where RtMapMemory did not work correctly when called from a Windows application linked to RTX64. (2347)
- Improved the Managed code framework to provide better range checking for network Interface properties. (2219)
- Resolved an issue where RtGetModuleBaseName did not properly support UNICODE. (2300)
- Resolved an issue where GetModuleHandle did not handle NULL as an input parameter for the module name. (2356)
- Resolved an issue where network functions failed when sin_family/sa_family were set to AF_INET. (2329)
- Resolved an issue where the RtEthernetFilter filter interface received all incoming packets twice when using the RtRtl8168 real-time network driver. (2336)
Notes
- If you are not a member of the RTX64Administrators or RTX64Users groups, you may encounter an error when creating a new interface. For more information on user groups, see User Groups and Access Permissions. (2417)
- The RTX64 2013 Runtime, SDK and RTX64Analyzer standalone installers cannot be installed on a 32-bit operating system, Attempts to do this will result in the following Windows error: "This installation package is not supported by this processor type. Contact your product vendor." (2412)
Known Issues
- The RT-TCP/IP stack can support large packets up to 2000 bytes. Jumbo packets are not currently supported. (2403)
- The
-t
option is not currently supported by RtssArp. This will be resolved in a future release. (2460)