gblauncher.exe
GBLauncher.exe
GBLauncher.exe runs games from a GameBase database via command line. It uses the specified GameBase database's GEMUS setup, ensuring that the games are loaded/run in the emulators the same way they are when launched through the GameBase frontend. This includes any unpacking/repacking of archives.
Usage
GBLauncher.exe db=name [id=gameid|fn=gamefilename] [emu=index] [wait=1]
Command Line Arguments
| Argument | Description | Examples |
|---|---|---|
| db=name | Required. [name] is the name of GameBase database containing the game to launch. NOTE: This must be the folder/.mdb name. If it contains spaces then “surround it with quotes”. | db=“GameBase Amiga” |
| id=gameid | Required if 'fn' argument is not specified. [gameid] is the GameBase Game ID of the game to launch. | id=12345 |
| fn=gamefilename | Required if 'id' argument is not specified. [gamefilename] is the GameBase Game Filename of the game to launch. If it contains spaces then “surround it with quotes”. It can be a path-less filename, or can include the relative path (within your defined game paths) that is stored for the game in the GameBase database (with or without the filename extension). GBLauncher will attempt to find the correct game file if an exact filename is not specified. | fn=Cannon_Fodder.adf fn=c\Cannon_Fodder.adf fn=Cannon_Fodder |
| emu=index | Optional. If specified, the corresponding emulator from the database's Emulators.ini file will be used. Defaults to “-1” which is the default emulator as used when you left-click the “Play Game” button in the GameBase frontend. | emu=2 |
| wait=1 | Optional. Causes GBLauncher to wait until the emulator is closed before quitting. Desirable if you are running GBLauncher from another frontend and you want to wait until the emulator is closed before returning to it. | wait=1 |
Example
GBLauncher.exe db="GameBase Amiga" fn=Cannon_Fodder.adf emu=2 wait=1
Notes
- GBLauncher creates the log file GBLauncher.log each time it runs, so if you are having problems getting things to work, check the log file for clues.
- If your GEMUS scripts have any user visible alerts (e.g. QUESTION()s, Show_Message()s, …) then these will still be shown to the user when running from GBLauncher. This might not be desirable if using GBLauncher from (for example) a full-screen app such as an arcade cabinet frontend, in which case you would need to modify the GEMUS script and remove all visible prompts.
See Also
gblauncher.exe.txt · Last modified: 2023/10/04 14:15 by 127.0.0.1