RTX MERGE MODULES INSTALL GUIDE

Transcription

1 RTX MERGE MODULES INSTALL GUIDE

2 Copyright by IntervalZero, Inc. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, graphic, electronic, or mechanical, including photocopying, and recording or by any information storage or retrieval system without the prior written permission of IntervalZero, Inc. unless such copying is expressly permitted by federal copyright law. While every effort has been made to ensure the accuracy and completeness of all information in this document, IntervalZero, Inc. assumes no liability to any party for any loss or damage caused by errors or omissions or by statements of any kind in this document, its updates, supplements, or special editions, whether such errors, omissions, or statements result from negligence, accident, or any other cause. IntervalZero, Inc. further assumes no liability arising out of the application or use of any product or system described herein; nor any liability for incidental or consequential damages arising from the use of this document. IntervalZero, Inc. disclaims all warranties regarding the information contained herein, whether expressed, implied or statutory, including implied warranties of merchantability or fitness for a particular purpose. IntervalZero, Inc. reserves the right to make changes to this document or to the products described herein without further notice. Microsoft, MS, and Win32 are registered trademarks and Windows 10, Windows 8, and Windows 7 are trademarks of Microsoft Corporation. All other companies and product names may be trademarks or registered trademarks of their respective holders. Installation Guide for RTX Merge Modules IZ-DOC-X R4 March Fifth Avenue Fourth Floor Waltham, MA Phone:

3 Contents Introduction 1 Editions 2 Requirements 3 Hardware Requirements 3 Development and Target Systems 3 Development Machine 3 Supported Network Adapters for the Target Machine 3 Target Machine Hardware Considerations 3 Software Requirements 4 Development Machine Software Requirements 4 Target Machine Software Requirements 4 Installing RTX64 Merge Modules 6 Additional Installation Options 6 Performing the Install 6 Files Added During Installation 7 Merge Module Deployment 8 Runtime Installation Requirements 8 Merge Module Dependencies 8 Target Activation and Configuration 9 Activating Product Components to a Machine 9 Activating Product Components to a Dongle 13 Setting the RTSS Boot Configuration 20 Configuring your System via Command Line Utility 21 Uninstalling RTX64 Merge Modules 22 Using the Sample 23 Advanced Installer Sample Project 23 Installation Errors and Warnings 25 Getting Support 29 i

4 Third-Party Support 29 Contacting Technical Support by Phone 29 Before Calling Technical Support 29 IntervalZero Website 30 ii

5 Introduction IntervalZero provides merge modules that contain components of the RTX64 Runtime. This allows developers to include selected components of the RTX64 Runtime into their product installation package. The RTX64 Runtime is broken down into the following merge module components. Subsystem.msm provides the RTX64 Real-time subsystem. All merge module components depend on this component, with the exception of haspds.msm. This is a required component. haspds.msm provides the DongleDriver used by IntervalZero-provided dongles. It installs haspds_ windows.dll and configures the system. RtTcpIp.msm provides deterministic processing and networking capability through a RT-TCP/IP protocol stack within the RTSS environment. This feature requires a separate license from the Subsystem. This is a required component if you plan to use networking within real-time applications. LatencyView.msm provides the RTX64 Latency View tool, which displays a visual comparison of latency between Windows and RTX64 cores. MonitoringUtil.msm provides the RTX64 Monitoring tool, which allows you to trace the behavior of your real-time applications by recording significant events that occur during execution of those applications. VirtualNic.msm provides the RTX64 Virtual Network, which provides a virtual point-to-point connection between Windows and RTX64 that emulates a local area network connection between Windows and the Real-time Subsystem with no additional hardware required. This module requires RtTcpIp.msm. TaskManager.msm provides the RTX64 Task Manager, which allows you to view, start, or end any active RTSS process or Windows process linked to RTX64 on your system. This guide provides information on the RTX64 merge modules, including system requirements and installation instructions. IZ-DOC-X R4 1 Introduction

