Act-Labs Lightgun possibly affecting monitor detection - SOLVED (unrelated)

[BuZz880]

Hi Calamity, crt_emudriver, groovymame and atom-15 are awesome.  Thanks.

Here's my problem.

I have an Act-Labs gun, when I restart my cabinet (Windows restart), it comes back up with a very very dark screen.  I can sort of make out my front-end.  If I unplug, then replug the USB to my Act-Labs lightgun, I can fix the problem.

Or, If I cold boot, ie. power down completely, then power up, no problem.

So my theory is crt_emudriver is not detecting my monitor if the PC is not completely shut down.  I already went into the Bios and disabled USB3, as well as USB legacy and anything to do with Wake On Lan or anything that sounded like it might be preventing the USB ports from being powered down on a soft reboot since I believe that is the core problem.  No success.

So, I wondered if you (or anyone?) had any thoughts.  I realize this might be unique to my setup but I do like the gun once in a while so prefer to keep it, I am pretty sure I did not have this issue with your earlier driver, based on Catalyst 12.5, but I was having other issues with monitor detection at that time so i upgraded to your latest 2.0.  I am on Beta 7 right now, Beta 5 had the same issue, I cannot recall if I tried an earlier Beta, probably not since I was sort of planning on moving to Windows 10 eventually and your earlier ones did not sound compatible. 

I am using:
Windows 8.1
crt_emudriver V2.0 Beta 7 and latest tools.
atom-15 Bios
HD4350 Card (VGA Port)
Act-Labs original VGA gun.
Groovymame, latest version, perhaps not the final version (not relevant to the issue)
K7000 Monitor with a JPAC

Thank you.

[Calamity]

I doubt this is monitor detection related, as long as you have video. Sounds more like the usb is not being enabled on wake-up for the gun. The only thing I can think of is enabling the usb device upon session logon using a software script.

[BuZz880]

Thanks. I will look into that script idea.

[BuZz880]

Ok, so just in case this ever happens to anyone else.
 - My problem had nothing to do with Groovymame or crt_emudriver. 
 - Pure coincidence that I didn't happen to encounter the issue until around when I installed the 2.0 driver.
 - The issue has more to do with my motherboard which is also new combined with my very old lightgun.

The fix:
I used devcon (part of the windows driver kit) to disable then enable the USB ID for the lightgun at reboot.  Easy to script in a bat file or call from vbs.  Done.  Also looks like an interesting tool if you have game controllers that change their assigned number in MAME as it would be easy to essentially virtually unplug then replug them in desired order at windows startup.

Thanks.

[wp34]

Thanks for posting a fix. I've got a pair of those guns I'm having trouble with as well.