VBS script errors

[r3trogear]

* Edit to include my issue is solved. Thanks everyone that commented here, and on Facebook. I appreciate the help. Sometimes that outside persepective is needed. Next time, I have to tell myself to calm down, and work sytematically, like a T-800.

The issue was, that I did not re-register B2S, as per a user recommending on WoVP FB group. It was the ONLY thing I had forgot to do. Todays issue was that my DMDdevice.ini had reverted back to False under the virtualdmd. I now have my DMD back, and FlexDMD works under 64bit as it shold. I got myself all confused on DMDext (which I was not even realizing was Freezy) When I updated it yesterday, It would not alolow me to resize my dmd independantly. My dumbass didn check ignore aspect ratio. I didnt even see it. I have latest Freezy installed and my system is 100% how I want it right now. It is a thing of beauty. Now to get my PinDMD 3.1, solenoids, nudge and plunger and drop it all in my AFM cab

 

 

Installed DMDext at the advice of someone, to fix my issues with FlexDMD. It did not solve the issue. I had backed up all the files beforehand. I reverted back but now I get "No process is associated with this object" error on most tables when trynig to run them.

I reinstalled all the script files in the visualpinball folder. did a scannow and it did fix an error. was missing MSSFMDT.dll in my syswow64 folder so I added that. Nothing is working now. 2 years of work is all screwed up. 

What can I do now? I am beyond furious at myself for messing with it, just for the sake of a few new tables that I couldnt get FlexDMD to work on my 64bit.exe. I really do not want to start over. It has been a long process, which im sure I dont have to tell anyone here.

 

In case it matters, I am on10.8 final, 1.9.1 Flex, 3.6 PinMAME, 2.1.5.1 B2S. 

 

 

Edited January 22 by r3trogear
added my version numbers

[deadmanworking]

What steps exactly did you do when reverting the backed up files? DMDext install is basically only replacing the DMDdevice.dll/DMDdevice64.dll and you must have broken your Vpinmame install or something when reverting. 

Nothing in the DMDext install would be touching your scripts folder etc.. in any case I wouldn't worry too much, these things happen and should be possible to fix if you follow a few steps.

 

To recover I recommend the following: 

-Reregister Vpinmame, FlexDMD and B2Sserver;
-check that you have both DMDdevice.dll and DMDdevice64.dll from the same install;
-re-check that you have the correct scripts from the 10.8 (2051) VPX install

 

If this still doesn't help, I would re-download the Vpinmame, FlexDMD and B2Sserver installs, unblock them, and install and re-register them. 

[r3trogear]

7 hours ago, deadmanworking said:

What steps exactly did you do when reverting the backed up files? DMDext install is basically only replacing the DMDdevice.dll/DMDdevice64.dll and you must have broken your Vpinmame install or something when reverting. 

Nothing in the DMDext install would be touching your scripts folder etc.. in any case I wouldn't worry too much, these things happen and should be possible to fix if you follow a few steps.

 

To recover I recommend the following: 

-Reregister Vpinmame, FlexDMD and B2Sserver;
-check that you have both DMDdevice.dll and DMDdevice64.dll from the same install;
-re-check that you have the correct scripts from the 10.8 (2051) VPX install

 

If this still doesn't help, I would re-download the Vpinmame, FlexDMD and B2Sserver installs, unblock them, and install and re-register them. 

Ended up doing all that last night again for a second time, just in case I forgot something first time around. Scripts were all replaced. DMDdevice.dlls were replaced, and everything registered. I did forget to re-register b2s, and that was the issue. And that is basically Why I asked for help. Its so easy to forget something, especially when frustrated, and I needed that outside persepctive.

 

I have DMD back, but its reminiscent of a DMD from years ago. right click on it brings up the old style menu where you need to click "show window border" to be able to resize, and the purple vpinmame logo comes up. I havent seen either of those things in many years. I would ne fine with this as is, but it still bothers me, plus the DMD doesnt seem to be saving position.

I jsut got home from work, and am going to go through all the steps again and see if I can fix it on my own. In the meantime, if you, or anyone else reading has an idea, it would save the headache. 

 

Edited January 22 by r3trogear

[Tikimaster]

Open table. press f1 - switch to external dmd. 

[r3trogear]

VirtualDMD was set to false in my ini, and now it works as should. It's not recalling all my DMD locations but if that's the least of my worries, im in good shape. Also, FlexDMD now works in all my tables on the 64bit, which was the issue that led me down this rabbit hole of nonsense. 

 

I do have one more question though. Where can I bring up the "f1 menu" seperate from launching individual tables? I seem to recall being able to open that up via my folder install, to change master settings there, instead of per table. I cannot remember which .exe it is, however. 

OK, two more questions. How smooth is the transition to a new video card? Im wondering if I should even bother, just for the sake of a few new tables, when I am quite happy with what I have now. 

[r3trogear]

5 minutes ago, Tikimaster said:

Open table. press f1 - switch to external dmd. 

yup that was part of the issue. the VirtualDMD being set to false was what I just found to be the main cause, after switching to external DMD earlier this morning. Thanks for commenting. Any bit of help is always appreciated

[r3trogear]

3 minutes ago, r3trogear said:

VirtualDMD was set to false in my ini, and now it works as should. It's not recalling all my DMD locations but if that's the least of my worries, im in good shape. Also, FlexDMD now works in all my tables on the 64bit, which was the issue that led me down this rabbit hole of nonsense. 

 

I do have one more question though. Where can I bring up the "f1 menu" seperate from launching individual tables? I seem to recall being able to open that up via my folder install, to change master settings there, instead of per table. I cannot remember which .exe it is, however. 

OK, two more questions. How smooth is the transition to a new video card? Im wondering if I should even bother, just for the sake of a few new tables, when I am quite happy with what I have now. 

aha nm everyone. hours and hours of dealing with this, has me not thinking straight. I knew it was a VpinMAME setting, but didnt realize to click "Setup Defaults" in the Setup64.exe.

I am officially good to go

[Tikimaster]

1 hour ago, r3trogear said:

Where can I bring up the "f1 menu" seperate from launching individual tables?

Open Vpinmame folder.
start your setup.exe or setup64.exe.
Click on Test
Choose the rom of the table you want to edit.
open "game options"