<descrip>
- <tag>LCADDR: $D400, LCSIZE: $C00</tag>
+ <tag>LC address: $D400, LC size: $C00</tag>
For plain vanilla ProDOS 8 which doesn't actually use the Language Card bank 2
memory from $D400 to $DFFF. This is the default setting.
- <tag>LCADDR: $D000, LCSIZE: $1000</tag>
+ <tag>LC address: $D000, LC size: $1000</tag>
For ProDOS 8 together with the function <tt/rebootafterexit()/. If a program
doesn't quit to the ProDOS 8 dispatcher but rather reboots the machine after
exit then a plain vanilla ProDOS 8 doesn't make use of the Language Card bank
2 at all.
- <tag>LCADDR: $D000, LCSIZE: $3000</tag>
+ <tag>LC address: $D000, LC size: $3000</tag>
For plain vanilla DOS 3.3 which doesn't make use of the Language Card at all.
</descrip><p>
Configuration for a system program running on ProDOS 8 and using the memory from
$2000 to $BEFF.
+Parameters:
+
<descrip>
<tag><tt/__STACKSIZE__:/ C runtime stack size</tag>
don't include the DOS 3.3 header. See <tt>samples/overlaydemo.c</tt> for more
information on overlays.
+Parameters:
+
<descrip>
<tag><tt/STARTADDRESS:/ Program start address</tag>
The easiest (and for really large programs in fact the only) way to have a cc65
program use the memory from $800 to $2000 is to link it as binary
(as opposed to system) program using the default linker configuration
-<ref id="apple-def-cfg" name="apple2.cfg"> with __HIMEM__ set to $BF00
-and load it with the targetutil LOADER.SYSTEM. The program then works like a system
+<ref id="apple-def-cfg" name="apple2.cfg"> with <tt/__HIMEM__/ set to $BF00
+and load it with the LOADER.SYSTEM utility. The program then works like a system
program (i.e. quits to the ProDOS dispatcher).
Using LOADER.SYSTEM is as simple as copying it to the ProDOS 8 directory of the
<tag/Interrupts/
There's no <tt/interruptor/ support. Any attempt to use it yields the message
'FAILED TO ALLOC INTERRUPT' on program startup. This implicitly means that
- <tt/a2.stdmou.mou/ and <tt/a2.ssc.ser/ are not functional as they depend on
+ joystick, mouse and RS232 device drivers are not functional as they depend on
interrupts.
</descrip><p>
The Apple ][ has no color text mode. Therefore the functions textcolor(),
bgcolor() and bordercolor() have no effect.
- <tag/Cursor/
- The Apple ][ has no hardware cursor. Therefore the function cursor() has
- no effect.
-
</descrip><p>
</descrip><p>
+<sect1>Specifying file types for fopen<p>
+
+<descrip>
+
+ <tag>Explanation of File Types</tag>
+
+ ProDOS associates a file type and an auxiliary type with each file.
+ These type specifications are separate from the file's name, unlike
+ Windows which uses the file name's suffix (a.k.a.
+ extension) to specify the file type. For example, <tt/.exe/,
+ <tt/.doc/, or <tt/.bat/.
+ The ProDOS low-level
+ Machine-Language Interface (MLI) functions for creating and opening
+ files require these types to be specified. And if they don't match
+ with the file being opened, the operation may fail.
+
+ In contrast, the ISO C function <tt/fopen()/ and the POSIX function
+ <tt/open()/ have no parameter to specify either a file type or an
+ auxiliary type. Therefore, some additional mechanism for specifying
+ the file types is needed.
+
+ <tag>Specifying the File Type and Auxiliary Type</tag>
+
+ There are two global variables provided that allow the file type
+ and auxiliary type to be specified before a call to <tt/fopen()/
+ or <tt/open()/. They are defined in <tt/apple2_filetype.h/:
+
+ <tscreen>
+ <verb>
+ extern unsigned char _filetype; /* Default: PRODOS_T_BIN */
+ extern unsigned int _auxtype; /* Default: 0 */
+ </verb>
+ </tscreen>
+
+ The header file <tt/apple2_filetype.h/ also defines many values
+ that can be used to set these variables. It is included in
+ <tt/apple2.h/, which is in turn included in <tt/apple2enh.h/.
+ So it isn't necessary to include it directly. Just
+ include one of <tt/apple2.h/ or <tt/apple2enh.h/.
+
+ <tag>Example</tag>
+
+ A text file cannot be created with just the
+ standard C functions because they default to the binary type
+ <tt/PRODOS_T_BIN/. The <tt/_filetype/ variable must be set to
+ <tt/PRODOS_T_TXT/ to create a text file.
+
+ For a text file,
+ <tt/_auxtype/ specifies the record length. A zero record
+ length text file is referred to as a sequential text file.
+ This is equivalent to text files on
+ other operating systems, except that the line terminator is a
+ carriage return instead of a line-feed (Linux/BSD/MacOS) or
+ carriage return, line-feed pair (Windows).
+
+ The "sequential" text file terminology is in contrast to a
+ "random-access" text file which would
+ have a fixed-length, non-zero record length, so that the
+ file position of any individual record can be calculated.
+
+ For this example, the
+ <tt/_auxtype/ does not need to be set because it defaults to
+ the desired value, which is zero. To be more explicit,
+ <tt/_auxtype/ can also be set to <tt/PRODOS_AUX_T_TXT_SEQ/
+ which is defined as zero.
+
+ <tscreen>
+ <verb>
+ #include <stdio.h>
+ #include <string.h>
+ #include <errno.h>
+ #include <apple2.h>
+
+ void main(void)
+ {
+ FILE *out;
+ char *name = "MY.FAVS";
+
+ /*-----------------------------*/
+
+ _filetype = PRODOS_T_TXT;
+ _auxtype = PRODOS_AUX_T_TXT_SEQ;
+
+ /*-----------------------------*/
+
+ if ((out = fopen(name, "w")) != NULL) {
+ fputs("Jorah Mormont\r", out);
+ fputs("Brienne of Tarth\r", out);
+ fputs("Daenerys Targaryen\r", out);
+ fputs("Sandor Clegane\r", out);
+ if (fclose(out) == EOF) {
+ fprintf(stderr, "fclose failed for %s: %s", name, strerror(errno));
+ }
+ }
+ else {
+ fprintf(stderr, "fopen failed for %s: %s", name, strerror(errno));
+ }
+ }
+ </verb>
+ </tscreen>
+
+</descrip><p>
+
<sect>License<p>
projects / cc65 / blobdiff