1790 replies to this topic

[Outhere]

 

 

 

 

I am using Windows 10
If I use the latest VPinMAME34_beta

and use a SAMBuild
When I run setup.exe and click on TEST VPinMAME closes

 

I found that will happen if you have any error in your vpmalias.txt file
wonder if that could be the same for you?

 

Tried with an empty file, tried with the default that comes with it no change
 

 

Odd

are you using this build or newer?

 

VPinMAME-sc-3.4-279-50e07cf-win-x86

 

have you tried renaming your existing vpinmame folder
then unzip the download into a clean vpinmame folder, just to see what happens when you click test?

 

I use the one from the 1st post
I went back to 33b everything works fine
 

[Thalamus]

Thanks @outhere. Important that we get some attention to this issue and that I'm not the only one having those crashes.

[wiesshund]

 

 

 

 

 

I am using Windows 10
If I use the latest VPinMAME34_beta

and use a SAMBuild
When I run setup.exe and click on TEST VPinMAME closes

 

I found that will happen if you have any error in your vpmalias.txt file
wonder if that could be the same for you?

 

Tried with an empty file, tried with the default that comes with it no change
 

 

Odd

are you using this build or newer?

 

VPinMAME-sc-3.4-279-50e07cf-win-x86

 

have you tried renaming your existing vpinmame folder
then unzip the download into a clean vpinmame folder, just to see what happens when you click test?

 

I use the one from the 1st post
I went back to 33b everything works fine
 

 

That one is outdated
A number of fixes and additions since then

You might try getting the latest off github

[toxie]

NOTE that inbetween some changes the setup.exe had to be adapted, too. So the old setup.exe will not work with the new VPinMAME.dll and vice versa.  :/

[Thalamus]

But, that is the problem. Use the one supplied and it crashes - at least for me it does and has for a while now.

[Carny_Priest]

Yes, I have the same issue with the TEST button in setup.exe. I was thinking it was a Win7 thing.

[toxie]

Do you guys know when this started?

[Thalamus]

No, the honest truth - while Carney created the sam builds, I extracted the dll. I had a very old setup.exe, and one day I extracted everything, probably because of a new bass.dll or something. Don't remember. I know, just like outhere mentions, go back to 3.3 and you can use the setup.exe at least. Earlier in this thread I mentioned it, obviously, when I noticed it myself. At that point in time, you guys also helped me to setup vscode so I could build vpinmame if I wanted to. I believe I actually was able to use one I created myself, but, I won't swear on it because it was so much going back and forth trying to unregister the "old" and getting the new to register without crashing afterwards that I was a bit confused myself to what version I ended up with. To use setup.exe to register the dll is not an issue. It seem there is not issue playing either. But, you can't press the test button and get a list of the roms without it crapping out.

 

Might this have started when auto build was introduced via github ?

[wiesshund]

Do you guys know when this started?

 

was quite a while ago, as far as thread downloads go

but i have not had that issue with the github builds

 

I am using VPinMAME-sc-3.4-279-50e07cf-win-x86, and it works fine

So does the non SC, but i kinda like the color

Maybe put those two in the tread to let them try since they may not have github and appveyor accounts?

Edited by wiesshund, 17 July 2021 - 10:27 PM.

[Thalamus]

Don't have github account ? Right. Both me and Carny have our own repo's of vp stuff ...  I'm downloading betas all the time.

[wiesshund]

Don't have github account ? Right. Both me and Carny have our own repo's of vp stuff ...  I'm downloading betas all the time.

 

Do you have VPinMAME-sc-3.4-279-50e07cf-win-x86 then?

cause there is no issue with that one, nor a good number of them prior to that

but the thread was never updated with any of those builds.

And i know there have been additions to vpinmame recently, because we found some previously unknow things in LTD roms
and so support was added for them.

I think there has been 20 something builds since the one in the 1st post of this thread

 

update to latest · vpinball/pinmame@50e07cf (github.com)

 

See if that one gives you the same nonsense with the test function?

Edited by wiesshund, 17 July 2021 - 11:01 PM.

[Outhere]

 

Don't have github account ? Right. Both me and Carny have our own repo's of vp stuff ...  I'm downloading betas all the time.

 

Do you have VPinMAME-sc-3.4-279-50e07cf-win-x86 then?

cause there is no issue with that one, nor a good number of them prior to that

but the thread was never updated with any of those builds.
And i know there have been additions to vpinmame recently, because we found some previously unknow things in LTD roms
and so support was added for them.
I think there has been 20 something builds since the one in the 1st post of this thread

update to latest · vpinball/pinmame@50e07cf (github.com)

See if that one gives you the same nonsense with the test function?

 

All better -  Thanks
 

[Outhere]

