PinballY
PinballY copied to clipboard
mjrgh
"PINemHi" crashes after autostart
Sometimes "PINemHI" crashes after startup (Automatic Administrator mode). I can always reproduce this crash when I scroll over table "Surf n Safari (Gottlieb 1991)". Therefore I have hidden this table. But sometimes it happens randomly again after autostart. Then I have to quit PinballY and restart it again (Administrator mode). After that the error does not occur anymore.
System: Win7 64 PinballY 1.1.0 Beta 5
Windows Error Message: PINemHI stopped working problem event name: CLR20r3 signature 01: pinemhi.exe signature 02: 1.0.0.0 signature 03: 5abe3944 signature 04: Microsoft Visual Basic signature 05: 8.0.0.0 signature 06: 530f27dc signature 07: 28b signature 08: 3e signature 09: System.IO.IOException OSVersion: 6.1.7601.2.1.0256.48 Territory-ID: 1031
I've seen that a few times, but so far I haven't been able to find a pattern to what triggers it. If you happen to observe a pattern, and you can figure out how to reliably reproduce it on demand, that might help track it down. The error is actually coming from PinEMHi, which unfortunately is closed-source, so it might not be possible to figure out the nature of the problem even with a reproducible test case, or maybe the PinEMHi author needs to get involved, but I don't think he has a way to report bugs other than maybe PM'ing him on vpforums. My guess is that the System.IO.IOException from PinEMHi is related to its config file, but that's just a guess, since that error message from Windows doesn't tell us more than "something went wrong with an I/O operation".
For the reproducible error with the table "Surf n Safari (Gottlieb 1991)" deleting the nv-file in the NVRAM folder of VPinMAME worked. After the file was recreated by a restart in VPX, the error disappeared. A post in the vpforums brought me to it.
For the reproducible error with the table "Surf n Safari (Gottlieb 1991)" deleting the nv-file in the NVRAM folder of VPinMAME worked. After the file was recreated by a restart in VPX, the error disappeared. A post in the vpforums brought me to it.
Thanks for the update. Sounds like you must have had the corrupted NVRAM file issue mentioned in the thread. I still don't have any idea what's behind the transient issue, if you're still having that happen.