I have my most recent project playable, but had something happen tonight the really screwed me up for bit.
Playing Defender and everything was going great, and all of a sudden the game slowed down perceptibly. It was playable, but not right. Firing was real slow, and hitting the 1 & 2 player buttons to exit didn't respond.
I ESC'd back to MaLa and could just see a dialog box flicking on and off real fast in the background. So fast that I couldn't even see the gray, just the square shape. I used the mouse to dump out of the front end, and when I got to my Windows desktop I couldn't click on any of the icons or get in the Start menu.
I figured something was just flaking out so I restarted. Same issue.
I then shut the cab off and cold booted... Same issue! To eliminate MaLa as the source of the problem (I was thinking about the losing focus issue I've heard mentioned), I started from the CMD prompt. Same issue!
I fired up another game (Dig Dug) and it was fine. Hmmm.
Back to Defender and it's freaking out and running slow again.
I was starting to get worried my IPAC was crapping out or something. Fiddling around in Notepad, the keystrokes would make a sound, but nothing would appear when I hit the buttons...
This was when I accidentally stumbled upon the problem. The button mapped to Fire in Defender had stuck, and it's either mapped to Alt or Ctrl. It freaked my whole system out. Since Dig Dug uses one button, it somehow didn't affect it. Really crazy, because the erratic behavior in both Windows and MAME made the problem seem much deeper than it actually was. What a relief it was something goofy!