The!Cart Studio

Welcome to "The!Cart Studio", the free cartridge image authoring tool for The!Cart, Atarimax Maxflash Cartridges, and free-style binary cartridge images. The program enables you to create workbooks for cartridge images that contain one or more ROMs or executables. The workbook can then be exported in different formats. Besides plain binary images for usage if an EPROM or external flash programming device, emulator cartridge images to run the cartridge in emulators and flash programming disk images which can be booted or loaded directly from the Atari to flash the target flash module. It would be best if you had a device and software that is capable of transferring the data from your PC to the Atari, like, for example, SIO2PC (available here and here ) with AspeQt or SIO2SD. For "The!Cart", you do not need a USB programmer device or other PC-related hardware for programming. "The!Cart Studio" can also create header-free binary export files for a workbook. You burn or flash them to any cartridge, for example, using a USB programmer.

Sequence for creating workbooks and transferring them to the cartridge

You can watch the YouTube video presentation to understand how it works and what it looks like. You should read this English manual carefully to learn the details and features. If you have questions regarding "The!Cart" or "The!Cart Studio", you can contact me directly or post in the "The!Cart" thread on AtariAge (English) or the ABBUC Forum (German).

Downloading the Program

This is version 2023-08-31 14:49:58 of the program. Click here to download the latest version of the program. The download is a single ".zip" archive file containing operating system-specific archives and a standalone ".jar" file. Extract the files from the system-specific archive for your operating system into a folder of your choice.

Download archive content

Starting the Program

"The!Cart Studio" is implemented in Java, making it compatible with all popular operating systems. To run the program, you must install Java Runtime Environment (JRE) or Java Development Kit (JDK/SDK) with version 1.8 or newer versions. "The!Cart Studio" requires enough RAM for the Java process to export images. The amount of available RAM is displayed in the "About" dialog. It should be twice the size of the cartridge you want to export. So, for a 128 MB "The!Cart" export, the program requires at least 256 MB. You can specify this when you start from the command line via "java -Xmx256M -jar TheCartStudio.jar". By default, "The!Cart Studio" checks if an update is available during the start. The check is performed in the background and does not impact the startup time. You can turn off this check in the options.

For your convenience, native wrapper applications are provided. They set the required Java memory parameters.

Windows

Double-click "TheCartStudio.exe" to start the program. Alternatively, the following parameters are supported when running from the command line.

Starting in Windows command prompt

Linux

After extracting the "TheCartStudio.sh" file from the download archive, the so-called "executable bit" should already be set. If not, you will see the following error when double-clicking the files.

After unpacking

Open the file properties and set the executable flag as shown below for the file.

Setting the executable bit

You can run the "TheCartStudio.sh" from the terminal or via the "Run as a Program" entry in the context menu of your file explorer. If you get an error message like "Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /usr/lib/jvm/java-17-openjdk-amd64/lib/libawt_xawt.so", you have the headless version of the JDK installed. You need the version that also supports UIs. Run "sudo apt install openjdk-17-jdk" to install a complete JDK.

macOS

The folder "TheCartStudio.app" in the download is a native package that contains a small Java stub, the "TheCartStudio.jar", and some additional configuration files. You can start the app directly from the Finder. It also sets Java's -Xms and -Xmx parameters as required to overcome the default of only 128MB heap space. Upon the first start, you must open the app directly from the Finder via the "Open" entry in the context menu. Then you must confirm the "TheCartStudio is from an unidentified developer. Are you sure you want to open it?" warning by pressing the "Open" button and authenticating the action with an administrator user.

Confirming the start of the app

General Usage

The "The!Cart" enables you to create workbooks for cartridge images that contain one or more ROMs or executables. The workbook can then be exported in different formats. Besides, plain binary images (".BIN", ".ROM") for usage if an EPROM or external flash programming device, emulator cartridge images (".CAR") to run the cartridge in emulators, and flash programming images (".ATR") which can be booted or loaded directly from the Atari to flash the target flash module. Depending on your disk emulation, you can export the workbook as a single large programming disk image for use with AspeQt or as multiple 16 MB sized programming disk images for use with SIO2SD, SIO2USB, or similar SIO device emulators. You can also export cartridge images in plain binary (".BIN") to burn or flash them to any cartridge using a programmer device.

Detailed sequence for creating workbooks and transferring them to the cartridge

