1790 replies to this topic

[GInsonic]

x64 would be interesting, yes. what troubles do have?

Please see screenshot attached, this only happens when compiling x64.

Attached Files

•  VS2019_Errors.jpg   236.86KB   6 downloads

[toxie]

Do you also have the full build log output? This one already only shows the kinda follow-up errors after the 'real' error.

[GInsonic]

Do you also have the full build log output? This one already only shows the kinda follow-up errors after the 'real' error.

 

Stupid noob me 

I compiled the entire solution and mixed up x32 and x64 in the release folders...

Now I generated the single projects and everything went allright!

 

For me both x32 and x64 (Pinmame.exe, PinMame32.exe, Vpinball.dll, Vpinball64.dll) now show the SAM roms when compiled using the color flag!

 

Thanks for your help!

Edited by GInsonic, 28 March 2021 - 05:56 PM.

[Thalamus]

Not the only noob around it seems For my understanding of VS 2019, I'm able to compile 64bit, but once I ask for 32bit to be compiled for PinMAME and PinMAME32, then it craps out quite quickly with :

 

Severity    Code    Description    Project    File    Line    Suppression State
Error    MSB8066    Custom build for 'src\windows\asmblit.asm;src\windows\asmtile.asm' exited with code 9009.    PinMAME32    D:\Code\VSCommunity\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets    240    

I'm probably good though, being able to compile the dll for 32bit VPinmame.dll and VPinballX.exe.

[wiesshund]

Not the only noob around it seems For my understanding of VS 2019, I'm able to compile 64bit, but once I ask for 32bit to be compiled for PinMAME and PinMAME32, then it craps out quite quickly with :

 

Severity    Code    Description    Project    File    Line    Suppression State
Error    MSB8066    Custom build for 'src\windows\asmblit.asm;src\windows\asmtile.asm' exited with code 9009.    PinMAME32    D:\Code\VSCommunity\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets    240    

I'm probably good though, being able to compile the dll for 32bit VPinmame.dll and VPinballX.exe.

I might be wrong as i am not really a programmer

but you might have to flip the project to 32bit before compiling

 

I know i have to do that when building freezys or flexDMD

otherwise i get errors too

[jsm174]

@Thalamus, when you compile the x86 versions of PinMAME, you need to have NASM installed:

 

FWIW, unless you are actively doing dev on PinMAME, you can always grab the latest compiled code as artifacts from the GitHub actions:

 

 

 Screen Shot 2021-03-28 at 9.00.49 PM.png   196.59KB   6 downloads

Edited by jsm174, 29 March 2021 - 01:02 AM.

[GInsonic]

Not the only noob around it seems For my understanding of VS 2019, I'm able to compile 64bit, but once I ask for 32bit to be compiled for PinMAME and PinMAME32, then it craps out quite quickly with :

 

Severity    Code    Description    Project    File    Line    Suppression State
Error    MSB8066    Custom build for 'src\windows\asmblit.asm;src\windows\asmtile.asm' exited with code 9009.    PinMAME32    D:\Code\VSCommunity\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets    240    

I'm probably good though, being able to compile the dll for 32bit VPinmame.dll and VPinballX.exe.

Definitely NASM missing!

 

Please goto https://nasm.us and install both 32bit and 64bit (as Administrator!)

 

