- This topic has 16 replies, 3 voices, and was last updated 3 years, 12 months ago by
.
-
Posts
-
** FIXED ** I had to delay my HOLD_ACTIVATION = 0 signal for 5 seconds after the table shut down which got rid of the Unhandled Exception error. Then I had to untick Run as Admin on FPPlayer.exe in the BAM folder to get PinEvent working. Hope that helps someone else out. Full details in this thread.
Hi all,
I’ve been trying to get the PinEvent table Tomcat working on my arcade cabinet. I can get other DOFLinx systems working and I’ve put a HOLD_ACTIVATION setting in my Launchbox frontend to ‘pause’ DOFLinx when I launch Tomcat as it uses PinEvent.
However, that table gives me the following error:
With this blurb in the Details section:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): Only part of a ReadProcessMemory or WriteProcessMemory request was completed
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.ProcessManager.GetModuleInfos(Int32 processId)
at System.Diagnostics.Process.get_Modules()
at DOFLinx.MainForm.IsFPHacked()
at DOFLinx.MainForm.DoStartup()
at DOFLinx.MainForm.SteamTimer_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DOFLinx
Assembly Version: 1.0.0.0
Win32 Version: 5.0.0.0
CodeBase: file:///D:/LaunchBox/Emulators/DirectOutput/DOFLinx.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
DirectOutput
Assembly Version: 3.1.7527.20768
Win32 Version: 3.1.7527.20768
CodeBase: file:///D:/LaunchBox/Emulators/DirectOutput/DirectOutput.DLL
----------------------------------------
Extensions
Assembly Version: 3.1.7527.20767
Win32 Version: 3.1.7527.20768
CodeBase: file:///D:/LaunchBox/Emulators/DirectOutput/DirectOutput.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Security
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Security/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Security.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Data.SqlXml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Data.SqlXml/v4.0_4.0.0.0__b77a5c561934e089/System.Data.SqlXml.dll
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4210.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.ComponentModel.DataAnnotations
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll
----------------------------------------
System.Web.ApplicationServices
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4210.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Web.ApplicationServices/v4.0_4.0.0.0__31bf3856ad364e35/System.Web.ApplicationServices.dll
----------------------------------------
System.Runtime.Caching
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Caching/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Runtime.Caching.dll
----------------------------------------
Microsoft.Build.Framework
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Build.Framework/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.Build.Framework.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
DOFLinxExt
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/LaunchBox/Emulators/DirectOutput/DOFLinxExt.DLL
----------------------------------------
B2SBackglassServer
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/LaunchBox/Emulators/Visual%20Pinball/Tables/B2SBackglassServer.DLL
----------------------------------------************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Anyone seen this error before?
Thanks for any light you can shed on this.
You need to login in order to like this post: click here
@johnnyt   Did you try running the game without DOFLinx running?
You need to login in order to like this post: click here
1 user thanked author for this post.
I didn’t
Why didn’t I think of that…!
I’m not back at the cabinet until tomorrow so I can try it then. If it works I suppose I’ll have to shut DOFLinx down completely when I run PinEvent tables and then fire it back up when I’ve finished?
I was under the impression that the HOLD_ACTIVATION setting would work? Does that only work for certain systems?
Thanks for the idea Outhere. Much appreciated
You need to login in order to like this post: click here
I didn’t
Why didn’t I think of that…!
I’m not back at the cabinet until tomorrow so I can try it then. If it works I suppose I’ll have to shut DOFLinx down completely when I run PinEvent tables and then fire it back up when I’ve finished?
I was under the impression that the HOLD_ACTIVATION setting would work? Does that only work for certain systems?
Thanks for the idea Outhere. Much appreciatedSome people do have a problem with the HOLD_ACTIVATION for DOFLinx
Terry does have info in his PinEvent guideYou need to login in order to like this post: click here
1 user thanked author for this post.
Hi Outhere,
I have been through the guide a few times (and the videos that Terry has done) and that has got me this far.
However, this is the first of me using the DOFLinx “pause” function so I must have missed that info. I’ll go back through the guide this evening after work when I get back on the machine and I’ll also just double check that DOF is still working on PinEvent tables if I leave DOFLinx off completely.
Thanks for the suggestions and the help. Much appreciated
You need to login in order to like this post: click here
Just a follow up… I managed to get rid of the error by delaying the HOLD_ACTIVATION going off… so my new script (after leaving a PinEvent table) is:
timeout /t 5
cd /d D:\LaunchBox\Emulators\DirectOutput
DOFLinxMsg.exe HOLD_ACTIVATION=0Unfortunately my DOF devices don’t work on PinEvent tables at the moment even with DOFLinx turned off so I’ll run through a re-install of everything over the weekend to try and sort that.
Thanks for your help
You need to login in order to like this post: click here
Update DOF R3++
Even if you think you have it installed… you MUST have the newest version.
http://mjrnet.org/pinscape/dll-updates.html
Update your DOF Config Tool Configs:
http://configtool.vpuniverse.com/login.php
You need to login in order to like this post: click here
1 user thanked author for this post.
Will do Terry. Thanks
You need to login in order to like this post: click here
Just a follow up… I managed to get rid of the error by delaying the HOLD_ACTIVATION going off… so my new script (after leaving a PinEvent table) is:
timeout /t 5cd /d D:\LaunchBox\Emulators\DirectOutputDOFLinxMsg.exe HOLD_ACTIVATION=0
Unfortunately my DOF devices don’t work on PinEvent tables at the moment even with DOFLinx turned off so I’ll run through a re-install of everything over the weekend to try and sort that.
Thanks for your helpBased on what you found
This should also work without a timer Instead of putting it in the close Script
Put it at the top of the launch scripts that required DOFLinx turned back oncd /d D:\LaunchBox\Emulators\DirectOutput
DOFLinxMsg.exe HOLD_ACTIVATION=0You need to login in order to like this post: click here
Yep but that would mean editing about 20 tables as oppose to editing 4
(Good suggestion though
)You need to login in order to like this post: click here
Yep but that would mean editing about 20 tables as oppose to editing 4
(Good suggestion though )Not sure what you mean
You need to login in order to like this post: click here
Yep but that would mean editing about 20 tables as oppose to editing 4
(Good suggestion though )Not sure what you mean
All I was meaning was that I’m using Launchbox as a frontend. Within each ‘game’ within Launchbox you can stipulate an application to run on startup and shut down.
I’ve edited the PinEvent tables to run my batch file to Hold Activation when they start and to run the “Release activation” when they shut down.
All the other tables I don’t do anything special with as I have DOFLinx just running in the background when Windows starts.
If I change it so that I’m running the “release activation” command for every table that would mean editing every table and, so far, I’ve got a lot more non-pinevent tables than ones that use pinevent. (unless I’m missing the meaning of what you said?)
You need to login in order to like this post: click here
Okay
I’m not familiar with Launchbox
With a standard pinball front end you have one emulator set up for the games maybe 2 (For each type of Virtual Pinball – VP, FP, FX3 etc )You need to login in order to like this post: click here
Yep, this was originally intended to just be an arcade cabinet for MAME and some of the old Atari stuff.
Then I discovered VPX, and then Future Pinball and then I discovered Terry’s videos and then I discovered DOF and then I discovered DOFLinx and then PinEvent and then, before I knew what was happening, I’d ordered 7 contactors and a 8 relay Sainsmart board from eBay and then I was frantically wiring and screwing and messing around and, this morning, I’ve just been making a load of marquee images for Pinball FX3…. so I’m now almost exclusively playing pinball and loving it!
I think it’s helped that my kids really love the pinball too, but they weren’t as fussed for the arcade games (apart from the odd game of Tekken 3 with my son).
But my son and youngest daughter have massive rivalry on who is dominating the high score table on the pinball games
Anyhoo…hence LaunchBox as a frontend (which it is a really good front end and very versatile – it’s just that most people on here don’t use it so it does take a bit of tweaking other’s suggestions in order to get it working as I want).
You need to login in order to like this post: click here
Update DOF R3++
Even if you think you have it installed… you MUST have the newest version.
http://mjrnet.org/pinscape/dll-updates.html
Update your DOF Config Tool Configs:
Well, I got to the bottom of it. I followed what you said Terry and the suggestions from Outhere and, one of the things in the install text file of DOF says “make sure BAM FPPlayer is not set to Run as Admin …. if you have problems you can set it to Admin or not depending on which way you had it set”.
When I checked mine was set to Run as Admin so I just unticked that box and now my PinEvents are working great!!
So looking forward to a game of F14 Tomcat tonight with a couple of beers.
Thanks Terry and Outhere for all your help and guidance with this. It’s very much appreciated.
You need to login in order to like this post: click here
Newest DOFLinx now lets you change what process will activate DOFLinx at any time (not just on startup). This is a much better option to use then the hold activation!
https://www.vpforums.org/index.php?showtopic=45152#entry458169
You need to login in order to like this post: click here
1 user thanked author for this post.
Newest DOFLinx now lets you change what process will activate DOFLinx at any time (not just on startup). This is a much better option to use then the hold activation!
https://www.vpforums.org/index.php?showtopic=45152#entry458169
What a great update!! Thanks for letting me know Terry. You’re a star!!
You need to login in order to like this post: click here
Forums are currently locked.
