MAMEHooker for Dummies (ATT: Howard_Casto, please)

[Curtishart001]

Hey everyone.

Trying to get MAMEHooker to work on my Windows 10 PC so I can get a Q*bert knocker working. I'm using a PAC-Drive as recommended here:
https://web.archive.org/web/20210507193435fw_/http://notrica.com/qbert.shtml
(The most 'complete' set of instructions I can find) but MAMEHooker doesn't seem to recognize neither MAME 0.250 nor the Pac-Drive controller. LEDBlinky sees my board and appears to function correctly when I run it (I have an LED right now for testing on a +5/Pin 1) but so far, every time I run MAME, nothing seems to capture in MAMEHooker.

Any ideas?

TIA

Curtis

[Curtishart001]

Okay,

Hoping additional information I'm putting here can help trigger someone how to get this thing to work. As mentioned, running Mamehook then running Mame 0.250 seems to do nothing.

Debug window is blank when I run MAME. Also, when I choose "Show Supported Devices" my PacDrive board doesn't show.

HOWEVER, I just ran a test in MH, in Test Mode I sent the command:

uls 1 1 %s%

and when I run it, it toggles the led bulb off and on so MAMEHooker can see the hardware and send commands for it to receive. I just don't know why just loading MH and running MAME does nothing.

[Curtishart001]

Welp, got it working. Not entirely sure what happened, but I *think* it's a combination of a cold reboot, using 32-bit MAME (ver 0.169) since it seems the MAMEHooker is 32 bits as well.

1 step down, now on to hardware.