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

    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!
  2. 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!
  3. 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?
  4. 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
  5. 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!
  6. 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!
  7. 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.
  8. 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! :-)
  9. 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!
  10. Pin2Dmd Colorprism V2.0 Firmware

    Great...that will be the answer to the question, thanks!
  11. Pin2Dmd Colorprism V2.0 Firmware

    Can I ask you this: today I installed the new SAMbuild (4466). In this package there is also a pin2dmd folder and in it is a pin2dmd.dll file. Are updates given through this package or is it best to keep track here on this forum? As I did not see any news here on this forum...should I install this dll from the SAMbuild package or not? Thanks
  12. Pin2Dmd Colorprism V2.0 Firmware

    Hi Lucky, as discussed on VPA I'd test the new 2.50 version, this is my result in 1 evening (will do more later): - this week I had the NASCAR dmd freezing. Table plays fine but there was a moment the display just stopped. Did have that before on an other table as well but tonight, after 8 games of NASCAR all were fine so...may-be an accident then? Will do more tests later this week - as I did have problems with the display not starting up at all in a previous version I tried it this time again: started Avatar a 50 times: all are fine so IO guess this issue is solved. - NOT solved, problem was present before and now: in PB X I have 2 kinds of displays : one of them are static pictures (when there is no dmd on the table like EM or early SS) where the manufacturer is being displayed. When starting a table the display should remain visable when the table starts and during gameplay. Well.....sometimes it isn't. When starting such table mostly it's ok but sometimes (say 1 out of 5) the display blanks when selecting and starting that table from PBX. I'm sure the "hide dmd" option on that table is unchecked : checked it in the game manager and (2nd check) same table starting again from PBX will display the manufacturer display. I did run the usb capture program so I hope you are able to have a look at this. When I saw the problem I did exit the table, did exit PBX and closed capturing so the problem should be visable at the (almost) end. Good Luck(y) :-) pin2dmd_port6
  13. Pin2Dmd Colorprism V2.0 Firmware

    as a test....25 times Avatar opened / closed and about 5 times after that Jurassic Park...all good! Thank you again for your (quick) support!
  14. Pin2Dmd Colorprism V2.0 Firmware

    This evening played Jurassic Park, also a .pal coloured display but also a freeze. Needed a reset with the tool and then it worked. Was running 2.46 It looks to me that if you start with a reset when a table gets loaded it would be solved but don't know if that is a good solution though.