Wasn't there something odd in the original Meteor code that was supposed to prevent it from working with an NVRAM installed in the original MPU board?

This project is a good reason to finally get the Alltek board out of my Meteor and get the original board reinstalled. May hang onto the Alltek for testing but doubt I would ever buy another because of the way they handle the ROMs limiting alternative versions.

This project is going to finally make me get the original MPU 200 back into shape. Just stripped off the old sockets, going to remove the memory cap, rejumper for 2732 chips, and install the dual NVRAM module I've had sitting here.

Still need to move Meteor back home but can participate in your Flight 2000 project since that is home and running.

IMG_20191226_182417 (resized).jpg

It looks like the ROM images for the new Meteor code may be off line. Is there a new link for them? I have an extra STERN MPU-200 all rebuilt and ready to run them. The board is configured for 2732 EPROM's at U2 and U6. I seem to recall the images were available as a set of 2716 chips. If there aren't images for 2732 chips I should be able to combine them but just need to confirm the order they should be combined before burning them.

Robert

Thank You! I'm running the 6 digit displays and will see if I can combine and make a set this evening. This note would be good to add within the Readme file in the ZIP

The addressing of those ROM's on the Stern and Bally boards is kind of odd. Ran into that and made more work when I was doing on some work with the Elektra code. Splitting those images to disassemble and then trying to recreate adds extra steps.... When I get back to that plan on scripting more.

This is another pretty cool tool for working with binary files.

https://www.hhdsoftware.com/free-hex-editor

When you did all the code updates was the overall checksum recalculated and intact? Would like to confirm that built-in test is still valid for the version of code at the above link. I did burn a set of the 6 digit version on a pair of 2732 chips. The board boots and I get all the expected flashes but after that nothing on the game (LED is dim as normal). If the checksum is valid then I would expect it found all the images in the correct order and location in the memory map and validated the ROM is ok.

This was an unknown MPU-200 to start with that I rebuilt to use for testing new versions of code like this. It boots on the bench but obviously there is still an issue. If the checksum part is working then I'll focus on the rest of the board first. If that checksum is skipped then I'll double check and burn another set of EPROM's.

Will try making a set of the originals and get the board up and running with those first. Just wasn't sure if the overall checksum was used yet or not. Totally understand about not doing it until the very end. Did the same thing when doing some work with the BackJack code I worked on.

Made a set of original ROM images on a pair of 2732 chips and same issue. Board gets all 7 flashes and then is dimly lit. No lights for attract and can’t get into diagnostic. Definitely a board issue. Back on the bench it goes for trouble shooting. I have some ideas and will work to track down on the weekend. Looking forward to trying the new code.