Dimitris Panokostas

I tested WinUAE, by manually configuring it to the same thing we do with the WHDLoad booter:  It fails in the exact same way. This seems to confirm my...

Actually, this fails even with the `.lha` archive extracted first. I think then that this is perhaps an issue with the `.lha` package specifically?

Maybe Pimiga doesn't include the `DEVS:Kickstarts/*` files, and WHDLoad cannot use them, so it skips that step? That would still indicate a problem with those specific slaves I think, however.

The RTB files are _not_ the same as the kickstart files, that WHDLoad uses (if found) to improve the compatibility. In the case of Pimiga, those files are missing, so...

@giantclambake I also suspected the archive handling, which is why I decompressed it and used it as a directory, in the test with WinUAE - still failed the same way.

@giantclambake That's due to the gfx rewrite there, the manual crop settings won't always look correct (Autocrop might do a better job in this case). That being said, the settings...

@sonnenscheinchen Thanks for the find, that seems interesting enough. We have already established that it's not the mounting of the archives which was at fault, since the exact same thing...

Custom values parsing is the next item to fix, so hopefully that will take care of that. The rest (e.g. CPU) can be fixed by updating the XML accordingly.

The `dev` branch has some work-in-progress implementation, but I haven't had time to revisit this lately. The current status is that the virtual keyboard is brought up on the screeen...

This seems to work in the latest version from `master`