PC Failing to boot when using thisoldgame Star Wars USB Yoke Interface

[iamjimmic]

Anyone come across this problem before or have any resolution suggestions....

I'm running a Windows 7 PC with the USB Star Wars Yoke interface from thisoldgame. The PC has an issue booting up when the Yoke and Interface are plugged in.

The drive is solid state, so a successful boot takes just seconds. But with the interface plugged in it invariably fails to load windows and reboots. The screen (an arcade CRT) is blank at this point, so I can't see any messages. Every other boot I get the 'Windows Failed to Start" message with the two options of "launch Startup repair" or "start windows normally". If I select "start windows normally, it usually boots up ok.

Unplug the Yoke and everything is fine.

I have a theory that the Yoke doesn't completely centre itself - it's usually a fraction off the x-axis or y-axis or both. Could it be sending a signal, similar to holding a key pressed down, that is affecting windows as it boots up?

Any ideas?

[pbj]

I'd throw something like this between your yoke and the PC and get on with life..

http://www.ebay.com/itm/5V-30V-Micro-USB-Power-Delay-relay-Timer-control-module-Trigger-delay-switch-/311357481998

[iamjimmic]

I'd throw something like this between your yoke and the PC and get on with life..

http://www.ebay.com/itm/5V-30V-Micro-USB-Power-Delay-relay-Timer-control-module-Trigger-delay-switch-/311357481998

This would almost does what I want, but the USB connection provides more than power - it also passes back the Yoke signals. And I haven't been able to find anything that does that.

After further experiments, I can discount my theory that the offset yoke was the issue. The problem persists with just the USB interface attached - even without the Yoke attached to the interface.

I have also tried various BIOS settings - switching off USB ports before OS (Windows 7) boots - but whilst this seemed to help, the problem of not booting every time still remained.

I eventually swapped the interface with the one that RAM controls made a few years ago - and the RAM controls interface works perfectly - no issues whatsoever booting up.

I have tried two interfaces from thisoldgame and both do exactly the same thing - so I doubt there is an issue with the thisoldgame interface. It must be something to do with my motherboard or OS that just doesn't agree with the interface.

[pbj]

The relay controls the 5V source going to your yoke, nothing more.  You'll have to cut into the USB cable going to your yoke to make this work.

If you don't want to bother with the relay, wire in a toggle switch somewhere hidden?

[lamprey]

I have that board and have no issues booting. Did you try contact TOG and see if they have had that issues reported before?

It's possible that you might be able to change a setting in your bios, but not sure what that would be.

[Thenasty]

I came a problem with my Machine Hanging, not booting correctly, restarting etc.... it drove me nuts. It took me days and days to trouble shoot everything.

Maybe this problem you're having might be the same thing I went through.

I finally figured out my problem and it came down to the setting in bios about USB 3.0 XHCI/EHCI settings ( I had a USB Wireless Mouse plug in this port)

After days or changing RAM, reformatting HD, replacing HD, Cleaning FANS.... I mean the whole works....Then for some reason I unplug the USB wireless mouse and the damm thing worked (That light the bulb on top of my head). So I plug it in again and it acted weird again. So I thought the MOUSE is shot. Changed it to a WIRED mouse in the same USB 3 port and..... same problem.

Then I said the port is bad, don't use it...... I went back to BIOS and saw this USB 3 setting. It say, "If your having problem with XHCI mode, change it to EHCI mode.

After I changed it, put back my Wierless USB mouse in the port and..... PROBLEM IS GONE FOR GOOD.

My PC defaulted to XHCI setting.

Look in the BIOS setting for USB 3.0 setting and set it EHCI.

[iamjimmic]

Hi,

Tried the playing about with XHCI/EHCI mode but still issues.

Of note, the thisoldgame interface works fine with an old Mame build PC and my Windows 7 laptop. So it all points to something in my BIOS.

As I've got a RAM controls interface, I'm content to use that and probably sell my thisoldgameone - or save it for another build.

I did drop Kendra at TOG a note before posting this thread, but it wasn't something the had come across before.

Of note, the motherboard is an ASUS H81M-Plus.

Thanks for your help...