This is a technical questions for other techies...

[slinger]

This is a technical questions for other techies...

I have my keyboard emulator working (so I thought).

When playing single player everything works just fine but when playing two player, when player 1 moves then player 2 cannot move until player 1 releases the joystick, I just want to know is this a limitation of the PC?? when I check my output I can send as many breakcodes as I like but the pc stops responding after a couple.

Any ideas?

[grafixmonkey]

Keyboard hack, or ipac, or what?

not sure what you mean by keyboard emulator.

[shumph]

also if its a keyboard hack is it usb?

[CthulhuLuke]

That's a ghosting problem, do a search on ghosting, there's a few programs that I think Saint has up that you can to see whats ghosting, and you can just remap your keys so that none of the inputs will ghost, or will have a very low chance, like 2nd player start, and 4th button.
      -Chu

[slinger]

Sorry, this is a keyboard emulator that I created myself, it plugfs into the PC's ps/2 port.

It's not ghosting because that happens when two keys are pressed on the matrix and a third one is "ghosted", I don't have this issue, I'm using a scanning matrix there are no ghosting issues with this method. I have set it up so that the results of the keypress are sent kia the com port (of the emulator) to a laptop to monitor when a make code is sent and a break code is pressed. there are no ghost keys present even when every key is pressed at the same time.

when I see this problem occur both the make codes for the respective joysticks are sent but only one will work at a time, I wonder if I ran into a limitation of mame that I wasn't aware of.

Ron

[rampy]

you created it yourself?  IS it a microcontroller or or

or is it a keyboard hack?

It's possible it's "blocking" which happens with modern keyboards, but if you designed this yourself, it shouldn't be an issue right?

It's hard to trouble shoot this as you haven't give enough info...  what is it you want to know again?

My other random thought is you goofed up the ground wireing or wiring to the NC instead of the NO on the microswitch causes weird phenomemon similiar to what you are describing...

*shrug* else I got nutthin

rampy

[slinger]

->you created it yourself?  IS it a microcontroller or or

I'm using a PIC16F874 Microcontroller

->or is it a keyboard hack?

No keyboard hack here

->It's possible it's "blocking" which happens with modern keyboards, but if you designed this ->yourself, it shouldn't be an issue right?

It does it's job as I designed it perfectly, I'm thinking it's a PC issuse, because the proper codes are being sent, I've actually only noticed this on wizzard of wor, I should try it in windows with say a text editor. I'll try that one tonight.

-It's hard to trouble shoot this as you haven't give enough info...  what is it you want to ->know again?

What I'm asking is if anyone knows of any limitations with the keyboards

->My other random thought is you goofed up the ground wireing or wiring to the NC instead ->of the NO on the microswitch causes weird phenomemon similiar to what you are ->describing...

I'm using NO and all switches are in sets of eight(right now only 4 sets)

->*shrug* else I got nutthin

->rampy