In case you are creating workbooks for "The!Cart", you can make use of the native cartridge emulation feature and reuse the existing software for the "Atari Maxflash" cartridge and "MegaCart". This means you can, on the one hand, directly use existing compilations and add them as a single file. On the other hand, you can use Maxflash Studio and MegaCart Studio to create new compilations and images for these cartridges and then add them as a single file. Because the Extended Menu of "The!Cart" also recognizes the menu systems of these two cartridge systems, it can optionally offer you the entries within these menus directly.

Detailed sequence for creating workbooks and transferring them to the cartridge

Using different studios with their specific loaders can be particularly useful when adding ATR disk images. No 100% accurate emulation of standard disk handling is possible when loading from ROM cartridges. Any ATR emulation must use at least a small amount of the computer's RAM. If a particular program uses this RAM area while loading from the cartridge, the loader will be overwritten and crash. The details of the different methods used can be found in the section ATR Disk Images. The following table gives an overview of the features supported by the individual loaders. With this information, you can decide which loader might be the right one for you.

Loader Compatible with Programs using the RAM under the OS Supports Disk Swapping Supports Poke and Patches
Maxflash Studio Modified Atari OS in RAM No Yes No
MegaCart Studio Modified Atari OS in RAM No Yes No
The!Cart Studio Modified ATR Disk Image Yes No (planned) Yes

User Interface

The user interface of "The!Cart Studio" is localized and currently comes with English and German screen texts. You can change the display language via the "Tools/Options..." menu entry. The default value is "Automatic", meaning that the language is determined automatically based on the operating system's language settings.

Options

Only the most frequently used columns are displayed in the various tables by default. You drag & drop to change the order of the columns. Clicking on the column header with SHIFT or CONTROL held down extends the sort order by appending this column. This way, you can sort by genre and title, for example. Clicking a column header without pressing SHIFT or CONTROL resets the sort order to that single column. You can also use the context menu to hide visible columns, unhide invisible columns, reset visibility, and sort order to the default. All layout changes are saved automatically when the program is closed. This also applies to the size and position of the main window and to the different folders that were last used for loading/saving workbooks, adding entries, and exporting cartridge images.

Workbook entries table header context menu

All relevant commands have a key binding, so you can use your keyboard to control the program.

Creating Workbooks

In the "File" menu, you can find the usual "New", "Open", Save", "Save As", and "Close" actions. When "The!Cart Studio" is opened, and a new unnamed project is prepared. You can display the dialog to edit the workbook options via the "Edit/Workbook Options..." menu entry.
Workbook options

Adding Entries

You can add files for new entries via the "Edit/Add Entries..." menu entry. The file chooser has multi-selection enabled, which means you can select multiple files at once and add them in one go. Alternatively, you can use drag & drop to drop one or multiple files onto the window to add entries.

Selecting one or more files to add

"The!Cart Studio" contains a database of popular ROMs and will assign the correct title automatically based on size and the CRC32 checksum of the file. If no matching entry is found in the data, the title of the workbook entry is defaulted from the file name by removing the file extension.

When new files are added, they remain at their original location first. When you save the workbook, all newly added files will be copied into the workbook's data folder (".tcd")). This way, you have all the files and the workbook together in one location. Consequently, a file in the workbook is uniquely identified by its case-insensitive file name, irrespective of the folder it was originally copied from. Adding files with the same file name will result in a confirmation dialog where you can overwrite the existing file in the data folder with the new file, rename the file automatically during copying, or skip the new file, leaving the existing file in the data folder unchanged. The choice can be applied to the current file only or to the current and all following files.

Confirm overwriting an existing file

Entry Properties

The information for every entry is displayed in the table's columns on the "Entries" tab". Only the most important columns are visible by default. They are shown with bold names on the table. You can configure the visibility and order of the columns as described in the section General Usage. Columns listed as editable can be read only for specific entries depending on the workbook entry type or other conditions.

Column Editable Description
Line No The line number in the table.
Type No The type of the workbook entry. Possible values are:
  • File
    This workbook entry was added via the standard "Add Entries..." action by selecting a file that is now part of the workbook. The workbook entry and content of the file will be exported when the workbook is exported.
  • User Space
    This workbook entry was added via the "Add User Space Entry..." action by selecting a file that is now part of the workbook. User-space entries can only be added if user space is reserved in the workbook options. A user space entry is exported as a single menu entry only and points to a bank in the User Space that is not maintained from "The!Cart Studio".
