segascream

Holy crap! I can't believe i missed that!! Thank you so much!

Yes, that's it exactly! It seemed a hell of a lot easier to write a batch script to do this rather than go through and assoxiate JoyToKey to 600+ roms. So, this was just the test script I wrote. Testing it on my NES emu: my plan was to write the script, test it, and then adapt it for all my other emus once i was satisfied. If you could give me some idea of where I'm going wrong, I would greatly appreciate it. Thanks. EDIT: I should probably also mention that I've got JoyToKey in every single emulator and PC game directory, so that i never have to mess with trying to make sure the correct profile is being used.

I started using Launchbox a few months ago, and I love it. However, I've run into a bit of a problem (actually, a chain of problems that I finally ran out of solutions for). I've been using Launchbox for both my emulators and PC games, and I've been using JoyToKey for all my PC games. I had my emulators configured for my 2 bluetooth gamepads, but for some reason they occasionally get confused on Win7. (They'll sometimes appear in emulator input configs as Joy0 and Joy1, but sometimes Joy1 and Joy2, and then last week they both randomly decided to identify as Joy255.) Anyway, it appears I don't tend to run into those issues in JoyToKey, so I wrote a batch script to, when I click on a given ROM in Launchbox, have it fire up the appropriate emulator and JoyToKey with the correct profile loaded. It all works great, except.... I can't seem to figure out how to get this batch file to pass the selected ROM to the emulator. I'll click on a game, it'll open the emu and JoyToKey, but it doesn't actually load the game info the emu. Can anybody give me some clue as to what I'm missing? Thanks