26 replies to this topic

[Torre]

Good afternoon.

I’m almost finished with my cabinet and hopefully will be testing feedback, buttons, etc. this weekend.

I have been loading games over the past week and I get an error message “machine terminated before initialized, check the rom path or rom file” on most of my installs.

These are all VPX tables and I have verified the roms are good through the PinMame test. In fact, I have tested several VP9 tables which use the same rom in the folder and they open and play fine so I’m stumped. I do have a few VPX tables that open fine so the problem can’t be that they are VPX.

So I got out my 10 year old (and relatively slow) laptop running Windows 7 (My VP cab is a brand new gaming PC running Windows 10). I loaded the tables I am having trouble with and they all open and play fine on my old Sony Vaio albeit in desktop mode. Hmm

Any ideas would be much appreciated!

Mark

[giovanni1966]

I had the same error message. The tip from Shugoo helped. Disable "force full screen". Thank you, good man.

[FPVBrothers]

I was having similar issues as OP was; some games were working while others weren't. Roms tested fine. Disabling "Force Exclusive Fullscreen Mode" in the video settings fixed it for me! Thanks Neophyte! 

[Spunkmeyer]

Aaaargh I used the SetDMD util and was working Full screen exclusive mode for a little bit, sometimes a bit jerky ball.

 

So I changed some more options on it and now I get the dreaded " Machine terminated before Initialise " with all roms. Turned off Full screen Exclusive to no avail.

 

Sorry for hijacking but didn't want to make another thread when one here already.

[Spunkmeyer]

Seems I cant use this tool or it " breaks " all the Rom registry entries.

 

Even manually editing individual entries seems to generate the machine terminated error and I have to delete the whole reg entry and load the rom as fresh. 

[BR4iNL355]

Some scripts of the tables need admin rights.

Run Visual Pinball as administrator!

[mbp27]

Hello, I'm using vpx 10.8 for some weeks almost everyday. Today, when I was going to continue configure my tables for head tracking pov, all the tables with rom started to present this issue.
I swear to God that I didn't anything to change that yesterday night.
It's really strange.
An update...since it was a really strange behavior, I decided to restart the pc. Everything's back to normal.
Typical MS solution..