On Time RTOS-32 programs to be run under RTOS32Win must always contain an Init function which must call RTVmfInit to initialize the RTOS32Win run-time system. Optionally, function RTVmfExtendHeap may also be called from the Init function to add all available RAM to the program's heap.

The program may not use any hardware devices which have not been assigned to the RTOS virtual machine. For example, the program must not call functions such as RTCMOSSetSystemTime or RTCMOSExtendHeap. The same is true for the keyboard driver call KBInit. There is also no screen. Data written to standard output (i.e., printf, etc) is rerooted to the Virtual Debug Console by RTVmfInit. Such data is only visible if a terminal program for the Virtual Debug Console is run under Windows.

Under RTOS32Win, programs always run in APIC mode. Functions such as RTMPSetAPICMode or RTMPSetPICMode are not supported an must not be called. The same applies to all functions related to the "MP Floating Pointer Structure" (RTMPDumpInfo, RTMPTableCreate, etc). The IOAPIC and multi-CPU configuration information is supplied by the RTOS32Win run-time system instead.

Programs must not assume that hardware interrupts are routed to a particular interrupt vector range. Global variable RTIRQ0Vector contains the first vector used for hardware interrupts. Its value can be changed by RTVmfInit.

Left RTVmf-32

Compiling and Linking

Down Debugging