pearsoe

Attached are examples of Mobile Objects working in both Graphics Mode I & II. Since I was testing on an ADAM the examples will only run on an ADAM and are in DDP format. I've included the source for both examples so it could be modified to run from a ROM image. I had to modify the patch for Graphics Mode I mentioned in Appendix B since there was a bug that corrupted the graphics. MOBILE_OBJECTS_EXAMPLE.zip

@tschak909 Could your issues with Mobile objects be related to the PUT_MOBILE bug mentioned in the "Colecovision Coding Guide" on page 2? http://adamarchive.org/archive/Technical/CV Tech Manuals/ColecoVision Coding Guide (2005) (NewColeco).pdf

The JED file is on the Github page under https://github.com/epearsoe/MIB238/blob/main/Documentation/Media/MIB238.jed and it is in the PLD file you uploaded on the last page. It starts with OrCAD PLD-386. I used the JED file from that document that James Notini uploaded. I usually don't include the Eagle project file with schematic on my Github projects but rather complete and tested Gerbers for the DIY builder.

Attached is the ROM I started with. It doesn't have the fuel gauge update graphic issue shown in the screenshot by Keatah. The Moonsweeper ROM has two 768 byte name tables stored; one at $ACFF for the galaxy selection screen and one at $B43F for the game play screen. Both of these name tables had to be edited. Basically the problem with the graphics was the wrong pattern generator was being used. I edited those name table entries to use (what I thought) should be the correct patterns. If you open the attached ROM and the updated ROM (attached above) in a hex editor and perform a compare you can see all the differences. To answer Tempest's question I believe Ikrananka mentioned the problem exists in the released cartridge so I don't think it is from a bad ROM dump. Probably just bad QA before release or a rushed release. Moonsweeper (1983) (Imagic).rom

Cleaned up the graphical glitches in the ROM. The weird red square in the upper left, the wrong characters in the lower left. The fuel gauge update glitch was already fixed in the ROM I had. Moonsweeper (1983) clean.rom

The expansion ROM binary is in a different format than a cartridge ROM so you can't just launch the expansion ROM BIN as if it was a cartridge ROM. You probably could create a cartridge that would boot the hard drive if one doesn't exist.

The Tape code algorithms are calibrated to specific speeds so having a slower or faster DDP would probably throw off those calculations and cause seek issues; under shooting or over shooting the desired block.

I didn't see an answer to NIADs question. If you power on the ADAM, after you get the black screen, if you pull the right hand cartridge reset does the picture change at all or still just a black screen? Also do you have the sound channels from the ADAM going to the monitor? I was wondering if you get any sound when you turn on the ADAM.

From my reading of the IDEBOOTROM code if it detects the HD (or CF drive) it modifies the EOS read block, write block, init dir, find/get dcb, and request device status routines and puts driver code in the E300h area of upper RAM. It stands to reason any program not expecting these changes could have issues especially if it overwrote the driver code.

I think you are trying to do this: ld hl,MUSIC_TIMER ;load hl with the address of the value for MUSIC_TIMER inc (hl) ;increment the MUSIC_TIMER value at location hl ld a,(hl) ;load A with the incremented value at location hl

You can also download it from http://adamarchive.org/ The filename is EOS9Kit.pdf.

There is a recent discussion about EOS9 on the Coleco ADAM Facebook page where James Walters is a member. EOS9 was used in a number of Walter's Software titles and was a custom, enhanced version of the EOS operating system. I don't know of any titles beyond Walter's that used it. Walter's also released the EOS Programming kit which included EOS9. The programming kit manual has reemerged and is available (on the Facebook page files section) but the media for the kit has not. I suppose the media could be reconstructed since EOS9 is built in to those other Walter's titles.

Might want to look at this thread: https://atariage.com/forums/topic/146231-colecovision-labels-thread/?tab=comments#comment-1779506

There are instructions on replacing the Colecovision BIOS in the ADAM on the ADAM Facebook page by John Lundy. The ROMs on the Gamma Board are for Smartwriter and EOS. You might get more traction on these posts if they were in the main Colecovision/ADAM forum instead of in Colecovision Programming.

You should look at http://adamarchive.org There is a lot of technical information on the ADAM there.