Main > Main Forum
IPAC refuses programming?
(1/5) > >>
pmc:
I think I've seen this before in this forum, but can't seem to find it now. Anyone know how to search these forums?

Anyway, I have a few-months-old two-player PS/2 IPAC model on a Win98 machine. Works great with the MAME jumper in place. I moved it to ALT to program some custom shift keys. The software was acting flaky (ignoring input) and inconsistent (different flaky behavior after reboots and s/w relaunches).

So I switched to the console. While weird running a console in NOTEPAD, it certainly works great. And the test function is very nice.

So now everything is programmed and great, BUT, no matter what I do, I cannot get j/s-down to map to "down arrow". The console takes the program attempt, but then when you "list" what's mapped, it's blank. Mapping to another key (e.g., "t") works great, but not down-arrow.

Yes, the down-arrow key works. It works great. And the IPAC console sees me push it too. It just doesn't record the mapping and subsequently does not write it to EEPROM.

So I've been playing alot of Galaga which is OK I guess. But you try Berserk and only move up/left/right!

Any ideas? I hope it's something silly like NUMLOCK or soemthing. Thanks in advance!

- Patrick
Superdude:
Have you downloaded the latest software WINIPAC util from utimarc?  Have you restored the defaults?  I think there is a way to reset the jpac or ipac in the documentation section.
_Iz-:
Are you overclocking your system? Is the system stable otherwise?

Have you tried loading the defaults then just reprogramming the keys you want to change?
pmc:

--- Quote from: _Iz- on June 20, 2003, 01:14:02 pm ---Are you overclocking your system? Is the system stable otherwise?

Have you tried loading the defaults then just reprogramming the keys you want to change?

--- End quote ---

Well, "stable" for Windows98 anyway. Meaning that I get the occassional blue-screen, MameWAH sometimes crashes, the CDROM drive is sometimes not an ATAPI device to the BIOS (a reboot fixes that), the NIC is sometimes "newly discovered hardware" upon boot and needs drivers installed repeatedly and then is listed multiple times as a MAC/PHY device...

Stuff like that. And yes.... I do consider that "stable" for Win98. And yes, I do need to wipe the partition and re-install for a nice clean cabinet MAME install. But I don't think any of that is related to my problem (unless you know something I don't!).

Regarding loading the defaults and starting over -- I'll try that. I didn't because the Windows software seems to repeatedly refuse to take input and I figured it'd be a step backwards. But I can reload the defaults and then use the console to program it. Good idea.
_Iz-:
you can load the defaults from the console as well. You might be better off doing it all from the console. see ultimarcs help/documentation for the command.
Navigation
Message Index
Next page

Go to full version