6 Editions IntervalZero provides six different Runtime editions of the RTX64 product, listed in the table below. The edition... Solo Entry Basic Professional Premium Ultimate Includes support for real-time operations on... One dedicated RTSS processor in a multicore/multiprocessor environment. Up to two dedicated RTSS processors in a multicore/multiprocessor environment. Up to three dedicated RTSS processors in a multicore/multiprocessor environment. Up to seven dedicated RTSS processors in a multicore/multiprocessor environment. Up to 15 dedicated RTSS processors in a multicore/multiprocessor environment. Up to 63 dedicated RTSS processors in a multicore/multiprocessor environment. IZ-DOC-X R4 2 Introduction

7 1 Requirements This chapter lists the hardware and software requirements for using the RTX64 Merge Modules. Hardware Requirements Development and Target Systems Using the Merge Modules software involves multiple machines: A development machine on which you install the merge modules and then use an MSI deployment tool to create a setup installation kit, and The target machines where the installation containing the RTX64 Runtime will be installed. Development Machine The development machine on which you install Merge Modules should have an MSI deployment tool that supports merge modules and can be used to create an installation kit. Supported Network Adapters for the Target Machine The RTX64 TCP/IP merge module provides support for a number of network adapters. For the most up-todate list, see the RTX64 Network Driver Support PDF available at the IntervalZero website: Target Machine Hardware Considerations Some hardware configurations are not supported by RTX64 installations. When RTX64 can detect these unsupported configurations, the default behavior is to display a popup error message. IZ-DOC-X R4 3 Requirements

8 Although RTX64 runs on most x64 platforms, unique attributes of some processors require special consideration before selecting them as a target system. For a comprehensive list of approved and supported hardware, see the Microsoft Windows Logo Program web page: You will experience latency when running programs such as SRTM on Skylake and Kaby Lake systems with Integrated graphics, which shares resources with CPU and system memory. This creates a burden on CPU and system memory, causing high latency in APIC Timer interrupt delivery. Such latency is not encountered on Skylake or Kaby Lake systems with Discrete graphics. For more information, see the TechNote Understanding the Effects of Discrete and Integrated Graphics on RTX64/RTX Performance. NOTE: Support for Intel 6 generation Skylake and Kaby Lake systems was added in Update 2 for RTX with Service Pack 2. Previous versions of RTX64 will not work on Skylake systems. Software Requirements Development Machine Software Requirements The RTX Merge Modules require the Windows Installer MSI Version 4.5 (Windows 7) or Version 5.0 (Windows 10 and Windows 8.1). Target Machine Software Requirements Target Machine Operating System The RTX Runtime is supported on the 64-bit configurations of these operating systems: Windows 10 (up to Fall Creators Update Version 1709) NOTE: For deployment systems running Windows 10, we recommend the Windows 10 LTSB (Long Term Service Branch) version. Windows 10 IoT Enterprise LTSB (Long Term Service Branch) Windows 8.1 with Update Windows Embedded Standard 8.1 (must support MSI installation to allow RTX64 to be installed) Windows 7 (x64) with SP1 IZ-DOC-X R4 4 Requirements

9 Windows Embedded Standard 7 (x64) with SP1 (must support MSI installation to allow RTX64 to be installed) NOTE: Windows Home editions are not supported. IZ-DOC-X R4 5 Requirements

10 2 Installing RTX64 Merge Modules This section describes the installation of RTX64 Merge Modules. Additional Installation Options In addition to using the merge modules described in this document, the RTX64 Runtime is also available in the following installation types: RTX64 Runtime RTX64 is available as a Runtime installation. This support is provided in a separate installer. The RTX64 Runtime can also be installed silently. For more information, see the Silent Installation section of the RTX64 Runtime Install Guide. Performing the Install To install RTX64 Merge Modules: 1. Download the zip file RTX64_3.4_MM_Setup.zip from the IntervalZero website: 2. Extract the contents of the zip file. 3. Double-click the self-extracting executable RTX64_3.4_MM_Setup.exe. 4. Click Next in the IntervalZero RTX64 Merge Modules installation Welcome window. 5. Read the End User License Agreement, select I accept the terms in the license agreement and then click Next. IZ-DOC-X R4 6 Installing RTX64 Merge Modules

