Dingoo A320 forum

@Hellsing1: Dingux crashes? Does that happen for any MSX model and game or only for some? Any other actions needed to reproduce? Do you run openMSX from some kind of menu or from /usr/local/sbin/main?
I haven't had any OS crashes myself, only filesystem corruption once in a while but that's a known issue of the current Dingux releases.

I'll take a look at the Spectrum emu's virtual keyboard.

X just happens to be space under Dingux and openMSX doesn't remap it yet. If it were only about labels, I think A would be the best choice (space and joystick button A typically have the same function), but it's so close to the side of the case that's it not a good place to rest your thumb on. B is a good choice and it's consistent with the European PSX mapping.

@Reo: We have a big game database included already (see softwaredb.xml), we could add something there. But I'd prefer to have categories and a reasonable default so we don't have to add info separately for every single game.

This is the way it runs from start:

Executable = "./openmsx-start.sh"
WorkDir = "/usr/local/emulators/openmsx"

It returns to the main menu then freezes and there's a flashing cursor at the top the the screen.

Also it should remember the roms directory when you have accessed the first game - as Picodrive does.

Which menu is that exactly? I don't have any installed yet.

I think the "openvt" might be the problem: it's possible the menu returns just fine but is running on a virtual terminal that is not visible. Can you try playing with "chvt" when logged in with telnet? ("chvt 1", "chvt 2" etc)

It should remember the ROMs directory: it is saved in /usr/local/home/.openMSX/share/settings.xml, under the "osd_rom_path" key. Can you have a look whether that file was created and if so, whether the key exists and if so, what its value is?

Hi,

Ooops - does remember the rom directory.

It crashes on the dmenu, the main screen where you select the emus/games/music etc.