Hey- lovely Lyman tribute.

However -- every RFM version I tried since the shaker is supported, I get a hard reset before I can finish a game, it is that bad.

Never happened to me on any 1.x software, not 1.5 nor 1.8 (enough memory in the PC).

% Fatal Errors
------------

Game #50070 : Revenge From Mars
Game Version : 2.24 - Sun Dec 19 18:43:00 2021
XINA Version : 1.36 - Sun Oct 30 17:16:00 2021

Current Time : Thursday, 3 February 2022, 7:25:10 pm
*** Fatal: 11 Jan 2022 22:11:10
*** Fatal: Last[XPid 1 APid -1 (grimreaper)] Current[XPid 50 APid 142 (Switch_42)]
*** Fatal: Leff Manager(RT): Error creating leff Run() process

*** Fatal: 3 Feb 2022 19:15:27
*** Fatal: Last[XPid 129 APid 0 (exec)] Current[XPid 66 APid 143 (Switch_43)]
*** Fatal: Deff Manager(SU): Error creating deff Run() process

The last crash was in mothership multiball -- I cannot quite remember where the other one occured.
I think it is quite usual to happen in multiball though.

Is there anything I can do to provide better output?
I would really love a fix, else I would have to trash the shaker and knocker...

talking of which. The 2.24 knocks *twice* for the first two extra balls, but it did knock only once when I got the third one (not a points price this time).

Cheers + Thanks for reading,
--Enver

If I remember correctly, what fails here usually is a bridge rectifier made out of four discrete diodes 4x P601.

Honest?

*** Fatal: 3 Feb 2022 19:15:27
*** Fatal: Last[XPid 129 APid 0 (exec)] Current[XPid 66 APid 143 (Switch_43)]
*** Fatal: Deff Manager(SU): Error creating deff Run() process

Are you saying this is the kind of error you'd get when there's no protection diode? To me it looks more like resource exhaustion, but this is not to say you're wrong, only I'd like to understand what's going on. The reset also never happens early in the game, so that's another pointer.

I did mount the diode on the knocker (but I don't think it was about to go off anyway when the last reset occurred).
I have the Stern SAM shaker, and I am using the original Stern control board. Will check whether this diode is on the board already or if I am really missing one over the next few days.

'newer 2.24'?
Will have a read -- so there are two or more 2.24 then, okay... did not expect that, as the installed one is 2.24.

Cheers+Thanks,
--Enver

Thanks for the feedback! Glad it worked out!

Others told me they never had a problem like I do, agreed. I switched RAM for testing, to no avail. I have another Pinball 2000 machine remaining, so I can switch computers with an SWE1 in case the mainboard variant plays a role, or maybe CPU speed or something like that.

I will also double-check that the crash times logged indeed reflect the hard crash.

I tried connecting to the machine via 'nc' on port 23, and I realised that the command 'reslist' works only a few times: when I start a game and choose some mode, then keep the ball in the shooter lane, after a few runs of 'reslist' the system reboots. Having said that, I sold my other Pinball2000 kit so I cannot easily check if this misbehaviour was already present with RFM1.5 (and there the TCP high-ports bug would even have to be mitigated).

It seems the mothership multiball is a good candidate for when the machine crashes, but I am not sure if I can start this from the terminal.

Interestingly, I just issued "attack_mars start" and after a few seconds without play, the machine crashed and rebooted.

Which opens up another theory: maybe most (testing) people don't have a network card in the machine, and/or have networking disabled?

If you'd find the time to have a look, I suggest we take the debugging 'off line', that is, into personal messages or such to reduce public clutter.

Cheers,
Enver

applejuice Upgraded to 2.24 of 29th January 2022. I turned off the Network connectivity in my original computer and could play without any reset, attacked Mars in the first game (default 2.24 ball savers). Probably this is what most people have.

WITH Network (IP 192.168.1.99, Netmask 255.255.255.0, Gateway 192.168.1.1, DNS 192.168.1.1) though after a few modes I had the usual hard reset.

Hope this helps fixing the beast. Thanks a bunch!

Cheers,
--Enver