My mistake - No better
When I put a SAMBuild over it and run setup.exe and click on TEST VPinMAME closes
 

[wiesshund]

My mistake - No better
When I put a SAMBuild over it and run setup.exe and click on TEST VPinMAME closes
 

just curious, rename your vpinmame folder so it is backed up and safe

make a new vpinmame folder and put that build into it

does it still implode when clicking test?
I realize there wont be any roms there to test, but for your issue, it wont matter

 

Do you also run windows 7?
I may have a laptop here with win 7 still on it, will have to look.

[RYSr]

Just tried vpinmame sc 3.4 221 as well as v165 from the link on the Sambuild thread and setup exe crashes on my Win 8.1 PC. I don't have a Get hub acct to try the latest v279. Sambuild 3.2b work fine. But doesn't have the newer rom entries I wanted. I tried it on the new Cheech & Chong table and it does not error on finding the ROM file now, but still doesn't run it on table start.

 

Tried creating a new empty vpinmame folder and put the ver 3.4 221 in it and ran install and setup still crashes,

 

new: Tried creating a new folder with the VPinMAME34_beta from the first post in this thread. Uninstalled and reinstalled and tried running setup/test and it worked, then Cheech & Chong table and it worked.

 

I then tried coping the sc-3.4-221 setup.exe into it and test still worked. Then copied the vpinmame.dll to it and then crash happened.

Edited by RYSr, 18 July 2021 - 07:44 PM.

[Thalamus]

@jsm174 - @toxie : Now I'm quite surtain that this is OS related. I have a crappy machine upstairs with Win10. No issues.Win7 on the cab, is a no go. Seeing RYSr post, just adds Win8 to the mix of OS' where it isn't working. Want to make it clear ... SC is what I'm trying to install. I don't want to be without my Sterns

Edited by Thalamus, 18 July 2021 - 07:05 PM.

[wiesshund]

Just tried vpinmame sc 3.4 221 as well as v165 from the link on the Sambuild thread and setup exe crashes on my Win 8.1 PC. I don't have a Get hub acct to try the latest v279. Sambuild 3.2b work fine. But doesn't have the newer rom entries I wanted. I tried it on the new Cheech & Chong table and it does not error on finding the ROM file now, but still doesn't run it on table start.

 

Tried creating a new empty vpinmame folder and put the ver 3.4 221 in it and ran install and setup still crashes,

 

new: Tried creating a new folder with the VPinMAME34_beta from the first post in this thread. Uninstalled and reinstalled and tried running setup/test and it worked, then Cheech & Chong table and it worked.

 

I then tried coping the sc-3.4-221 setup.exe into it and test still worked. Then copied the vpinmame.dll to it and then crash happened.

 

Here, from Github latest build

VPinMAME-sc-3.4-279-50e07cf-win-x86

 

May still blow up on windows 7, looking for power supply to win 7 laptop.
It would have to be the one with the funky 3 pin PSU

 

@Thalamus
WHat is the build date on the last one that works for you in windows 7?

If i find the damned PSU, i could start running through the past builds to see when it hits the toilet.

[toxie]

Or wait.. Did you guys really all use the matching setup.exe and VPinMAME.dll (from the same zip/release) AND press 'Install' before trying 'Test'?

[Thalamus]

YES

 

I did uninstall - saying no to clean the registry and install. Both on Win7 and Win10. Crashes when pressing test button on Win7, not on 10, but, I can't find anything being an issue with the dll itself. Stern games work normally, and new roms does too. YES, using the supplied setup.exe in these cases. Doesn't really help though. Took a copy of setup.exe first. Registered with the new setup. Renamed the updated setup to setup broken and tried using the older one. Still craps out. So, it is basically, the dll that is killing the setup.exe - when the test button is used, no matter if it is a old setup.exe or a new one.

 

Problem is kind of like this now. If you want to go in and look at your roms, change options ... keep an old vpinmame.dll around, some rename mumble jumble, at least now you can adjust almost all the roms, and then when your finished, rename back Method is very hacky and doesn't support newest roms Which I admit, will work for a while. Isn't that many new roms coming around, but I certainly would not have to do this each time.

Edited by Thalamus, 18 July 2021 - 09:02 PM.

[Outhere]

 

My mistake - No better
When I put a SAMBuild over it and run setup.exe and click on TEST VPinMAME closes
 

just curious, rename your vpinmame folder so it is backed up and safe

make a new vpinmame folder and put that build into it

does it still implode when clicking test?
I realize there wont be any roms there to test, but for your issue, it wont matter

 

Do you also run windows 7?
I may have a laptop here with win 7 still on it, will have to look.

 

Doing this made no difference

using windows 10 - 2 computer same thing
 For now I'm using the new SC version from the github without SAMBuild