Title Yes The title of the workbook entry in the extended menu. It must be specified and unique within the workbook because it is the basis for the search in the extended menu. The length of the title is limited to 40 characters and to characters that exist in the Atari computer's character set. The title is defaulted based on the built-in cartridge database when the workbook entry is added. If no entry can be found in the database, the title is defaulted based on the name of the newly added file.
Genre Yes The genre of the workbook entry. Genres like "Games", "Demos", or "Tools" can be defined in the workbook options. Every entry can optionally be assigned to a genre. There are three ways to do this. First, by typing in the name of the genre with the keyboard. Second by choosing the genre from the drop-down list of the field. Third, via the action "Set Genre..." in the "Edit" menu. Using the "Set Genre..." action, you can set or clear the genre for all selected entries at once. If an entry is not assigned to a genre, it will only be on the "All" tab of the extended menu. If a type is assigned to a genre, it will be on the "All" tab and the tab for the genre.
Favorite Yes If you set the favorite indicator for a workbook entry, the initial list of entries in the extended menu only shows the favorites for the active genre. This way, you can use the joystick or cursor keys to select from a restricted list of entries. When you start typing a search term, the favorite indicator becomes irrelevant, and all entries are searched for the search term.
File Path No The source file path for newly added and unsaved entries. Once the workbook is saved, the file will be copied from the source file path into the data folder of the workbook, and the file path will be cleared.
File Name No The file name of the workbook entry uniquely identifies the workbook entry within the workbook and the data folder.
File Size No The exact file size of the file is displayed in bytes.
File Header No The file header type of the file. Possible values are:
  • None
    The file does not have a specific file header that describes its content. The complete file content is considered relevant data for "The!Cart". You have to select the proper content type manually.
  • Cartridge
    The file is a ".CAR" file that contains an additional header that describes its content. Only the part of the file after the header is considered relevant for "The!Cart". The content type of the workbook entry is set automatically and cannot be changed manually.
Content Size No The size of the relevant content in the file. For files with header type "None", it equals the file size. For files with another header type, it is the file size minus the header size.
Content CRC32 No The CRC32 checksum of the content. This checksum is used as identification to find information in the cartridge database. You will sometimes also find this checksum when people try to identify which ROM or version of a ROM they have.
Content Type Yes The content type of the workbook entry. The content type controls how "The!Cart" and the extended menu interpret the binary content behind the workbook entry. To start an entry correctly, the correct content type must be set. If you add entries with a "Cartridge" file header, the content type is determined automatically and cannot be changed manually. If you add a plain binary file, "The!Cart Studio" will default the content type based on the file size. If more than one content type matches the file size, select the correct one from the field's drop-down list. The content types and associated file sizes are available in the "Content Types Overview" dialog. The dialog can be opened via the "Help/Content Types" menu.
Display Mode Yes The display mode for the workbook entry. Possible values are:
  • Single Entry
    The workbook entry is a single menu entry in the extended menu. The workbook entry title in the workbook is used as the workbook entry title in the extended menu.
  • Multiple Entries
    This value can only be selected if the file behind the workbook entry contains a menu supported by "The!Cart Studio". The inner menu entries are extracted from the file during the workbook export. Only the titles of the inner menu entry, but not the title of the workbook entry, will appear in the extended menu.
Parameters Yes The parameters are relevant for entries with the "ATR - Atari Disk Images" content type. They contain the information required to modify the disk image content so it can run from "The!Cart" instead of a disk drive. When you add an entry based on a disk image, "The!Cart Studio" automatically determines the default parameters. You can change them manually if the disk images do not work correctly with the defaults. To restore the defaults, add the disk image file again. For more information on the parameters, see File Format and Content Type.
Start Bank Fixed Yes By default, "The!Cart Studio" arranges the data for the entries of a workbook automatically. This is done based on a strategy that keeps the position of existing entries stable as long as there is enough free space. Together with the incremental flashing feature of the flashing software, this helps to keep the time required for updating "The!Cart" short. Suppose you are a developer creating software specifically for "The!Cart" or even creating other arbitrary binary exports with "The!Cart Studio". In that case, you may want to have control of the order and position of the workbook entry data in the export. The corresponding field in the "Start Bank Fixed" checkbox becomes editable by setting the "Start Bank" checkbox. "The!Cart Studio" will then use the specified start bank for the workbook entry and will not rearrange the workbook entry if space on the cartridge runs out.
Start Bank Yes The bank where the content for the workbook entry is placed. "The!Cart Studio" automatically determines and manages the start bank by default. By setting the "Start Bank Fixed" checkbox, you make this field editable and specify a fixed value manually.
Banks No The number of banks the workbook entry will occupy on the cartridge.
Bank Assigned No This checkbox indicates the required banks for the workbook entry could be assigned correctly. If there is insufficient continuous space for the banks of the workbook entry left on the cartridge, the "Banks Assigned" checkbox will not be set. Saving the workbook is possible, but exporting the workbook is disabled. You can use the menu "Edit/Reassign Banks" to trigger a reordering of all entries to minimize gaps and free more space.

