Currently there are no graphics drivers available for the Atari platform. However, the runtime library provides a function named _graphics, with a mode parameter just like the BASIC GRAPHICS command. This function will switch to the requested graphics mode. There are currently no functions available to access the graphics memory. The access must be implemented manually.
Many graphics modes require more memory than the text screen which is in effect when the program starts up. Therefore the programmer has to tell the program beforehand the memory requirements of the graphics modes the program intends to use. This can be done by using the __RESERVED_MEMORY__ linker config variable. The number specified there describes the number of bytes to subtract from the top of available memory as seen from the runtime library. This memory is then used by the screen buffer.
The numbers for the different graphics modes presented below should only be seen as a rule of thumb. Since the screen buffer memory needs to start at specific boundaries, the numbers depend on the current top of available memory. The following numbers were determined by a BASIC program.
|graphics mode||reserved memory|
The values of "1" are needed because the graphics command crashes if it doesn't have at least one byte available. This seems to be a bug of the Atari ROM code.
Currently there are no extended memory drivers available for the Atari platform.
Supports up to four standard joysticks connected to the joystick ports of the Atari.
Supports up to eight standard joysticks connected to a MultiJoy adapter.
Currently no drivers available (in fact, the API for loadable mouse drivers does not exist). There is a static driver you can use.
Currently there are no RS232 loadable drivers available for the Atari platform. There is a static driver you can use.