11 6. In the Destination Folder screen, select the default folder C:\Program Files (x86)\intervalzero\rtx64 Merge Modules\3.4\, and then click Next. 7. In the Ready to Install the Program screen click Install. 8. Click Finish in the installation Completed screen. Files Added During Installation The RTX64 Merge Modules installation adds files to the following directory: c:\program Files (x86)\intervalzero\rtx64 Merge Modules\3.4 (by default) Merge Modules can be found in the subdirectory \Repository The merge modules that are installed include: \Repository\haspds.msm \Repository\RtTcpip.msm \Repository\Subsystem.msm \Repository\LatencyView.msm \Repository\MonitoringUtil.msm \Repository\VirtualNic.msm \Repository\TaskManager.msm A sample Advanced Installer project file, RTX64Sample.aip, can be found at: %ProgramFiles(x86)%\IntervalZero\RTX64 Merge Modules\3.4\ IZ-DOC-X R4 7 Installing RTX64 Merge Modules

12 Merge Module Deployment Once the merge modules have been installed onto the development system, they can be included in a setup file that will be installed on a target system. Runtime Installation Requirements In addition to the target machine operating system requirements listed at the start of this document, take note of the following information when RTX64 merge modules are added to an installation. Administrator privileges are required Installations using RTX64 merge modules must be done from an account that has administrator privileges. You must reboot after RTX64 has been installed, licensed and configured. Merge Module Dependencies If any of the RTX64 merge modules are added to an installation, they must include the RTX64 Subsystem, which is contained in the merge module file Subsystem.msm. IZ-DOC-X R4 8 Installing RTX64 Merge Modules

13 Target Activation and Configuration Once RTX64 Runtime is installed on your target system, you must activate the RTX64 product and configure system processors. This can be done through the RTX64 Activation and Configuration Utility, or through a Command Line utility. NOTE: Licenses for RTX and previous versions will not work with RTX You must purchase a new license to activate RTX Note that licenses for RTX will work for RTX You can activate and lock your RTX64 product components to a specific machine or IntervalZero-provided dongle. This warning symbol appears in the Activation and Configuration utility whenever an issue is encountered. When the warning symbol appears, hover the mouse over it for more information. Activating Product Components to a Machine Follow the appropriate steps below to license RTX64 components to a specific machine. NOTE: The steps required to activate the components will depend on whether or not the machine is connected to the Internet. To activate RTX64 product components to a machine: 1. Launch the RTX64 Activation and Configuration utility from Start > All Programs > RTX > Activation and Configuration. The product components activated by your current key are indicated by a check mark. 2. Choose the appropriate activation option: Activate over the network Activate with a fingerprint file Activate immediately using a valid activation key. This option requires a network connection with access to the IntervalZero License Server. Create a fingerprint file with a valid activation key which you can then convert to a license file and import using the Activate with a license file option. IZ-DOC-X R4 9 Installing RTX64 Merge Modules

14 Activate with a license file Activate by importing a valid license file. Activate Over the Network Use this option to activate immediately using a valid activation key. NOTE: This option requires a network connection with access to the IntervalZero License Server. To activate over the network: 1. Click Activate over the network. 2. Make sure your machine is connected to the Internet with access to the IntervalZero License Server. Icon: Status: Network connection established Unable to establish a network connection Next steps: Continue with activation Make sure all network cables are plugged in and click the Network icon to refresh. If a network connection cannot be established, you can do one of the following: Try to configure a Proxy Server. Follow the steps under Activate with a fingerprint file. 3. Enter a valid activation key. NOTE: You can find your activation key in the you received from IntervalZero Sales upon purchase of RTX64. IZ-DOC-X R4 10 Installing RTX64 Merge Modules

15 4. Click Activate. The product components activated by this key are added to the Components box on the right side of the Activation and Configuration dialog. 5. Create a RTSS boot configuration, if one has not already been created. See Setting the RTSS Boot Configuration for more information. IMPORTANT! You must set a RTSS boot configuration before you can use RTX64. Configuring a Proxy Server Follow the steps below to configure a proxy server. You may need to do this if a network connection cannot be established. To configure a proxy server: 1. Click Configure proxy server. 2. Provide the requested settings: Server Port User Name Password NOTE: This information can be provided by your IT department. 3. Click OK. Activate with a Fingerprint File Use this option to create a fingerprint file with a valid activation key which you can then import using the Activate with a license file option. IZ-DOC-X R4 11 Installing RTX64 Merge Modules

