austinwilli

[austinwilli]

Thank you for this and DOOM! – great work!

You need to login in order to like this post: click here

[austinwilli]

Same issue here with pindmd v2 device.   Running net framework repair fixed it!  Thank you and Nailbuster!

You need to login in order to like this post: click here

[austinwilli]

Net repair tool worked! Fingers crossed it is resolved. Very odd that microsoft net fix would be required on a new load.

Thank you very much!

You need to login in order to like this post: click here

[austinwilli]

Nailbuster,

I did as you proposed:   altered ini and ran doctor. The pupdmd.exe works and doesn’t kill itself in that mode. (I see the virtual dmd). So the software is setup properly (registry, etc.)

So now I am working on the driver pindmd v2 side of things – as you suggested it would be hardware. What has me lost is that in VP,FX3, other front ends, and ultra tables the real DMD works- Just not popper with pupdmd.

When I have the ini configured for pindmd2=true – the exe kills itself and throws an app error for the exe in Windows event viewer – also throws a companion netframe error (my win 10 has the latest updates) – I am getting the rpc error in doctor only because the pupdmdexe has already died.

 

the event viewer is similar to this:

Faulting application path: C:\VISUAL~1\VPinMAME\PUPDMD~1.EXE
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

 

Any other ideas? Is there a way to set up an alternative way of driving the dmd from popper?

 

Thank you!

 

You need to login in order to like this post: click here

[austinwilli]

I tried that driver – doesn’t work for pindmd v2 –

You need to login in order to like this post: click here

[austinwilli]

Shadow,

Any other suggestions?- I am running into a very similar issue (just posted) – I tried everything you mentioned.

You need to login in order to like this post: click here

[Author]

Posts