And do not forget to copy DX7SDK (https://osdn.net/pro...SDK/Dx7sdk.zip/) and add include and lib directories to the build path!

Edited by GInsonic, 29 March 2021 - 06:27 AM.

[Thalamus]

@jsm174 : Thanks, I don't think I'll be doing any code changes for pinmame any time soon - but, I would not mind being able to compile it, even though you've made it easy to get it of github ( awesome job btw )

 

@ginsonic : Thanks, I was not aware that there are different versions of nasm, that is probably my issue. DX7SDK, believe I've got that covered, appreciate the link though to verify.

 

Update : With the info from the last couple of pages, I've seem to have figured it out - thanks again guys.

Edited by Thalamus, 29 March 2021 - 09:31 AM.

[Thalamus]

@jsm174 | @toxie : I believe that the latest builds at least of vpiname's setup.exe crashes if you use the 'Test' button. Not a huge problem, just use a old one, but, thought I should mention it. I tried both regular and "sc" of VPinMAME-3.4-184-74746b1-win-x86

Edited by Thalamus, 08 April 2021 - 07:50 PM.

[jsm174]

Did you uninstall and then reinstall?

 

Some methods that were in a previous release were deprecated.

 

184 from here right?

 

https://github.com/v.../runs/720340213

[Thalamus]

Yes, from there. No, I didn't uninstall, never had to. I'll give it a go.

Edited by Thalamus, 08 April 2021 - 07:58 PM.

[jsm174]

Can you try just for the heck of it?

[Thalamus]

Oh. Yes, that was the issue - as I said, never had to do it that way so that is what tripped me. Thanks

[jsm174]

cool. thanks. I'll keep an eye on it. I <think> it has something to do with the deprecated functions.

[toxie]

Yes, sounds plausible. But how does VP(X) work, but the Test button doesn't?!?!

[Thalamus]

Haha. Yes, that is a good question. I tried this on both my cab and my computer before reporting and had no issues what so ever with playing. I wanted to look up the rom name and it is convenient to use the test button. That is when I noticed and started to try different things. Obviously, NOT trying to uninstall - LOL

 

First run after the uninstall now, the table was very laggy. Unplayable. Tried the procedure again, now with the old setup and again registering with the new and that problem was solved too. Might be just one of those odd things though. Chose each time not to clean the registry.

Edited by Thalamus, 08 April 2021 - 08:39 PM.

[toxie]

But did you maybe use an old setup.exe with that new/current VPinMAME.dll?

Cause when i use a new/current setup.exe, then the Test button also works without doing the uninstall first.

[Thalamus]

Both yes and no. I decided to put all the new files onto my cab, overwriting the ones I had. Used new setup.exe for the install part. I noticed later the crash, using the list function - no issues playing or anything. What I did then was to just copy an old setup.exe back and once I got the list up I thought that it was a bug with the list function of sorts. That is where the cab's status is now.

 

Here. I downloaded the same files ( desktop test maskin ), Did the same thing, then reported and well, then I did what I just wrote.

 

Hmmm, come to think of it - could it be that I never pressed the install on the cab ? It might very well be true. Many times, just overwriting the dll has been enought. So, now you made me unsure. Hmm. No, that can't be true, I would have tested the install on the crash situation. I'm sure of it.

Edited by Thalamus, 08 April 2021 - 08:55 PM.

[wiesshund]

Both yes and no. I decided to put all the new files onto my cab, overwriting the ones I had. Used new setup.exe for the install part. I noticed later the crash, using the list function - no issues playing or anything. What I did then was to just copy an old setup.exe back and once I got the list up I thought that it was a bug with the list function of sorts. That is where the cab's status is now.

 

Here. I downloaded the same files ( desktop test maskin ), Did the same thing, then reported and well, then I did what I just wrote.

 

Hmmm, come to think of it - could it be that I never pressed the install on the cab ? It might very well be true. Many times, just overwriting the dll has been enought. So, now you made me unsure. Hmm. No, that can't be true, I would have tested the install on the crash situation. I'm sure of it.

 

I ran into same thing
Pinmame worked but test just closed setup

clicked uninstall, closed, clicked install, close
reopened clicked test, it exited
but tables ran
i rebooted and then it made a liar out of me and test worked
no idea why, maybe i should have uninstalled before popping the new files in i guess.

Or maybe some piece of the previous pinmame was floating in memory someplace?
No idea

[toxie]

hmmmppf.. i guess this is the price for cleaning up some 15 year old todos..  ;-/