Monopoly 3.20 MAJOR bug?

Was burning roms for machines last night, and figured I'd burn 3.20 for
Monopoly and put it in while the burner was out. Got a 1 Meg chip,
burned and verified the binary, checked the checksum, and installed the
new chip into the game. So far so good, everything is blanked, so the
settings reset. Get everything reset and start to play a game to see
what's different.

Get some dice rolls and start moving around the board, collect a few
properties, but then I notice I start landing on and collecting
properties and modes I've already collected and that are already lit.
So I start paying more attention, and every dice roll is a 3 (1& 2).
All of the sudden it's really easy to hit breakout, free parking, and
rip-off multiballs, since one can plan what you are going to land on;
free money over and over was great too. Of course one can also land on
Community Chest, and since there is nothing to award for Community
Chest (since you can never collect it from a dice roll) the machine
goes into Neverland with the blanking circuit flash (where the
controlled lamps flash on and off very brightly opposite the GI lamps.)

Tried doing factory resets and all kinds of other things (install
tournament rules, film star, reset audits, insert coins, etc) to stop
the always rolling three problem, and nothing helps.

I then go back to firmware 3.03, and everything is normal again. So
it's definitely the 3.20 firmware, switch roms again, trying with the
coin door closed, and then open to know it does a dump, get the "open
the door" message. Play a game and it again always rolls three.

Has anyone else updated to 3.20? And if so have you noticed the issue?
While I like landing on already collected properties again, and it
makes the game harder since you have to work harder to get all the
properties, I doubt it should be that predictable, nor should it crash
(have your token on Boardwalk, and then roll the dice).

I hoping Keith will see this and check the code, and make sure there is
not some test he left in (easier to test if one always knows where it
will land), or some new bug introduced this go around. Also hoping to
save others if they erase their chips and recycle, and have no older
code to go back to.

Steve

> I hoping Keith will see this and check the code, and make sure there is
> not some test he left in (easier to test if one always knows where it
> will land), or some new bug introduced this go around. Also hoping to
> save others if they erase their chips and recycle, and have no older

Just FYI, this game was programmed by PLD, not Keith. He could forward
the bug report to Pat Lawlor's company, but I don't think he can fix it
himself.