File Format and Content Type

Several file formats are supported when adding entries. To properly handle the ROM-specific bank switching scheme, every entry must know its content type. For those file formats where the content type cannot be determined automatically, for example, because there are multiple possible options, you have to select it in the "Content Type" column. The value help in the "Content Type" column is automatically filtered based on the file length and content. So, it only offers the potentially matching content types. In addition, some file formats are even automatically converted before they are added to the workbook. Saving the workbook is possible anytime, even if there are entries with unknown content types. When the workbook is exported, the content type for all entries must be present. Here is a description of the supported file formats and their handling.

File Format Description
CAR Cartridge Image This is the recommended format for adding ROM files. It is also by emulators. It contains a header with the exact type of the ROM file and a checksum to verify its integrity. This enables emulators to run the file without prompting the user for the precise content type upon each start. Similarly, it allows "The!Cart Studio" to automatically determine the content type, so you don't have to choose something, and the content type is not editable in this case.
BIN Cartridge Image
ROM Cartridge Image
This is the regular dump format for ROM files. It does not contain information on the type of flash module dumped from and the required bank switching to run it. Based on the file size, the "Content Type" column is restricted to those values that represent ROM with the exact file size. For example, a file with precisely 1 MB of data could be "Atarimax 1MB", "Mega Cart 1MB", "XEGS 1MB" or "Switchable XEGS 1MB". If you also want to use your ROM files in an emulator, converting the plain ROM file into a ".CAR" file is advisable. All popular emulators have this function built in. This way, you don't have to choose the correct flash module type at every start.
ATR Programming Images Collections created with the Maxflash Studio are sometimes available as "ATR Programming Images" instead of "BIN" or "ROM" cartridge images. They are bootable disk images that contain the program to flash the "Atarimax Maxflash" cartridge directly from the Atari. They cannot be run or tested in an emulator. These programming images are recognized by "The!Cart Studio". When you add such a file as an entry, it is first converted into a ".CAR" cartridge image, which is saved in the folder of the programming image. If the ".CAR" file already exists in that folder, it will be overwritten. The new ".CAR" file is added to the workbook. This way, you can even run and test the content of the ".CAR" cartridge image in an emulator before flashing.
ATR Disk Images This is the standard Atari disk image format emulators use. Many disk-based programs in this format can also be started from flash cartridges. However, there are some natural limitations arising from the fact that loading the ATR images requires a simulation of the SIO routines that are placed in the ROM of the original Atari OS. For example, the code for the simulation must be placed in the RAM and may be overwritten when the loading from the ATR disk image starts. In addition, the banks of the flash cartridge have to be activated during the SIO operation to load the data of the ATR disk image.
Consequently, a program that uses a display list, graphics, or interrupts in the cartridge memory area will run into problems. Also, programs that try to write data to the disk will fail when run from an ATR simulation. Two approaches are used for the simulation: Modified ATR Disk Images and Modified Atari OS in RAM. Which method works best depends on the ATR disk image and its programs.

