1
0
mirror of https://github.com/pfusik/xasm.git synced 2024-06-08 18:29:29 +00:00
xasm/doc/xboot.htm
2013-01-07 12:07:29 +01:00

98 lines
3.7 KiB
HTML

<HTML>
<HEAD>
<TITLE>X-BOOT 5.0</TITLE>
</HEAD>
<BODY BACKGROUND="6502proc.gif">
<CENTER>
<H1>X-BOOT version 5.0</H1>
<HR>
</CENTER>
<H2>INTRODUCTION</H2>
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
<A HREF="xload.htm">X-LOAD</A>), and the emulators (e.g.
<A HREF="http://www.a800win.atari-area.prv.pl">Atari800Win PLus</A>).
However, X-BOOT may still be useful, especially when using
professional loader.
<H3>CHANGES</H3>
<H4>Version 5.0</H4>
<UL>
<LI> long file names support
<LI> more flexible syntax: both <TT>obxmask atrfile</TT>
and <TT>obxfile atrpath</TT> can be used
<LI> internal write protection flag (supported by APE and Atari800)
set in generated disk images
<LI> headers with end address less than start allowed
<LI> Unix-like <TT>-p</TT> option allowed
</UL>
<H4>Version 4.0</H4>
<UL>
<LI> wildcards support - now you can convert a set of files
<LI> .ATR name not required - name can be taken from executable
<LI> no length limit - files longer than 60k allowed
<LI> truncated executables are supported
<LI> checking for memory conflicts
<LI> better errors handling
</UL>
<H4>Version 3.2</H4>
<UL>
<LI> .OBX is default extension of Atari executable
</UL>
<H4>Version 3.1</H4>
<UL>
<LI> first release
</UL>
<HR>
<H2>USAGE</H2>
Syntax for invoking X-BOOT is following:<P>
<TT>XBOOT [/p] obxfiles [atrpath][atrfile]</TT><P>
Parameters in brackets are optional.<P>
If file name extension is omitted, the default .OBX or .ATR is added.
If no <TT>atrpath</TT> is given, disk images are written by default in
the directory where executables are.<P>
If file name contains spaces, you should enclose it in quotation marks.<P>
<TT>/p</TT> switch (or equivalent <TT>-p</TT>) 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.<P>
Both loaders disable Atari Basic, so you don't need to hold the OPTION key
while booting.<P>
Below are some examples:<P>
<DL>
<DT><TT>XBOOT -p test</TT>
<DD>Converts <TT>test.obx</TT> to <TT>test.atr</TT> in current directory
using professional loader.
<DT><TT>XBOOT d:\games\*.xex \atrs\</TT>
<DD>Converts all files in <TT>d:\games</TT> with <TT>.xex</TT> extension
and writes disk images to directory <TT>\atrs</TT> on current drive
using standard loader.
<DT><TT>XBOOT "c:\test\Very Long File Name.AtariExecutable" /p</TT>
<DD>Converts <NOBR><TT>c:\test\Very Long File Name.AtariExecutable</TT></NOBR> to
<NOBR><TT>c:\test\Very Long File Name.atr</TT></NOBR> using professional loader.
<DT><TT>XBOOT d:* /p .</TT>
<DD>Converts all .OBX files in current directory on <TT>d:</TT>
to current directory on current drive using professional loader.
</DL>
<HR>
<H2>DETAILS</H2>
Produced ATR is single density and as short as possible.
Loader occupies one boot sector.<P>
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.<P>
For more details, read source files of the loaders:
<UL>
<LI>Standard: <A HREF="xbootstd.asx">XBOOTSTD.ASX</A>
<LI>Professional: <A HREF="xbootpro.asx">XBOOTPRO.ASX</A>
</UL>
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.
<P><HR><P><A HREF="index.htm">Back</A>
</BODY>
</HTML>