This monopoly will be the death of me. It keeps developing odd solonoid behaviors. Originally, it was with the 20v solonoids. They'd pulse very weakly - weakly enough that the electric company couldn't kick out. They'd behave fine in test mode, but during the game they'd just barely fire. We brought it in from the field. I changed out the driver board, the solonoid, the ROM, the transformer...everything I could think of. Didn't fix the problem. I just gave up and started stealing parts from it.

I stole both boards for other games, and the CPU board seemed to be messed up. So I thought I'd try getting it working again. Put back the parts I stole, put in a brand-spankin'-new CPU board, a known working driver board, and turned her on. Original prblem gone (yay!). New problem arises. The Chance kickout solonoid now won't kick out properly. Similar symptoms. I can literally put a ball into it during play, and watch it struggle and not kick it out, then hit the test mode button, and watch it kick the ball like a mule. What the heck is going on? If it were a code issue, other people would have this problem. If it were a transistor, wiring, or solonoid fault, it wouldn't be able to kick during test mode. I've tried turning off both the bank, motor, and motor relay. No dice. Any ideas, anyone?

No, one was the original 2.02 ROM, the other was a burned 3.02 Rom, at least according to the file. It was the ROMs in your TSPP?

I didn't try a display ROM switch...not like it could hurt, I guess. I did swap the board though. Might as well try a different version CPU ROM as well. How very weird, though. Is it some kind of bug brought about by running a ROM that was build for a version 1 CPU in a version 2 CPU?

Ok, I took all the sound ROMs out, because if they're not there, they can't interfere. Tried a new display ROM, nada. Tried the 3.20 cpu: wouldn't boot for me. 2.33 booted fine, but same problem. Anyone have a real early rom, like version 1. something?

To be honest, no, I didn't think of it. Will try tomorrow. Thanks for being so helpful, Ralph.

No better with the factory reset on either the 2.33 or the 3.02. Can't think of what else to do.