Modified ATR Images
This is the approach used by the "Extended Menu" of "The!Cart". When you add an ATR file directly to a workbook, the file is analyzed, and all potential code locations that call the Atari OS SIO routines are identified. For disks that contain a known DOS (DOS 2.0S, DOS 2.5, MyDOS) and its "DOS.SYS" file, only the sectors that belong to that file are patched by default. For disks that contain the Bootmanager by Mike Langer, only the sectors of the Bootmanager are patched. For all other disks, the complete disk is scanned for usages of the SIO, which may potentially result in false positives. In this case, you must manually remove the patch from the parameters. The result of this analysis is stored in the "Parameters" column in the form "base=$100, $123=SIOV, $456=DSKINV". This column is hidden by default and can be shown via the context menu. When the workbook is exported to the Atari, the calls at the found offsets are modified to point to the SIO simulation placed at the address specified with the "base=$...." parameter. The advantage of this approach is that it also works on Atari 400 and Atari 800 machines that do not have RAM under the OS and for software that uses RAM under the OS, such as "Turbo Basic XL 1.5" or "The Brundles". Specifying the corresponding parameters will work even for software that uses non-standard SIO routines instead of the Atari OS SIO routines like, for example, "MyPicoDOS". The disadvantage of this approach is that it will not work with programs where the code that calls the SIO vectors is packed or encrypted in the ATR disk image. The following parameters are supported. Numbers are given in hexadecimal notation and are just example values. In the Compatibility Patches, you can find a list of known parameter combinations for programs that don't work with the default parameters.

  • base=$100
    This specified the base address for the SIO simulation code, which is less than 256 bytes in size. The default base address is $400. If the ATR disk image crashes while loading, it might be the case that the program overwrites this memory area. For example, MyPicoDOS uses the memory location $400-$40f during loading. To solve this problem, you can change the base address to $410. Other good choices for base addresses are $100, $400, $480,$500, and $600. Just try which one works for the specific program.
  • $123=SIOV
    The two bytes starting at offset $123 are changed to the start address of the emulation code for the SIOV vector ($e459).
  • $123=<SIOV
    The byte at offset $123 is changed to the low byte of the start address of the emulation code for the SIOV vector ($e459).
  • $123=>SIOV
    The byte at offset $123 is changed to the high byte of the start address of the emulation code for the SIOV vector ($e459).
  • $123=DSKINV
    The two bytes starting at offset $123 are changed to the start address of the emulation code for the DSKINV vector ($e453).
  • $123=<DSKINV
    The byte at offset $123 is changed to the low byte of the start address of the emulation code for the DSKINV vector ($e453).
  • $123=>DSKINV
    The byte at offset $123 is changed to the high byte of the start address of the emulation code for the DSKINV vector ($e453).
  • $123=SELECTEDITEMNUMBER
    The two bytes at offset $123 are changed to the memory location, which contains the item number of the selected menu entry. This can be used to modify inner menus to skip the selection and start the chosen entry automatically. The item numbers are counted starting at zero. For example, if you select the menu entry representing the 3rd item on a disk-based ATR disk image, the values in the memory location will be "2".

If you messed up the parameters somehow, you can add the ATR disk image again to the workbook and choose to overwrite the existing file in the workbook. The analysis is performed again in this case, and a parameter default is generated.

The SIO simulation in this approach supports both the read ("R", $52) and the status ("S", $53) command for "D1:". The status command sets the three density bits of the "DVSTAT" status based on the density and size of the ATR disk image. Using other disk units than "D1:" results in the error code "130 - Nonexistent Device". Using commands other than "R" and "S" results in the error code "132 - Unknown command".

Modified Atari OS in RAM
This is the approach used by the "Atarimax Maxflash" Menu or the "MegaCart" Menu. The operating system is copied to the RAM under the OS ROM and is then modified to load the "disk sectors" from the flash cartridge instead of the actual disk. The advantage of this approach is that it works equally for all software that uses the standard Atari OS SIO vectors, even if the SIO-relevant code on the ATR disk image is packed and encrypted. The disadvantage is that the approach will not work on machines like the Atari 400 or Atari 800 that do not have RAM under the OS like the Atari and not with programs that use the RAM under the OS themselves. You can use the Maxflash Studio or MegaCart Studio to create 128 KB, 1 MB, or 2 MB collections with ATR disk images. Both studios come with proven emulation and provide several options to specify how the disk image shall be handled. You can then export the collection as a BIN or CAR cartridge image and add it to the workbook.
Adding an ATR disk image Setting disk image options

COM Executable
EXE Executable
XEX Executable
This is the Atari DOS composite file format of executable files that can be loaded from a DOS. They can be added to "The!Cart" in three ways. All of them have advantages and disadvantages.

Directly as a single file
Executable files (COM, EXE, XEX) can be added directly to the workbook. While adding files directly is very convenient, the worst-case waste of space is 8191 bytes per file. Therefore, the options below are recommended if you add many executable files.