16 To activate with a fingerprint file: 1. Click Activate with a fingerprint file. 2. Enter a valid activation key and then click Save As. NOTE: You can find your activation key in the you received from IntervalZero Sales upon purchase of RTX In the Save As dialog, name the file fingerprint.rfp. By default, the file will be saved to the desktop. 4. Navigate to the desktop, and then copy and paste the file fingerprint.rfp to an external device. 5. Connect the device to a machine with Internet connectivity. 6. Launch a web browser, and navigate to 7. Browse for and open the file fingerprint.rfp. 8. Click Activate to generate a license (.lic) file. 9. Click Save if your browser prompts you to save the license file. Some browsers automatically save the downloaded license file without prompting. 10. Copy the file License.lic to the external device, and transfer it to the machine on which RTX64 is installed. 11. Activate with a license file (see below). NOTE: Once a fingerprint file is saved, this section collapses, and the Activate with a license file section expands automatically. Activate with a License File Use this option to activate by importing a valid license file, such as a license file created from a fingerprint file created by the above option. To activate with a license file: 1. Click Activate with a license file. IZ-DOC-X R4 12 Installing RTX64 Merge Modules

17 2. Click Import... and then browse for and open the file License.lic. 3. Create a RTSS boot configuration, if one has not already been created. See Setting the RTSS Boot Configuration for more information. IMPORTANT! You must set a RTSS boot configuration before you can use RTX64. Activating Product Components to a Dongle This topic walks you through the steps required to activate RTX64 product components to an IntervalZeroprovided dongle. NOTE: The steps required to activate the components will depend on whether or not the machine is connected to the Internet. Understanding the Different Dongle Types Dongles are available in two sizes, Small Form Factor and Standard. Small Form Factor Supported RTX64 Versions RTX with Service Pack 2 and above Holds a copy of the license file? Yes Standard All No Activation Options for Small Form Factor Dongles You have three options when purchasing a small form factor dongle and a product license at the same time: Option 1 (default) IntervalZero activates the dongle for you when you purchase the software and a small form factor dongle. Simply plug in the dongle to use RTX64. Option 2 Request that IntervalZero not activate the dongle for you when you purchase the software and a small form factor dongle. You will then need to activate the product to the dongle yourself, following the steps below. IZ-DOC-X R4 13 Installing RTX64 Merge Modules

18 Option 3 Use an existing small form factor dongle. You will need to activate the product the dongle yourself, following the steps below. NOTE: You can also license RTX64 components to an IntervalZero-provided dongle using the Dongle Activation Utility. The IntervalZero-provided Dongle Activation Utility can be used to activate licensed components on other machines similar to the pre-activation service you can request from IntervalZero. You can download the Dongle Activation Utility from the IntervalZero website at IMPORTANT! You cannot license RTX64 components to a dongle when more than one dongle is connected to the machine. Follow the appropriate steps below to license RTX64 components to an IntervalZero-provided dongle. If you have a dongle that has already been activated, jump to step Using a Pre-Activated Dongle. To activate RTX64 product components to a dongle: 1. Launch the RTX64 Activation and Configuration utility from Start > All Programs > RTX > Activation and Configuration. 2. Check the status of the dongle icon in the Activation and Configuration dialog: Icon: Status: Dongle connected and active Dongle not connected / not active Multiple dongles detected Next steps: Choose the appropriate activation option to lock the RTX64 component(s) to the dongle. Make sure it is securely connected to your machine. If the dongle still isn t recognized, the RTX64 component(s) will be locked to the machine. Choose the appropriate activation option only if you want to license to the machine. You cannot license RTX64 components to a dongle when more than one dongle is connected to the machine. Remove all additional dongles until there is only one connected to the machine. IMPORTANT! Once components are locked to a dongle, that dongle must be connected in order to use RTX64 components on that machine. 3. Choose the appropriate activation option: IZ-DOC-X R4 14 Installing RTX64 Merge Modules

19 Activate over the network Activate with a fingerprint file Activate with a license file Activate immediately using a valid activation key. This option requires a network connection with access to the IntervalZero License Server. Create a fingerprint file with a valid activation key which you can then convert to a license file and import using the Activate with a license file option. Activate by importing a valid license file. Activate Over the Network Use this option to activate immediately using a valid activation key. NOTE: This option requires a network connection with access to the IntervalZero License Server. To activate over the network: 1. Click Activate over the network. 2. Make sure your machine is connected to the Internet with access to the IntervalZero License Server. Icon: Status: Network connection established Unable to establish a network connection IZ-DOC-X R4 15 Installing RTX64 Merge Modules

