Main > Main Forum

A single beep from the motherboard.. and then slowdown

<< < (7/17) > >>

cdbrown:
Is it the same buttons being pressed and joystick direction each time the pc beeps.  I just tested on my keyboard and when I press 5 keys at the same time - nothing comes up on the screen and pc beeps.  But you have said before that holding all buttons down (except shift) and moved the joystick and all is fine.  Perhaps the x-arcade encoder is dodgy.  Would be interested to see the default.ini file in the XArcade ctrlr folder (if you have told mame to use that ctrlr file).  That numlock problem is due to the ctrlr file being mapped to
P1_JOYSTICK_UP          "KEYCODE_8_PAD"
P1_JOYSTICK_DOWN        "KEYCODE_2_PAD"
P1_JOYSTICK_LEFT        "KEYCODE_4_PAD"
P1_JOYSTICK_RIGHT       "KEYCODE_6_PAD"
instead of
P1_JOYSTICK_UP          "KEYCODE_UP"
P1_JOYSTICK_DOWN        "KEYCODE_DOWN"
P1_JOYSTICK_LEFT        "KEYCODE_LEFT"
P1_JOYSTICK_RIGHT       "KEYCODE_RIGHT"

Also was this what you were talking about shift before
P1_BUTTON4              "KEYCODE_LSHIFT"

Now that you've remapped do you still get the problem in the xarcade tool regarding one button cancelling out the joystick?

Tiger-Heli:

--- Quote from: cdbrown on March 11, 2004, 12:39:03 am ---Is it the same buttons being pressed and joystick direction each time the pc beeps.  I just tested on my keyboard and when I press 5 keys at the same time - nothing comes up on the screen and pc beeps.

--- End quote ---
That's because modern keyboards are designed to prevent ghosting and won't allow three keys in the same square on the matrix to be pressed.  The encoder in the X-arcade should not have this problem, though.

--- Quote ---Perhaps the x-arcade encoder is dodgy.  . . . That numlock problem is due to the ctrlr file being mapped to
P1_JOYSTICK_UP          "KEYCODE_8_PAD"
instead of
P1_JOYSTICK_UP          "KEYCODE_UP"

--- End quote ---
And it is mapped to keycode 8 instead of Keycode Up probably partly b/c (as I said above) the UP Arrow sends more codes to the keyboard buffer, and possibly the X-Arcade encoder can't handle it.

A bit of history, before I get flamed by X-Arcade.  HotRod basically started this with their encoder.  The official story is that it was for compatibility with older programs and older keyboards that did not have separate arrow keys.  But when it was being sold, MAME was it's most common use.  And MAME has always used the arrow keys as default (poor choice, performance wise).  So I suspect the choice of the Numpad keys had more to do with the performance of their encoder.  But since it's non-programmable, there's no real way to test this.  I suspect that X-Arcade selected the NumPad keys mainly to have forward compatibility for people purchasing it to replace a HotRod, but the fact that the NumPad keys provided better performance probably didn't hurt either.

--- Quote ---Now that you've remapped do you still get the problem in the xarcade tool regarding one button cancelling out the joystick?

--- End quote ---
Good question, Truz?

Truz:
yes i remmapped the button that was mapped to shift and replaced it with M.

Then i went into the x-arcade utility and i still had the problem with that button and the control stick being pressed at the same time. They are still basically cancelling each other out.

SirPeale:
One thing you have not mentioned is what motherboard you have.

Your 'specs' are certainly up there - P4, tons of RAM...but a crappy motherboard will be a serious bottleneck.

The two most important pieces of any computers system, in order, are: Power Supply and Motherboard.  Without them, you have a box of parts.

Tiger-Heli:

--- Quote from: Truz on March 11, 2004, 08:49:55 am ---yes i remmapped the button that was mapped to shift and replaced it with M.

Then i went into the x-arcade utility and i still had the problem with that button and the control stick being pressed at the same time. They are still basically cancelling each other out.

--- End quote ---
I wouldn't think that should be happening.  Maybe it's a wiring problem with the X-Arcade, or with it's encoder (your specific one, not in general).

At this point, I think I'd give their tech support number a call and see what they have to say

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version