Leaderboard

ive got a maxima sys100 manual ?

Hi people... I was having great fun starting these last night so I thought I'd share the progress. I got 5 bare boards from my Buddy Rob-the creator of them It's taken around 6 years for me to have a go mainly because of the difficulty level.

that johnparker is a clever chap ..... you can find him on here i think and on youtube https://www.youtube.com/@johnparker007

A lot of this is trial and error, but it shows that it's possible to find settings to change attributes of the game, just takes a while to hunt them down. The speed changes on the hold sequence and the roulette wheel. Same principle as the credit change to 10, Load Accumulator A (LDA) with a value of #$96 and it will decrement (DECA) every scan until the value becomes 0 (Branch if Not Equal to 0 will loop on its self to address 7908), then it will move to the next line. So if we make the value smaller to 45, the pause will be less time, then bigger to FF it will take longer. So to change the value for FF search for the HEX string of 37 36 86 96 then change to 37 36 86 FF Save and reload in the emulator.

MPU 3 roms only check the rom integrity once(on boot up).so once the machine has passed that your good to go.

Interesting that you should mention the the speed of the gamble ed .I noticed there was a marked difference in speed upon selection of the odds between the two rom versions ,ie I think the later version 5x creds for 50p was slower than the earlier 1cred/four 10ps .another reason I prefer the later rom .not sure if it's dip related but pretty certain it's not .

Here's a Motorola M6800 Programming Reference guide. Motorola_M6800_Programming_Reference_Manual_M68PRM(D)_Nov76.pdf

Is there a checksum bypass built in to MFME 5.1? I had a play around with the rom tonight and found that I could make changes to routines and the game still ran in the emulator. Is it possible that this machine didn’t have a checksum routine? I managed to turn off the sound on the roulette gamble, I also found how to slow down the speed of the gamble routine at selection between the stakes. A bit trial and error to watch the code and to stop it after a gamble. Then to look at the assembler commands in that area. Interesting exercise to try to understand what’s going on.