I did a fresh installation on a Windows 8 laptop and at first startup I got an error:
openmsx -bash -romtype
failed (with something like: bad parameter).
Catapult worked, but the ROM type list was empty. However, after restarting Catapult, everythign worked fine... That's odd!
Perhaps Catapult uses the openMSX path configuration parameter without having it set at that point?
AH, yeah, that must be it...
wxString cmd;
ConfigurationData::instance().GetParameter(ConfigurationData::CD_EXECPATH, cmd);
I guess the configuration data isn't filled in at that point, because the dialog is even open that asks the user to fill it in
wouterv, can you fix that while I'm on holiday, please?
I did a fresh installation on a Windows 8 laptop and at first startup I got an error: openmsx -bash -romtype failed (with something like: bad parameter).
Catapult worked, but the ROM type list was empty. However, after restarting Catapult, everythign worked fine... That's odd!