aboutsummaryrefslogtreecommitdiff
path: root/xexcat.1
diff options
context:
space:
mode:
authorB. Watson <urchlay@slackware.uk>2024-04-28 16:45:54 -0400
committerB. Watson <urchlay@slackware.uk>2024-04-28 16:45:54 -0400
commit1d622118a4da208d47d8c52c4c22cedb95ec4913 (patch)
treec86342c03d98aa87c433f6c3c94edee36bd990f9 /xexcat.1
parent547b463ed5571815cacb77e8fe7e778a157612e3 (diff)
downloadbw-atari8-tools-1d622118a4da208d47d8c52c4c22cedb95ec4913.tar.gz
Makefile: fix fenders target (derp).
Diffstat (limited to 'xexcat.1')
-rw-r--r--xexcat.18
1 files changed, 7 insertions, 1 deletions
diff --git a/xexcat.1 b/xexcat.1
index 522bedf..21c8ea1 100644
--- a/xexcat.1
+++ b/xexcat.1
@@ -145,6 +145,11 @@ The terms "Atari executable", "binary load file", and "XEX file"
all refer to the same thing. Also, there is no difference between
Atari executables named with "XEX", "COM", "BIN", "EXE", etc. The
Atari and its DOS don\(aqt care about the names, only the contents.
+.sp
+The \fBdasm\fP \fB\-f1\fP file format is also the native binary format for
+the Commodore 8\-bit machines (PET, 64, etc), so you can use \fBxexcat\fP
+to load Commodore code & data into an Atari... though of course the
+code won\(aqt run correctly on the Atari.
.SH EXIT STATUS
.sp
Exit status is zero for success, non\-zero for failure.
@@ -196,7 +201,8 @@ Watson <\fI\%urchlay@slackware.uk\fP>; Urchlay on irc.libera.chat \fI##atari\fP\
\fBxexamine\fP(1),
\fBxexcat\fP(1),
\fBxexsplit\fP(1),
-\fBxfd2atr\fP(1).
+\fBxfd2atr\fP(1),
+\fBxex\fP(5).
.sp
Any good Atari 8\-bit book: \fIDe Re Atari\fP, \fIThe Atari BASIC Reference
Manual\fP, the \fIOS Users\(aq Guide\fP, \fIMapping the Atari\fP, etc.