Copy up to a 31K ColecoVision ROM IMAGE file onto a self-booting ADAM DDP IMAGE file

This process is only compatible with 31K or smaller ColecoVision ROM IMAGE files. If you attempt a 32K ROM IMAGE file, it will load and seem to work, but will eventually crash.

Files in ZIP Archive:

FILE 1 - original master to be repurposed - Evolution.DDP

This is a previously configured CV ROM IMAGE of Evolution that was setup as a self-booting ADAM DDP IMAGE file. It contains a Boot Block (block #00), a standard directory (block #01) and the Evolution rom dump (blocks #02-17). The Boot Block instructs the ADAM to load the BASICPGM file starting on block #02 and seeing as the ADAM doesn't care what the code stating on block #02 is, it happily loads and executes it.

FILE 2 - ROM file renamed to a DDP file - BC Grog's Revenge.DDP

This is a cart dump of the game BC Grog's Revenge. It is a 24K ROM IMAGE file that I have simply renamed from *.rom to *.ddp for easier use in copying it to FILE 1 using File Manager v3.0 seeing as the ADAM really doesn't care what the file contains.

FILE 3 - finished product - BC Grog's Revenge ADAM DDP version.DDP

As it says, this file has the ROM IMAGE of FILE 2 copied to the appropriate place on FILE 1 to make a new self-booting ADAM game DDP image file.


I used Virtual ADAM emulator to perform this mod for the sake of speed:

1. Mount the File Manager v3.0 disk image in Disk Drive #1
2. Mount FILE 1 in Data Drive #1
3. Mount FILE 2 in Data Drive #2
4. Boot the emulator and File Manager v3.0 will be loaded and waiting for user input
4. Press SmartKey II - Media Functions
5. Press SmartKey III - Copy Blocks
6. SOURCE settings - Data Drive 2, Single-Sided, Start Block #00, Number of Blocks #24
7. TARGET settings - Data Drive 1, Single-Sided, Start Block #02
8. Press RETURN to start the copy process
9. Exit the emulator using F10, unmount all the files, mount FILE 1 in Data Drive #1 and BOOT emulator.

I have used this method over the years with great success for all CV rom image files up to 24K in size, but a thorough testing of the results is always recommended.

For compatibility with rom image files that are 32K, watch for a future update.
