On Time Logo
Home Prices Free Download Full Products Search Site Map Contact

On Time RTOS-32 Documentation

Welcome

Introduction

Hardware and Software Requirements

This Manual

Technical Support

Installation

License Keys

Licensing Terms and Liability

RTTarget-32

RTKernel-32

RTFiles-32

RTIP-32

RTPEG-32

RTUSB-32
PreviousPrevious NextNext

Installation

To install On Time RTOS-32 on your computer, simply execute the installation program(s) (one for each On Time RTOS-32 component) under Windows. If you are installing a full release of On Time RTOS-32, you will be prompted to enter an installation key and a License Key. Both values are case sensitive. The correct keys are given on your License Certificate. Installation keys are used to decrypt the data to install. License Keys identify a developer and a different license key should be used by each developer. You may install On Time RTOS-32 on two or more computers with the same license key only if you can guarantee that the software will never be used on more than one of them simultaneously.

The following directories are created under the On Time RTOS-32 installation directory:

Directory Contents
Doc HTML Help documentation and related tools.
Bin Executable programs and DLLs delivered with On Time RTOS-32.
Include On Time RTOS-32 include files.
Libbc Libraries and various object files for Borland C++.
Libdel Interface unit source files for Borland Delphi.
Libmsvc Libraries and various object files for Microsoft Visual C++.
Demobc Example programs for Borland C++.
Demodel Example programs for Borland Delphi.
Demomsvc Example programs for Microsoft Visual C++.
Demomsdev Example programs for Microsoft Visual Studio (IDE Projects).
Boot Source code of RTTarget-32's boot code.
Monitor1 Source code of RTTarget-32's Debug Monitor.
Driver\Rtk322 Source code of all RTKernel-32 drivers.
Driver\Rtf323 Source code of all RTFiles-32 drivers.
Driver\Peg4 Source code of all RTPEG-32 drivers.
Driver\Rtip5 Source code of all RTIP-32 drivers.
Driver\Rtu326 Source code of all RTUSB-32 class drivers.
Source\Rtt321 Source code of the RTTarget-32 run-time library Rtt32.lib.
Source\Emu Source code of the 387 FPU emulator.
Source\Metaw Source code of the MetaWINDOW support library Rtmetaw.lib.
Source\Rtk321 Source code of the RTKernel-32 scheduler.
Source\Rtk32sup2 Source code of the RTKernel-32 supplemental modules.
Source\Rtf321 Source code of the file system core of RTFiles-32.
Source\Peg1 Source code of the GUI library RTPEG-32.
Source\Rtip5 Header files and source code of the TCP/IP Stack RTIP-327.
Source\Rtu321 Source code of the USB Host Protocol Stack RTUSB-32.
Source\Smb1 Source code of the SMB Client and Server.
Source\Rtos32WinLib8 Source code of the RTOS32Win RTOS Library.
Source\Acpica1 Source code of Intel's ACPI Component Architecture library (required to build Library Acpica.lib and function RTMPACPITableCreate).

Here are the steps required to run one of the demo programs to test the installation of a full On Time RTOS-32 release. If you have installed the On Time RTOS-32 Evaluation Kit, please refer to the Readme.html file for information on running the demos.

  • Connect your host PC with the target PC using a NULL modem cable. If a port other than COM1 is used on the host, click "Edit Settings" and record the COM port used in file Rttarget.ini. If a different port is used on the target, edit the COMPort command in configuration file Demopc.cfg included with each demo.
  • Click on one of the demo program shortcuts created in the On Time RTOS-32 Start Menu folder. For a command line demo, this will open a command prompt window with all required environment variables defined and the current directory set to the directory of the selected demo. For Visual Studio demos, the respective workspace and project files for the demo are loaded.
  • Insert an empty formatted diskette in drive A:.
  • For command line demos, build the demo using the MAKE utility of your compiler (MAKE for Borland, NMAKE for Microsoft). In Visual Studio, select "Target - Win32 Debug" as the active configuration and build the project. Visual Studio will create the Debug Monitor Boot diskette in this step.
  • For command line demos, create a Debug Monitor boot diskette with command: 
    BootDisk Monitor A:
  • Use the resulting diskette to boot the target. For the Borland command line demos, start the RTTarget-32 debugger with: 
    RTD32 Hello
  • or simply download and execute the program with: 
    RTRun Hello
  • In Visual Studio, any command which starts the Visual Studio debugger (e.g., Build, Start Debug, Step Into) will download the program and run it under the debugger. If you are prompted for the name of the executable to run, enter Debug\<project name>.exe.
  • Note that GUI demo programs or demos not running on PC compatible targets may need a custom Debug Monitor.
1This directory is only created if you have purchased the respective component's source code
2This directory is only created if you have purchased RTKernel-32
3This directory is only created if you have purchased RTFiles-32
4This directory is only created if you have purchased RTPEG-32
5This directory is only created if you have purchased RTIP-32
6This directory is only created if you have purchased RTUSB-32
7The source files are only installed if you have purchased the RTIP-32 source code
8This directory is only created if you have purchased the RTVmf-32 source code

UpTechnical Support

DownLicense Keys

Copyright © 1996,2012 On Time