Included with multiple files on an ATR disk image
The most compatible and space-efficient way to run these files is to copy them with the required DOS onto a disk. It is even the only valid way for executable files that load additional data like fonts from separate files. And while adding executable files directly in the workbook is possible, adding them onto an ATR disk image with the Bootmanager by Mike Langer first and then adding the ATR disk image has advantages. You can create ATR disk images representing compilations and work on actual disk drives. In addition, ATR disk images work with sectors of 128 or 256 bytes. So if multiple files are copied to one disk, at most 127 or 255 bytes of space are wasted per file. The Homesoft website contains many disk images already prepared with the Bootmanager by Mike Langer.

Included with multiple files on an "Atarimax Maxflash" or "MegaCart" cartridge
This is similar to including files on an ATR disk image. Instead of using DOS and a Bootmanager, you can use the Maxflash Studio or MegaCart Studio to create 128 KB, 1 MB, or 2 MB collections with COM/EXE/XEX executables. Both studios come with proven emulation and provide several options to specify how the executable shall be handled. You can then export the collection as a BIN or CAR cartridge image and add that to the workbook.
Adding an EXE executable Setting EXE executable options

Cartridge Database

Many popular ROMs' titles and content types are stored in the cartridge database. If your ROM is found in the database, the title and, if known, the content type are proposed. If no matching entry is found, the content type is set to "Unknown", and you have to select the appropriate content type manually before exporting the cartridge in and form.

The cartridge database is based on the list by Tomasz Krasuski (Kr0tki) maintained at AtariAge. It currently contains over 700 known titles and almost 700 known content types. The exact numbers are shown in the About dialog. You can support "The!Cart Studio" and improve the quality of the cartridge database by sending your workbook file without (!) the ROMs.

Display Mode

Via the column "Display Mode", you can select how the workbook entry is represented in the extended menu. Possible values are:

The following types and versions of inner menus are currently supported. For all of them, you can add the inner menu entries to the extended menu by choosing "Multiple Entries". When you add a workbook entry, the "Display Mode" will automatically be set to "Multiple Entries" by default. You can change the values if you don't want the inner menu entries to appear separately. By default, you will start the inner menu when you select one of its entries in the extended menu. Dedicated support has been implemented for some inner menus, so choosing the inner menu entry directly starts the inner menu entry.

File Type Menu Description
ROM Image Maxflash Studio Multiple entries are supported for many versions of Atari Maxflash Studio. Direct start is supported for the menus created with the latest "Maxflash Studio" version.
ROM Image MegaCart Studio Menu Multiple entries are supported for all official versions of MegaCart Studio. Direct start is supported for the menus created with the latest version of MegaCart Studio.
Disk Image Bootmanager by Mike Langer Multiple entries are supported for the 1996 and 2022 versions of the Bootmanager by Mike Langer. Direct start is not supported. You can find the massive archive of disk images that use the Bootmanager on the Homesoft website.
Disk Image MyPicoDOS Menu by Matthias Reichl (hias) Multiple entries are supported if a "PICONAME.TXT" configuration file is on the disk. Direct start is not supported.

Previewing Workbooks

The menu entry "Tools/Preview" allows for a testing preview of the complete cartridge export and its menu in an emulator. The workbook is exported as a ".CAR" file with a fixed name into the user's temporary folder for the preview. A previously existing preview is overwritten automatically. If no path to an emulator executable is configured in the options, "The!Cart Studio" tries to open the ".CAR" file with the associated default program of the operating system. If that fails, it will ask you to maintain the full path to the emulator, for example, to "Altirra.exe" or "atari800.exe" in the options.

Exporting Workbooks

Export Formats

