Main > Software Forum

Really *WEIRD* MAMEWAH problem

(1/3) > >>

Xochi:

Guys, I just "finished" my cab and am having a really odd problem with it:

I powered everything up and let the main OS GUI come up (Win 2K Pro). I ran MAMEWAH (which I had setup previously on the machine in the cab) and I tested it out using the cab control panel (IPAC based, also tested prior to install) and everything works great.

So far so good. Soooo, I decide to put MAMEWAH in my 'Startup' folder so the cab will go straight into MAMEWAH on boot up. This where it gets weird: with MAMEWAH in the startup folder, it launches MW on boot as I'd expect, but the IPAC (and keyboard on the pass through port) seems locked, no buttons on the CP or keyboard work to get any response from MW. I have to do CTRL-ALT-DEL on the KB (which does work) and kill MW to exit.

I tried taking it in and out, removing all other startup folder items, etc, but the behavior is always the same: if I boot to mamewah it appears locked.

Anyone have any ideas on what it could be or what I could try as a work around?
 

TalkingOctopus:
From what it sounds like, I think that MAMEWAH is probably launching, but you are still in windows.  If you do a mouse click on mamewah, it would switch from windows to mamewah and everything should be good to go.

Unfortunately, I do not have a good solution for this problem.

EndTwist:
So basically, it sounds like MAMEWAH is losing focus after starting? If that is so, you/someone could make a program that sets focus back to MAMEWAH on startup. (in VB for example)

MrSaLTy:
If loosing focus seems to be the problem, you could prolly confirm this by hitting
ctrl-alt-del and from there hit task manager.... then on the applications screen,
choose mamewah and then choose switch to.

If it switches to mamewah and all is well... then that is the problem.  I don't know how to fix it though.
Maybe of there was a way to make it wait a bit before starting.... it may be that the os and other programs are still loading and they somehow grab focus.  Anyways..... good luck.

sac01:
I had a problem like this before, try changeing the order of stuff in your startup folder, make sure mamewah is the last to get loaded...

worked for me

Navigation

[0] Message Index

[#] Next page

Go to full version