20 Next action: Continue with activation Make sure all network cables are plugged in and click the Network icon to refresh. If a network connection cannot be established, you can do one of the following: Try to configure a Proxy Server. Follow the steps under Activate with a fingerprint file. 3. Enter a valid activation key. NOTE: You can find your activation key in the you received from IntervalZero Sales upon purchase of RTX Click Activate. The product components activated by this key are added to the Components box on the right side of the Activation and Configuration dialog. 5. Create a RTSS boot configuration, if one has not already been created. See Setting the RTSS Boot Configuration for more information. IMPORTANT! You must set a RTSS boot configuration before you can use RTX64. IMPORTANT! Once components are locked to a dongle, that dongle must be connected in order to use RTX64 components on that machine. Configuring a Proxy Server Follow the steps below to configure a proxy server. You may need to do this if a network connection cannot be established. To configure a proxy server: 1. Click Configure proxy server. IZ-DOC-X R4 16 Installing RTX64 Merge Modules

21 2. Provide the requested settings: Server Port User Name Password NOTE: This information can be provided by your IT department. 3. Click OK. Activate with a Fingerprint File Use this option to create a fingerprint file with a valid activation key which you can then import using the Activate with a license file option. To activate with a fingerprint file: 1. Click Activate with a fingerprint file. 2. Enter a valid activation key and then click Save As. NOTE: You can find your activation key in the you received from IntervalZero Sales upon purchase of RTX In the Save As dialog, name the file fingerprint.rfp. By default, the file will be saved to the desktop. 4. Navigate to the desktop, and then copy and paste the file fingerprint.rfp to an external device. 5. Connect the device to a machine with Internet connectivity. 6. Launch a web browser, and navigate to 7. Browse for and open the file fingerprint.rfp. 8. Click Activate to generate a license (.lic) file. IZ-DOC-X R4 17 Installing RTX64 Merge Modules

22 9. Click Save if your browser prompts you to save the license file. Some browsers automatically save the downloaded license file without prompting. 10. Copy the file License.lic to the external device, and transfer it to the machine on which RTX64 is installed. 11. Activate with a license file (see below). NOTE: Once a fingerprint file is saved, this section collapses, and the Activate with a license file section expands automatically. NOTE: See RTX64 Activation Usage for a full list of supported command line parameters. Activate with a License File Use this option to activate by importing a valid license file, such as a license file created from a fingerprint file created by the above option. To activate with a license file: 1. Click Activate with a license file. 2. Click Import... and then browse for and open the file License.lic. 3. Create a RTSS boot configuration, if one has not already been created. See Setting the RTSS Boot Configuration for more information. IMPORTANT! You must set a RTSS boot configuration before you can use RTX64. IMPORTANT! Once components are locked to a dongle, that dongle must be connected in order to use RTX64 components on that machine. Using a Pre-Activated Dongle If the dongle you have received has been pre-activated, follow the steps below: IZ-DOC-X R4 18 Installing RTX64 Merge Modules

23 To use a dongle that has already been activated: 1. Do one of the following, based on the type of dongle you have: Small Form Factor Plug in the dongle (the license file is already on the dongle) Standard Import the license file 2. Connect the dongle to a USB port on the machine. 3. Open the Activation and Configuration dialog. This dialog appears once RTX64 has been installed. You can also launch it from Start > All Programs > RTX > Activation and Configuration. 4. Make sure the Activation and Configuration utility recognizes the dongle: Icon: Status: Dongle connected and active Dongle not connected / not active Multiple dongles detected Next steps: Choose the appropriate activation option to lock the RTX64 component(s) to the dongle. Make sure it is securely connected to your machine. If the dongle still isn t recognized, the RTX64 component(s) will be locked to the machine. Choose the appropriate activation option only if you want to license to the machine. You cannot license RTX64 components to a dongle when more than one dongle is connected to the machine. Remove all additional dongles until there is only one connected to the machine. Proceed once you see the Dongle Active icon. Steps 5-6 are for Standard dongles only: 5. Click Activate with a license file. 6. Click Import... and then browse for and open the file License.lic. IZ-DOC-X R4 19 Installing RTX64 Merge Modules

