Vplaunch4 and nvram troubles

[brophog]

I'm having a problem. I'm running Howard's Visual Pinball wrapper through Mamewah 1.62. Everything is set up fine and I have no problems with the tables themselves. They load fine, run fine, and exit fine.

However, they do not write/overwrite an nvram file. When I run the tables through the Visual Pinball editor, I do not have this problem.

[brophog]

Nobody has this problem? I can now recreate it on two separate computers, I just can't find a solution of fixing it.

[brophog]

I have a partial solution, although not a correct one. I've messed with this for some time and it appears that it doesn't do this on all tables. Some tables are saving nvram files correctly.

For those that are not, hitting F3 to reset pinmame prior to exiting a table ensures that the nvram file is being re-written.

I'll continue to mess with it and see if it is only a certain class of tables with this problem, and maybe we can bug fix it better that way. For now, hitting F3 ensures I have a new nvram, and therefore, a saved high score.

[Howard_Casto]

Unfortunately it's more of a visual pinball issue then a wrapper issue.  Try launching a table by right clicking it in explorer and choosing play from the menu you'll run into similar issues.  Also I had to write some "anti hang" code because some tables don't want to quit via code.  I have a timeout and if the mame window isn't closed by that time, it's killed.  So that might be an issue as well, although I seldom run into it myself.