>My old Ipac2 didn't support this, but the ones made after Aug'02 (?) >support on-the-fly programming.
They supported it long before that. Aug' 02 was about when the WinIpac software came out. Before that you had to use IPACUTIL, but it would do the same things.
> Ctrl files are easier in Mame32.
>If you're using a different front end, you can probably script it to call >the Ipac utility and update the key mapping there.
You can, but it's safer, faster, and simpler, and easier all around to update it in MAME than in the I-PAC software. I don't think there's any difference between Windows MAME and MAME32 as far as ctlr.ini files.
>If you're gonna remap it and physically wire each button to its own >terminal position on the Ipac, than it really doesn't matter what >button # is which.
Good point. I think this confuses a lot of people who are new to the Scene.
Consider Button X below:
X 2 3
4 5 6
I can wire Button X to P1B1 on the I-PAC, use the default I-PAC code set, use the Default MAME code set, and Button X will work as Button 1.
I can also wire Button X to the P2B2 terminal (S) on the I-PAC, re-program the I-PAC so P2B2 is left Ctrl, use the Default MAME code set and Button X will work as Button 1.
I could also wire Button X to the P2B2 terminal (S) on the I-PAC, leave the default I-PAC codeset, reprogram MAME (ctlr.ini files or INPUT-ALL GAMES) so P1B1 is "S", and Button X will work as Button 1.
Finally, I could wire Button X to the P2B2 terminal on the I-PAC, re-program the I-PAC so P2B2 is Q, reprogram MAME so P1B1 is Q, and again, Button X will work as Button 1.
So as you said, there are several ways of getting the desired results.