24 NOTE: The license is locked to the dongle. The dongle must be connected to the machine in order to use RTX64 components. 7. Create a RTSS boot configuration, if one has not already been created. IMPORTANT! You must set a RTSS boot configuration before you can use RTX64. Setting the RTSS Boot Configuration You can assign available processors to Windows or RTX64 through the RTX64 Activation and Configuration utility. The RTX64 Activation utility automatically detects the total number of processors on your system. NOTE: If your system is hyper-threaded, it is recommended that you assign an even number of processors between Windows and RTX64. The Windows logical processor and RTSS logical processor must not share the same physical processor. NOTE: This warning icon indicates that the RTSS boot configuration needs to be reconfigured. To set the RTSS boot configuration through the Activation and Configuration dialog: 1. Launch the RTX64 Activation and Configuration utility from Start > All Programs > RTX > Activation and Configuration. 2. In the Activation and Configuration dialog, click Set the RTSS boot configuration. 3. Assign processors between Windows and RTX64. For example, on a machine with 8 processors, and a Professional Runtime license at minimum, you can assign up to 7 processors for RTX64. NOTE: We recommend you do not split Hyper-threaded cores between Windows and RTX64, as it can cause loss of determinism. 4. Click Apply to complete configuration. IZ-DOC-X R4 20 Installing RTX64 Merge Modules

25 NOTE: The Apply button remains grayed-out until a valid configuration is provided. 5. When you are prompted, click Yes to reboot your computer. 6. Restart the system. Choose the RTX64 boot configuration at system startup. NOTE: You must reboot the machine if you change the number of Windows processors. If you change the number of RTSS processors, you must restart the RTX64 Subsystem. NOTE: Even if you don't reboot immediately, all changes will be saved and will take affect after the next reboot. The RTX64 Subsystem will not work correctly until after the next reboot. NOTE: On Windows 8.1, configuration changes will only take effect following a restart, not a shutdown. Configuring your System via Command Line Utility NOTE: If your system is hyper-threaded, it is recommended that you assign an even number of processors between Windows and RTX64. The Windows logical processor and RTSS logical processor must not share the same physical processor. Setting the boot configuration: 1. Navigate to the RTX64\bin directory. 2. Run Rtx64ActivationUtil.exe as Administrator. You must activate your system before you can configure system processes. 3. Provide the number of Windows -w and RTSS -r processors. For example, to assign 3 processors to Windows and 5 processors to RTX64 on a dedicated system, you would type: Rtx64ActivationUtil.exe -w 3 -r 5 4. Restart the system. IZ-DOC-X R4 21 Installing RTX64 Merge Modules

26 Uninstalling RTX64 Merge Modules To uninstall the RTX64 Merge Modules: 1. Navigate to the Windows Control Panel. 2. Under Programs, click Uninstall a Program. 3. Select IntervalZero RTX Merge Modules and then click Uninstall. 4. Click Yes to confirm. IZ-DOC-X R4 22 Installing RTX64 Merge Modules

27 3 Using the Sample The RTX64 Merge Modules installation includes a sample Advanced Installer merge modules project, RTX64Sample.aip. This sample is installed in the %ProgramFiles(x86)%\IntervalZero\RTX64 Merge Modules\3.4\ directory. Advanced Installer Sample Project This sample project contains all of the RTX64 Runtime merge modules to build a setup.exe installation kit. Follow the instructions below to run the sample project. Prerequisites Install Advanced Installer: Before you can run this sample project, you must first install Advanced Installer version or later, available at Install the required Windows SDK tools: To create installation packages with Advanced Installer, the following tools must be installed on the build machine. These tools are distributed with the Windows SDK: SignTool.exe - digitally signs files using.pfx certificates MsiMsp.exe - creates Windows Installer patches MsiZap.exe - allows you to remove a broken installation package To use Merge Modules in your installation package, you must register the file mergemod.dll with regsvr32.exe. Visit for more information. IZ-DOC-X R4 23 Using the Sample

