KeyWiz40-ST input stuck, trying alternative config, get keywiz connection failed

[papaschtroumpf]

Wow, I haven't been on these forums forever, mostly because once I got my cabinet working I decided to stop tinkering/upgrading it, and spend the time playing instead.
My original keywiz died, so I replaced it with a keywiz40-st. It worked for a while but the L1 input (left joystick 1) then started acting stuck: even with nothing connected to it, the computer acts like the left key is being pressed. I also confirm it with a little utility that shows key pressed. When the keywiz is disconnected from the PS-2, no more stuck left key, so it really is the keywiz.

I saw on some board that RandyT says some inputs can get stuck due to poor static protection. Not sure what else to do to protect from static, but I'll assume this is what happened.

The keywiz was almost new when the problem started happening, I just didn't get to it immediately due to some health problems, so I'm reluctant to buy another one if i can avoid it. what I tried to do was remap the L1 input to the "L GUI" key (whatever that is). It seems to have the desired effect, in that Windows no longer sees the left key being constantly pressed, without any "side effects" that I can see, i.e. windows doesn't seem to see a key being pressed, so not sure what "L GUI" is.

I then proceeded to connect my joystick the to M input (because it was the closest free one from the L1 input). I then created a custom  config "A" where the M input is mapped to the left key.

This works fine when I run the keywiz uploader 3 once windows has started. it programs the keywiz with config A, I launch MAMER, and life seems good from then on.

The problem is that when I try to automate the process of launching keywiz uploader 3 at boot, it fails and I get a pop-up "keywiz connection failed". if I dismiss the popup and run the uploader manually, everything is fine again.

I'm not sure why the uploader fails at boot, maybe because it sees the "left" key stuck and doesn't flush the queue and can't talk to the keywiz? (I'm running Windows XP on my cabinet by the way)



Anyone ran into a similar problem? any sugegstion on how to fix the program-at-boot problem? Maybe the first thing would be to try to run the keywiz uploader later in the boot process, since running it after windows starts seems to do the trick. I'm not sure what mechanism is usedto run it an boot, but the program is not in the "Startup" folder.

[papaschtroumpf]

I removed the startup options in the keywiz uplaoder 3 program, and instead added a shortcut to <path>/keywiz_uploader3.exe /A /PA in my startup folder. I specifically omitted the /S option so I could see what's going on.

I see the uplodaer trying 5(?) times then giving up.

if I run the same shortcut again after I exit the first run, codeset A is loaded properly.