Export Format Description Supported Flash Types
BIN Cartridge Image Single plain binary cartridge file without header information with exactly the size specified by the flash type. It can burn or flash the cartridge file to a physical cartridge with an arbitrary Eprom burner or flasher. You can also run the cartridge file in an emulator like Atari800, Atari800Win, or Altirra. The emulator will try to detect the cartridge type from the ROM size and content. In case of doubt, the emulator will prompt you for the correct cartridge type whenever you open the file. Therefore, using the "CAR Cartridge Image" export instead is recommended in this case. Atarimax 128k
Atarimax 1MB
The!Cart 128MB
User Defined
CAR Cartridge Image Single extended binary cartridge file with header information. It can be used directly to run the cartridge file in an emulator like Atari800, Atari800Win, or Altirra. The emulator will detect the cartridge type from the header, so you don't have to select it when opening the cartridge file. Atarimax 128k
Atarimax 1MB
The!Cart 128MB
User Defined
ATR Programming Image for AspeQt Single disk image in ATR format for use with AspeQt and the "The!Cart" flasher software on the Atari. The ATR file uses large sectors to achieve the maximum transmission speed and to store up to about 512 MB of information (65534 sectors of 8k size) in a single file. The file contains additional information to support incremental flashing to speed up flashing in case only parts of the project have been changed. In addition, the file only contains the used sectors. Therefore, this export format can also be used to program "The!Cart" cartridges of a size smaller than specified by the flash type, as long as the size does not exceed the physical size of the cartridge. The!Cart 128MB
User Defined
ATR Programming Images (16 MB) Multiple disk images in ATR format for use with SIO2USB, SIO2SD, SIO2PC, or AspeQt and the "The!Cart" flasher software on the Atari. The ATR files use regular double-density sectors to be compatible with SIO2USB, SIO2SD, and Atari DOS versions like MyDOS and SpartaDOS. The files contain additional information to support incremental flashing to speed up flashing in case only parts of the project have been changed. In addition, the files only contain the used sectors. Therefore, this export format can also be used to program "The!Cart" cartridges of a size smaller than specified by the flash type, as long as the size does not exceed the physical size of the cartridge. The!Cart 128MB
User Defined

The export also generates a ".txt" index file with the title and origin of all menu entries. This way, you can use the file system search of your operating system function to find games in exports. The index file also contains the information that, for example, "Amaurote 128 (130 XE)" is one of the menu entries that result from the "Multiple Entries" setting for the workbook entry with the title "GAMES403" stored in "GAMES403.ATR".

Printing Workbooks

You can print the workbook's content, including the list of entries, via the menu entry "File/Print" (CTRL-P). The columns in the print output are the visible columns on the entries tab. Hence, you can configure the columns you want to see as described in the section General Usage. For example, you can make the column with the start bank visible to use the simple menu to start entries and see the banks assigned to user space entries.
Print output

Programming Flash Cartridges

The!Cart

  1. Plug "The!Cart" in and power on your Atari.
  2. Press "ESC" to leave the extended menu and enter the simple menu with the black text screen.
  3. Press "F" to select the built-in flasher and then "RETURN" to start it.
  4. The flasher will automatically detect if the attached storage device supports high-speed SIO.
  5. Press "1" for "Program Cartridge".
  6. If you use AspeQt and SIO2PC, insert the single large disk image created in the step Exporting Workbooks into the emulated drive "D1:" in AspeQt.
  7. If you use SIO2USB, SIO2SD, or your alternative storage device, insert the first of the nine 16 MB disk images created in the step Exporting Workbooks into the emulated drive "D1:" in AspeQt. If your storage device supports emulating multiple disk drives, insert the disk images 2..9 in the subsequent virtual drives. This way, you can leave the Atari alone longer during flashing.
  8. The flasher will prompt you with "drive number (1-15)".
  9. Press "1" and "RETURN" to start loading the data from the disk.
  10. The flasher will load the header information and display the workbook title, date, and number of used blocks. It will indicate if the export consists of multiple 16 MB images. In that case, you can search for further 16 MB disk images in all available drives.
  11. The flasher will prompt you, "Perform incremental update (y/n)?"
  12. Press "y" to use the incremental update.
  13. The flasher will prompt you with the message "Start programming (y/n)?"
  14. Press "y" to start the actual flashing.
  15. The flasher will load the checksums and determine which differences exist between the current content of "The!Cart" and the exported workbook. Only blocks that are different are loaded and updated.
  16. When done with programming, the flasher will prompt you with "Press any key to continue".
  17. Press "S" to start the cartridge.
  18. The flasher will prompt you with "Start Cartridge: 'E' for expert menu (y/e/n)?".
  19. Press "y" to start the updated extended menu.

Important Note: If "The!Cart" no longer starts after flashing...

In sporadic cases, for example, when I/O errors corrupt the first few banks of "The!Cart", you may be unable to enter the menus or the built-in flasher from "The!Cart" itself. Then you have the following options:

Extended Menu