28 Building the Sample To build the sample: 1. Run Advanced Installer as Administrator and open the file RTX64Sample.aip located at %ProgramFiles(x86)%\IntervalZero\RTX64 Merge Modules\3.4\ 2. Scroll the left pane and click Merge Modules under Requirements, The RTX64 merge modules are displayed in the Merge Modules tab. 3. Click Build in the title bar. The Build Project dialog appears and the project builds. 4. Click OK. 5. Launch Windows Explorer and navigate to %ProgramFiles(x86)%\IntervalZero\RTX64 MergeModules\3.4\ A new folder has been added to this directory: RTX64Sample-SetupFiles. This folder contains the installation kit RTX64Sample.exe that was built from the merge modules project. IZ-DOC-X R4 24 Using the Sample

29 Appendix A: Installation Errors and Warnings Possible registry key values in case of an error or warning during the product install are shown in the following table. No. Description of the error or warning 1 Silent install; the CheckUninst function found a previous (pre-msi) version of RTX64. 2 Silent install; the CheckUninst function found a previous (pre-msi) version of RT-TCP/IP installed. 3 The CheckUninst function found a previous (pre-msi) version of RTX64 installed; user clicked "No" when asked to uninstall it. 4 The CheckUninst function found a previous (pre-msi) version of RTX64 SDK installed; user clicked "No" when asked to uninstall it. 5 The CheckUninst function found a previous (pre-msi) version of RTX64 installed; user clicked "No" when asked to uninstall it. 6 The GetOSCurrentVersion function called MsiGetProperty(VersionNT) and failed. 7 The GetOSCurrentVersion function called MsiGetProperty(VersionNT) and got NullString. 8 The GetOSCurrentVersion function called MsiGetProperty(VersionNT) and len(value)!= 3. 9 The detected operating system version is not supported. 14 Calling RtxCapabilities failed. 21 Unused / saved for a "default" case. 22 Unable to load SUPPORTDIR from MSI table. 23 Either no address, or an invalid address was supplied. 24 No value found in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion:ProductId. IZ-DOC-X R4 25 Installation Errors and Warnings

30 No. Description of the error or warning 25 No value found in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion:InstallDate. 32 An exception occurred while calling VciValidate. 34 Unable to load VersionNT from msi table during Reg_SetProps. 35 RtxCapabilities failed during Reg_SetProps. 38 The user's operating system is not supported without extended OS support. 41 An exception occurred while validating installation. 42 Unable to load SUPPORTDIR from MSI table during RtxCapabilities. 43 Windows installation of the subsystem on a Svr'03' SP2 on a Uniprocessor platform is not supported. 44 Unable to load SUPPORTDIR from MSI table in DoInstallSubsystemActions. 45 Unable to load AppDataFolder from MSI table in DoInstallSubsystemActions. 46 SetSecInfo failed (this is the routine which patches the subsystem files). 47 Call to VciGetHalType failed. 48 The script variable sosversion is not initialized during GetHalType. 50 Detected HAL: "MPS APIC platform", only 1 processor. 51 Detected HAL: "ACPI APIC platform MP", only 1 processor. 52 Detected HAL doesn't match any known HALs. 53 Detected HAL name doesn't contain "x86" or "ACPI" on windows Vista or higher. 55 A call to ListCreateFailed. 56 RegDBQueryKey("HARDWARE\\RESOURCEMAP\\Hardware Abstraction Layer") Failed. 57 First call to ListCreate failed. 58 Second call to ListCreate failed. 59 Third call to ListCreate failed. 60 In ListGetValue. The list passed in is not valid. IZ-DOC-X R4 26 Installation Errors and Warnings

31 No. Description of the error or warning 61 In ListSetValue. The list passed in is not valid. 62 MsiGetProperty( "ProductCode" ) returned "". 63 MsiGetProperty( "VersionNT" ) returned "". 64 Calling RTX64Capabilities with the current ProductID resulted in an error. 65 The OS Support field of the product code contains an invalid value. 66 The VS Support field of the product code contains an invalid value. 67 The Edition field of the product code contains an invalid value. 68 The Edition field of the product code contains an invalid value. 69 The Edition field of the product code contains an invalid value. 70 Upgrading from an evaluation package is not allowed. 71 CustomActionData was truncated. 72 Calling SetSecInfo failed. 73 MsiGetProperty( "SUPPORTDIR" ) failed. 74 Error occured while calling ShellExecute(): File not found. 75 Error occured while calling ShellExecute(): Path not found. 76 Error occured while calling ShellExecute(): Access denied. 77 Error occured while calling ShellExecute(): Out of memory. 78 Error occured while calling ShellExecute(): Invalid EXE file or error in EXE image. 79 Error occured while calling ShellExecute(): A sharing violation occurred. 80 Error occured while calling ShellExecute(): Incomplete or invalid file association. 81 Error occured while calling ShellExecute(): DDE Time out. 82 Error occured while calling ShellExecute(): DDE transaction failed. 83 Error occured while calling ShellExecute(): DDE busy. 84 Error occured while calling ShellExecute(): No association for file extension. IZ-DOC-X R4 27 Installation Errors and Warnings

