X-BOOT version 5.0


INTRODUCTION

This tool converts Atari executable files to disk images (ATR). Since its first version, X-BOOT lost significance, because now you can load an executable directly to Atari (e.g. using X-LOAD), and the emulators (e.g. Atari800Win PLus). However, X-BOOT may still be useful, especially when using professional loader.

CHANGES

Version 5.0

Version 4.0

Version 3.2

Version 3.1


USAGE

Syntax for invoking X-BOOT is following:

XBOOT [/p] obxfiles [atrpath][atrfile]

Parameters in brackets are optional.

If file name extension is omitted, the default .OBX or .ATR is added. If no atrpath is given, disk images are written by default in the directory where executables are.

If file name contains spaces, you should enclose it in quotation marks.

/p switch (or equivalent -p) forces writing 'professional loader', which allows you to load code/data intro the RAM under ROM and starts the program with disabled ROM and interrupts. By default, standard loader is used, which can load any Atari executable not demanding DOS nor any special loader.

Both loaders disable Atari Basic, so you don't need to hold the OPTION key while booting.

Below are some examples:

XBOOT -p test
Converts test.obx to test.atr in current directory using professional loader.
XBOOT d:\games\*.xex \atrs\
Converts all files in d:\games with .xex extension and writes disk images to directory \atrs on current drive using standard loader.
XBOOT "c:\test\Very Long File Name.AtariExecutable" /p
Converts c:\test\Very Long File Name.AtariExecutable to c:\test\Very Long File Name.atr using professional loader.
XBOOT d:* /p .
Converts all .OBX files in current directory on d: to current directory on current drive using professional loader.

DETAILS

Produced ATR is single density and as short as possible. Loader occupies one boot sector.

X-BOOT does not store the executable file in ATR as an Atari file. You can't read it from an Atari DOS nor extract it somehow or other. You can only run it by booting.

For more details, read source files of the loaders:

Loaders are so simple that they even do not detect end of file. Instead, they are modified when end of file is reached. The disk image contains one additional block, which doesn't belong to the executable file, but alters the loader to run the program instead of initializing.


Back