After exiting Mamewah, I can't double-click?

[pmc]

Not sure if this is a known-bug (didn't show up in my searches), another emulator's bug, or if it's something else on my machine.

This happened with an older version, but is also happening with the newest Mamewah which I installed last night. Windows 2000 Professional, MAME 0.75B, and an IPAC.

What happens is that SOMETIMES (and many times) after I exit to Windows, I can no longer double-click. Or at least, I can no longer launch applications or open folders. I'm not so sure it's a clicking thing so much as an inability to open/launch. I've also seen the error "item not available" but have not seen that one recently.

Start-menu works, so I just reboot. No problem. But annoying.

I did a whole reconfigure of my Mamewah install last night and I reworked all the .cfg files from scratch so I don't think there's any wierdness there.

It's possible that it's another emu that's causing it and would explain the intermittence too (because it would only happen when I used that emulator that one time).

Anyone seen this? Very annoying.

Oh... anyone using W2K that hasn't figured out how to setup a custom startup screen, Email me. I figured it out last night. It was not as simple as I had thought (or that many web sites erroniously lead you to believe).

[Sephroth57]

can you single click on a icon and hit enter to open it?

[pmc]

can you single click on a icon and hit enter to open it?

I'll have to try that. My gut sense (geek memory) is that I cannot. However, I seem to recall that I could get away with defining a path in START>RUN to get stuff to open.

I'll have to get it to error up on me tonight so I can answer your question. I'm in the mood for Puyo Puyo anyway (man am I addicted to that game).

[pmc]

OK. I tested it.

First off, it happened after using only MAME (boot > Mamewah (from taskbar) > Pacman > ESC > ESC to desktop). So it's not another emu that's causing it.

Select works, but hitting ENTER does not result in a response (same effect as a double-click).

START > RUN > C:\Program Files\Mamewah\Mamewah.exe

ran Mamewah without incident. So I can obviously run executables. I just can't get them to run from the GUI.

Incidentally, Puyo Puyo Sun doesn't work so I had to play under WGENS. Anyone know a Puyo Puyo clone that runs under MAME (any version -- it's all the same damn game!). I'm addicted to PP4 on the Dreamcast! Reminds me of what I went through with Tetris in 1987.  

- Patrick

[Minwah]

That's a pretty odd thing to happen.  I honestly don't know what the cause it, but I am pretty sure it is not to do with MAMEWAH.  The reason I say that is that I do nothing fancy or strange with mouse/keyboard input stuff, nor do I alter any system settings.

I doubt it will work but have you tried right clicking and selecting Open?

[Howard_Casto]

even if you did minwah..... windoze has safegaurds in place so that if you do something funky with the mouse, it only remains affected until the program that altered the mouse exits.  


I agree, sounds like a hosed system to me.

[Minwah]

even if you did minwah..... windoze has safegaurds in place so that if you do something funky with the mouse, it only remains affected until the program that altered the mouse exits.  


I agree, sounds like a hosed system to me.

Thanks Howard I hoped you might have an idea about it

[pmc]

I'll try to skip Mamewah and run MAME directly a few times to see if I can duplicate the problem to take Mamewah out of the picture.

I don't think a right-click to open something worked. I probably tried it.

I have not seen this behavior at any other time than after exiting Mamewah. I will test this observation to be certain.

This is a pretrty straight-laced W2K Pro install built just for the cabinet in September. There's practically nothing else on it but emulators and FEs. I'll be disappointed and suprised if a re-install is required. And of course, I'll now need to find the code that's responsible for doing this to me!

Of course I can work around this by MAMEWAH EXIT -> SHUTDOWN.

Thanks for the responses.

[pmc]

Veeeery interesting behavior today....

Running MAME from a command line straight out of a clean boot resulted in no problems for three times. Then my bug showed up. So it ain't MAMEWAH.

I decided to tune vector.ini while I had the machine up. After a game or two, my bug went away! Hmmmm.....

So I played some more. Looks like "P" no longer pauses anymore (control panel OR keyboard). Now that's funny.

So I run the interactive IPAC mode and check all the switches. The "P" button is dead. Looks like a loose wire. I'll fix it later today.

So what's the possibility a wiring problem or IPAC issue could prevent me from opening a file from the Windoze GUI? Maybe a bad ground or an intermittent keypress could get between double-clicks? Am I grasping?!  

And why would a "P" key press (not the button) be ignored by MAME? It's set correctly in \ctrlr\std.ini.

Anyway.... it ain't MAMEWAH and I don't think it's MAME. Hell, I don't think it's W2K anymore.... I think it's my wiring!

[Howard_Casto]

If a key is "stuck" on the ipac or the ground is faulted, all kinds of crazy things can happen, including interference with the mouse, other keys and general craziness.

A friend of mine noticed that his cab was randomly restarting... it turned out to be an ipac issue.  No it wasn't the "exit keys" constantly being pressed.... the key buffer was constantly full, eventually causing a fatal windows error.  In xp this means an automatic restart.  

So in short, you'd be suprised.  

[shmokes]

Why don't you try unhooking your ipac and plug in a keyboard?  That will help you narrow it down to wiring.