Pressing the RESET button on the "The!Cart" cartridge and pressing the RESET button on your Atari will take you to the menu. If the cartridge contains the extended menu, holding OPTION while pressing RESET on the Atari starts the simple menu. This allows for creating the built-in flasher and updating the extended menu if it does not work correctly. Holding SELECT while pressing RESET on the Atari turns off the cartridge completely. This allows for starting booting the flasher from a disk drive.
You can use the joystick or the keyboard to control the extended menu. You can filter the list by selecting the tab of a genre. The "All" tab always contains all entries. You can narrow the list within a genre tab by typing any word or part of the menu entry title you want. The search will find the menu entry, whether lower or upper case. You can also use the joystick and the cursor keys to scroll through the result list. You can use the following controls: The most recent version of the CPLD logic for the "The!Cart" cartridge supports a configuration lock. The configuration lock ensures no software can unintentionally or maliciously change the contents of the "The!Cart" cartridge. If you have an early version of "The!Cart" cartridge, you can use a JTAG interface to update the CPLD logic. By default, the configuration of "The!Cart" is locked when an entry is started. This means the configuration can no longer be changed via software until you press the "RESET" button on the "The!Cart" cartridge. You can prevent the configuration lock when starting an entry by pressing the "SHIFT" key as an additional modifier. This can be useful when using software built to access the "The!Cart" cartridge in native mode, for example, RAM disk drivers.

Advanced Topics

Several advanced features of "The!Cart Studio" that are not so interesting for the regular user are also available.

Trouble Shooting

In case of problems, post your question to the forums mentioned at the beginning of this document. Frequent mistakes are

For testing, if your cartridge and the flasher work correctly, several test workbooks are available for download here. If the computer does not even start with the cartridge inserted, you can try holding down the "OPTION" key during power-on to bypass the cartridge. Then, load the flasher program from the disk and flash the cartridge again.

Related Links

Compatibility Patches

This is a list of patches for programs that don't work out of the box with newer or non-standard Operating Systems or with the ATR loader of "The!Cart". For them, you can adapt the default parameters determined by "The!Cart" Studio. Just enter the solution listed in the "Parameters" column of the respective workbook entry to patch the files during the export. Since the offsets specified here are specific for a given disk image, they may not work on others.

Program File Issue Solution
Amaurote 128 (130 XE) GAME403.ATR It uses the memory starting at $480 during loading, hence overwriting the ATR loader if it uses that area. base=$0500, $011d=siov
Bandits Bandits (1982)(Sirius Software)[OS-B].atr It uses an indirect jump to the disk SIO vector to hide where it takes place. This requires an additional patch location, "$119D1", to be added manually. base=$500, $45=dskinv, $1617=dskinv, $208f=dskinv, $5326=dskinv, $0105c9=dskinv, $01065e=dskinv, $119D1=dskinv
Bounty Bob Str. Back! GAME049.ATR It uses the wrong PORTB value, $8f, when activating the OS ROM, causing extended RAM to become active in extended machines. The data from the empty extended RAM is copied under the OS, and when pressing RESET, the blank data is copied over the actual program. Though the program seems to start correctly, it'll break later. base=$0400, $011d=siov, $122ed=$ff, $12318=$fe
M.U.L.E. GAMES067.ATR The crack intro uses the normally unused stack area at $114 and page 4 at $400. Therefore, the base address for the ATR loader must be placed at a different address. base=$0600, $011d=siov, $016a01=$ae, $016a02=selected_item_number, $016a04=$4c, $016a05=$8b, $016a06=$09
Popeye GAME009.ATR It uses an illegal entry point to OS-B, so it doesn't work on a standard Atari XL. base=$0400, $011d=siov, $1101a=$ea, $1101b=$ea, $1101c=$ea

Change History

2023-08-31

2023-08-28

2023-05-29

2023-05-21

2020-08-13

2020-05-21

2020-01-01

2019-12-24

2019-11-26

2019-11-04

2019-10-28

2019-08-29

2019-07-20

2019-06-01

2019-03-02

2018-08-05

2018-07-17

2018-06-17

2018-06-06

2018-05-05

2017-10-30

2017-06-21

2015-09-20

2015-08-08

2015-08-07 - Fujiama 2015 Edition

2015-04-26

2014-09-25

2014-09-24

2014-09-22

2014-09-16

2014-09-11

2014-08-04

2014-07-18

2014-07-12

2014-07-02

2014-04-03

2014-03-18

2014-03-02

2014-02-27

2014-02-22

2014-02-16

2014-02-13

2014-01-23

2014-01-17

2014-01-15

2014-01-14

2013-12-28

2013-12-26

2013-12-18

2013-12-13

2013-12-12

2013-12-11

2013-12-06

2013-12-05

2013-12-04

2013-12-02

2013-12-01

2013-11-26

2013-11-25

2013-11-04