Command Post utilizes external databases to provide certain features. There is no need to install these databases, but without them, certain features will be unavailable. All Command Post databases have the extension CPDB. You can place the databases in any folder on your calculator, but do not change the names of the databases. We recommend that you archive your databases for best results.

Special Topics:

• Rom Call Database (romcalls.CPDB)
• Memory Locations Database (memdat.CPDB)

Rom Call Database (download)

The rom call database is called romcalls. When this database is installed, Command Post will automatically try to determine which asm statements in the disassembly refer to a rom call. If a match is made, Command Post will place a comment following the statement with the corresponding rom call name. Additionally, if you are viewing the first line of a known rom call in the disassembly view, Command Post will place the name of the rom call in the status line. You can download the current romcalls database from this location (full source code and instructions for making your own database are included). If you make any updates which would benefit the public, be sure to contact us!

NOTE: Command Post will attempt to generate a small (approximately 5K) internal database from the RomCalls database. If there is not enough free RAM to do this, Command Post will not tell you when you are at the first byte of a rom call in the disassembly view.

Memory Locations Database (download)

The memory locations database is called memdat. When installed, this database gives Command Post the ability to name Absolute Memory Addresses. As you move the Hex Editor Cursor, or the disassembly view over a recognized address, Command Post will alert you by placing the associated name in the status bar. You can download the current memdat database from this location (full source code and instructions for making your own database are included). If you make any updates which would benefit the public, be sure to contact us!