32 No. Description of the error or warning 85 Error occured while calling ShellExecute(): DLL not found. 86 MsiGetProperty( "SUPPORTDIR" ) failed. 87 A call to RtcplStopSubsystemComponent() failed. 88 CustomActionData was truncated possible long paths pushed the value past its limit. 89 Prop "SYSTEMP" not found. 90 Loading VciFindArc or one of its dependencies failed. 91 An exception occurred while trying to set security info. 92 An error occurred while trying to activate RTX Failed to copy Rtx_Rtss.sys file to drivers directory. 94 Failed to copy Rtx_HalExt.sys file to drivers directory. 96 An exception was thrown while calling RttlsSetNumberOfProcessSlots(). 97 RttlsSetNumberOfProcessSlots() returned FALSE. 98 Failed to load positive numeric value from [RTX64_CTRL_PROCESSSLOTS]. 100 The LaunchConditions action detected that the current operating system is not supported. 101 An earlier version of RTX64 was detected, and should be uninstalled before installing this version bit versions of Windows are not supported. 507 RttlsEnableComponent(COMPONENT_TCPIP) failed. 508 RtcplSetTCPIPUSBDependency() failed. 521 An Exception occurred while calling Stop_Rtss. IZ-DOC-X R4 28 Installation Errors and Warnings

33 Getting Support IntervalZero offers a number of support options for RTX64 users, including technical support and the IntervalZero Web site. Third-Party Support If you are a customer who purchased an IntervalZero product through a third-party reseller, contact the reseller for support. Contacting Technical Support by Phone For technical support related to installing and using RTX64, you can call technical support at At the prompt, press 3 for Support. Hours are Monday - Friday, 8:30 a.m. 5:30 p.m. US Eastern time (GMT-500), excluding holidays. Before Calling Technical Support Please have the following information ready before calling IntervalZero Technical Support: Your Support ID Customers who purchase direct support receive an address and password for use when accessing the IntervalZero support web site. The Version Number of Your RTX64 Software Before calling technical support, determine the version of RTX64 installed on your system. Also, make sure you have a valid maintenance license. To obtain the RTX64 version number: Windows Navigate to Start > RTX Runtime > Control Panel. 2. Record the RTX64 version that is shown in the RTX64 control panel. 3. Check that your system has a valid maintenance license. You can find this information in the RTX64 control panel on the Home screen. IZ-DOC-X R4 29 Getting Support

34 Windows Click the RTX64 metro tile. The RTX64 Control Panel appears. 2. Record the RTX64 version that is shown in the RTX64 control panel. Windows 7 1. Navigate to Start > Control Panel > System and Security category > RTX64 Control Panel. 2. Record the RTX64 version that is shown in the RTX64 control panel. IntervalZero Website The IntervalZero Customer Support Web page is located at: The IntervalZero support web pages provide electronic access to the latest product releases, documentation, and release notes. With a valid address and password, you can access the online problem report database to submit new issues or to obtain the status of previously reported issues. IZ-DOC-X R4 30 Getting Support

35 Index A activation 9 B boot configuration 20 D development machine hardware requirements 3 software requirements 4 E editions 2 errors 25 H hardware requirements 3 development machine 3 network adapters 3 I installing 6 additional options 6 errors 25 files added during installation 7 warnings 25 N network adapters 3 R requirements hardware 3 runtime installation 8 software 4 S samples 23 software requirements 4 development machine 4 target machine 4 support 29 T target machine hardware considerations 3 software requirements 4 U uninstalling 22 W warnings 25 L licensing 9 M merge modules dependencies 8 deployment 8 I