The RT Application Loader loads an RT application into the RT kernel’s memory area. The RT kernel then starts the application.

Command line

ldrta.exe [options] [rta-filename]

Available options

-a or -args "argument string"

Takes a string argument which the loader passes to the application being loaded.

-d or -debug

Loads the application and forces a breakpoint exception at the first instruction of the code.
Mostly used by debuggers but sometimes helpful for loading an application in order to attach a remote debugger to it.

-fbrw

Forces the loader dialog to open, even if you supply a filename.

-n or -noui

Runs the Application Loader without showing any dialogs or message boxes. Any errors which occur will be reported in the INtime event log.

-node or -r or -remote nodename

Specify the name of the node on which the application is to be loaded.

-noxm

Force the application to load in non-XM mode. By default the application will load in the mode defined by the PE header of the RTA file.
See XM processes for more information.

-odir numeric-value

Object Directory Size: Specifies the number of entries this INtime application’s object directory can hold. The default value is 3840 entries. The minimum is 3; maximum is 3840. The RT kernel allocates 16 bytes per entry.

-odseg

Open Data Segment: Enables the specified application to execute at any location in its memory space. Use this option for applications that need to load and execute additional code during their execution.
When an INtime application loads, the RT kernel allocates memory for the application’s code, data, and stack sections. By default, the RT kernel sets up the application's memory space so that only the memory allocated to the code section is marked 'executable'. This prevents some application error types, since executing outside the allocated executable area (for example, a data area) causes a protection fault. When you select this option, memory is no longer protected in this manner.

-pmax numeric-value

Override the Pool-Max value defined by the RTA file PE header. The value is defined in bytes, but you can specify a trailing K or M to indicate Kbytes or Mbytes.
See memory management for further details.

-pmin numeric-value

Override the Pool-Min value defined by the RTA header. The value is defined in bytes, but you can specify a trailing K or M to indicate Kbytes or Mbytes.
See memory management for further details.

-prog

Display a progress indicator while loading the file. May be useful in loading large files over a slow network connection.

-strictrsl

Chek the full path of the RSL before sharing.

-tout numeric-value

Specify the timeout for NTX operations in 10msec ticks.

-vseg numeric-value

Specify the size of the application VSEG. The value is defined in bytes, but you can specify a trailing K or M to indicate Kbytes or Mbytes. The minimum size is 8 Mbytes, and must be a multiple of 4 Mbytes.
See virtual memory for further details.

-w or
-wait seconds

Causes the loader to wait for the given time (30 seconds for the -w option) or until the application calls SynchronizeRtLoader.
Allows the application to complete initialization before the loader starts to load the next application.

-xm

Force the application to load in XM mode. By default the application will load in the mode defined by the PE header of the RTA file.
See XM processes for more information.

Example

ldrta.exe foo.rta -a "arg1 arg2 arg3" -pmax 0xffffff -vseg 0x20000000

Operation

If the utility is invoked with no command-line arguments then it opens a dialog box with fields for locating and loading an RTA, with options. See the utility help file for details of the GUI operation.

If the utility is invoked with a filename on the command line an attempt is made to load the application without opening a window. If any error occurs the dialog box may open, or a message box is displayed to describe the failure. If the -noui option is also specified then no window will be opened and error messages will be written to the event log.

Use piperta instead of ldrta to capture any output.

For further details of loading real-time applications, see the Loading INtime Applications topic.