2011-01-24, 21:52
Thanks for your reply!
Well, I even don't have to pass the %rom% data as the game itself is loaded via dosbox.conf autoexec section (I need some mapping and univbe running before the game itself).
So you can say dosbox.conf in this case is somehow like a batch file that's being loaded by dosbox. The only problem is that the appended dosbox.conf doesn't work when the conf is a rom entry - it only works when hardcoded into launcher argument. This is what really surprises me because I'd think the output (or: what DOSBOX sees) would be exactly the same.
Maybe you could do a short investigation if there's anything that can be done on ALA to solve this - DOSBOX games are going to need at least different gamepad/keyboard mappings per game so it'd be great if it would work without any workarounds. If it isn't possible it's no big problem though as it can be done with scripts too.
Well, I even don't have to pass the %rom% data as the game itself is loaded via dosbox.conf autoexec section (I need some mapping and univbe running before the game itself).
So you can say dosbox.conf in this case is somehow like a batch file that's being loaded by dosbox. The only problem is that the appended dosbox.conf doesn't work when the conf is a rom entry - it only works when hardcoded into launcher argument. This is what really surprises me because I'd think the output (or: what DOSBOX sees) would be exactly the same.
Maybe you could do a short investigation if there's anything that can be done on ALA to solve this - DOSBOX games are going to need at least different gamepad/keyboard mappings per game so it'd be great if it would work without any workarounds. If it isn't possible it's no big problem though as it can be done with scripts too.