Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Joppnl last won the day on October 12 2017

Joppnl had the most liked content!

About Joppnl

  • Rank
    Advanced Member

Profile Information

  • Gender
  1. Pin2Dmd Colorprism V2.0 Firmware

    THANK YUO, THANK YOU!!!! It's 'alive' again...!! Did a lot of testing and came down to this one problem: - in the pinmame test/run rom everything was fine. Perfect colors on pin2dmd. When running Metall. in VPX table and BG showed up but then it -hard- crashes to Windows. When using the same rom but just disabeling the colorize function the table does start. Using a non-colorized ROM but enabeling the colorize option did work to but not the nice colors of the real colorized ROM. Now, then I did the updates you suggested (pin2dmd firmware 2.57 shows 2.55 in display and 2.53 in colorprism but ok). Latest pinmame tried it...nothing, same problem. I did not download the seperate .dll from github as I think the .dll in the latest total package is te latest dll (??) But...then I had a look at this at91jitt $#%@$%!thing!! There was a '1' as value. Changed it to 0 and....it takes time before the table starts up but it worked! Put it back to 1 and crash again, rebooted the PC, put it back to 0 and it works again! Now...the only strange thing and question is.... How the h*ck can this value be changed all of a sudden? I defenitely know it was a 0 before (although all my tables worked fine I just did a check, long ago). Only thing I lately changed is that I removed my Geforce card and installed a 1070 NVidea card + drivers.... could that change it? Anyway...it DOES seems that this has been the problem, I did not un-91jit all the entries in the register, but it seems to be a reproduceble error and solution so I guess this it it, thank you again for your help, have a drink :-)
  2. Pin2Dmd Colorprism V2.0 Firmware

    Only the pin2dmd .dll, did not install freezy's (would it be any better for pin2dmd?) But also with your .dll it's possible to uncheck 'use external dll' and then when enabeling it on the BGoptions it shows a virtual dmd and the table does start instead of crash. Now, to summerize: for me 2.50 is fine and it works ok but no real color rom's anymore. What I can do is...test it again and see when I change some hardware options (like cables) if it comes back (I wonder), I could try Freezy's .dll to see if that makes any difference and if not I could 'USBcapture' the data when a color rom is set and when VPX crashes. Or if you have an idea pls let me know, thank you!
  3. Pin2Dmd Colorprism V2.0 Firmware

    Hi Lucky, can I ask for support on this... I've been updating everything to the latest...latest pinmame (v3.2 rev 4641), latest VPX (v10.5.3490), latest pindmd (2.57 (although display says 2.55). Now.... a lot of STERN tables do not work anymore: when starting up the BG comes up, table comes up (no lights) and then....few seconds, VPX hard crashes, back to Windows screen. Of course this could be everything but... When I go into the test-function of pinmame itself and I choose game-options, disable external .dll then the table is fine, starting perfect (although no pin2dmd but when I enable it, I can get a virtual display. Now...this might be a sign that there is something with the pin2dmd as disabeling it from the f1 menu (or, as I can not get the table running I change it in the Pinmame test menu). As a test I switched all to non-colorized ROM's. As a wild gues I reverted the pin2dmd software (both firmware and dll to V2.37 (I know...old one) and that worked! Tested 2.45: also ok....2.50..also ok 2.55 does not work for me and also 2.57 does not work anymore. So, with 2.50: now tables start, real colored rom's won't work (but that might also be a pinmame issue) standard colorized option does work. Now...any clue? 1 thing I do not know: I am on Win7 64 bit. Do I need the 64bit dll from the github source? (I tried it but it did not work as well). Tested with: AC/DC Rom : acd_168 Avatar Rom : avr_200 Metallica : mtl_170h color roms for ad/dc and mtl I can not get to work (anymore) with this 2.50 pin2dmd version Thank you!
  4. Hello everybody!

    spagb100 romtest gives a failed to load dll error.

    vinspa says it can use the rom, but dmd screen stays black, and table won‘t start.

    what can be the issue there?

    help is appreciated..



  5. Pin2Dmd Colorprism V2.0 Firmware

    Update: although 2.55 works now I did not see any color change when I switched to an other pin2dmd.pal file from an other table where I knew the colors where different. So...I removed my VPinspa folder and replaced it with a setup -found- 'somewhere' and now everything is fine, even no problem with the spgb_100 folder and, putting in an other .pal file gives a different colored display so...all good. Thanks for your support!
  6. Pin2Dmd Colorprism V2.0 Firmware

    Found it! 1st: used your pal : same error. The my eye catched this... The name of the 'ROM' in the VpinSPA folder is spagb100 Now..in this same folder there is also the altcolor folder. In this folder there was a subfolder, and that was the fault,: spagb_100 (notice the underscore) So..changing the spagb_100 to spagb100 did it and now it works. Strange though that when the VpinSPA program can not detect a .pal file it crashes.... And strange that the 2.50 dll does not have this behaviour and the 2.55 does. But found it, thanks for your help!
  7. Pin2Dmd Colorprism V2.0 Firmware

    Now...that's interesting... Using firmware 2.55 and .dll 2.55 and UNchecking the colour option : GBruns great...even with the same green colors I see when I do check that option. Pressing F1, enable/check color option, restart table and the problem is back...with install spa utility uncheck the color and it will work again...😊 You have any clue?
  8. Pin2Dmd Colorprism V2.0 Firmware

    Good thinking! But....no I am already using the Winusb as driver. Nevertheless..... I deleted the libusbk file, ran Zadig again and installed the same driver again (see attachment) and gave it a try, no luck. What I see is this: 1st: on power up : pin2dmd has the normal standard color-blocks as it shows when it's reset (this is ok, no software has run). When I enter the spa-pinmame and run the GB test - start: I do see a colorchange in the square blocks on the display but spa-mame crashes without warning. Display color stays changed, now, running the test again does not change anything, only the crash. I did make a USBcap of these 2 tests, may-be it helps? (see file attachment underneath driver-picture) Thanks for your support! pin2dmd_no_gb
  9. Pin2Dmd Colorprism V2.0 Firmware

    Thank you for testing Lucky. I did test what you said and it is the same behaviour as starting the GB table with VPX: with the 2.50 dll I can start the display-test but when I use the 3 files from 'integration' V2.55 and I press start then the program is 'thinking' for a few seconds and then terminates without any warning, just like starting GB within VPX. In case it helps and you want to have a look: here are my files on the vpinspa which do not work : https://we.tl/DBOMtaH8Xn Thanks!
  10. Pin2Dmd Colorprism V2.0 Firmware

    Checked that but it was never enebled and still is on 0 for that spagb_100 entry. For me: now I run firmware 2.55 and dmddevice and the other files in integration from 2.50 and I do a handcolorization by the F1 menu and that works. Tested it with both GB 1.1 and 1.2 but does not work here. VPX 10.5.0 rev 3359, can upgrade to 3385 to see if that makes any difference... Edit: updated to latest VPX Beta build and latest pinmame (mrch 2018) but no difference thanks!
  11. Pin2Dmd Colorprism V2.0 Firmware

    OK, 1 problem solved, an other one comes in..... (never a dull moment with VP) Frimware pin2dmd : 2.55 Used dmddevice etc from 'integration' also 2.55 Ghostbustbusters won't start. As I run it I do see a short dmd initialisation (change of color?), backglass comes up but playfield won't and VPX terminates. Now....getting dmddevice etc (3 files) from the 2.50 version then everything is fine, GB starts, having display etc. (firmware still on 2.55) I do remember that when I was on 2.50 and Lucky released just a new dll for colorisation of GB I had the same problem. But for now I'll play with 2.55 firmware and 2.50 dmddevice probably without the right colorisation well...perhaps later. PS: other machines then GB run fine on the total 2.55 combination, it's just GB. So... not working dmddevice is 94kB (2.55), working one is 93,5kB (2.50) but you only see this when overwriting one with the other, in explorer both look like 94kB.
  12. Pin2Dmd Colorprism V2.0 Firmware

    After a couple of hours I think I've found it.... looks like a bad usb connection, either the motherboard or at the processorboard causes trouble. Changed cable and made a very careful connection and it seems to work, now I can work backwards to see what is wrong.... Glad it works now...let's play GB! :-)
  13. Pin2Dmd Colorprism V2.0 Firmware

    Now I'm stuck...please some help... Was on V2.50, everything fine. Changed USBport to programming port, copied the firmware files to it , display resets and the firmware is 2.55 on the display, so far..so good. Plugging the USBcable to the other, playing port Windows comes up and says, no driver found. I have had that before so what I do then, I go into the computer and I delete the unknown device. (see picture) After that I start Zadig. But now the problem I can not resolve anymore: When in Zadig I click on Show Device it says : Unknown device and I can not install any driver. Normally here should be displayed something like 'pin2dmd' and then I'm able to install the Windows driver but now, whatever I do, it says no device. Did reset the display by unplugging it and plugging it again, did a total boot seq of the PC....nothing. What can I do more? Thanks!
  14. Pin2Dmd Colorprism V2.0 Firmware

    Great...that will be the answer to the question, thanks!