Configuring openMSX on a Rasbperry Pi with Sedai Linux

Por galaxy frog8

Supporter (2)

imagem de galaxy frog8

01-10-2021, 05:01

I've been impressed with how smooth this seems to run for other people, but I am stuck on what is probably a simple step...

I cannot figure out how to move my machine ROMS (which are in a folder in USB0) to the correct directory ('Hardware' in the main menu). I want to be able to change my Machine and eventually add other drives and cartridges. I suspect I might be doing this entirely wrong, because I see that selecting 'Load ROM... (slot A)' opens toUSB0 just fine. How can I do the same for the hardware machine ROMS?

Entrar ou registrar-se para comentar

Por Manuel

Ascended (18252)

imagem de Manuel

02-10-2021, 00:27

I don't know how things are typically supposed to be configured on Sedai. But I can tell you the following things:
1. You cannot move ROMs (i.e. ROM files) from inside the openMSX menu.
2. Load ROM is not about moving ROMs, it's the virtual/emulated way of inserting a ROM cartridge in the cartridge slot, by means of selecting a ROM file.
3. In openMSX, machines are not identified by the ROMs, but the other way around: machines are specified and they will need certain ROMs, as specified in their configuration. So in order to run other machines, their ROMs must be findable by openMSX. On a desktop system, you put these ROMs in the share/systemroms folder (see http://openmsx.org/manual/setup.html#romlocation), but as I said before, I'm not sure what the author of Sedai had in mind for this, as it's also possible to change the location on where openMSX looks for these system ROM files.

Having that said, please follow the advice of a Sedai expert :)

Por galaxy frog8

Supporter (2)

imagem de galaxy frog8

02-10-2021, 00:49

I figured out what was going wrong. The files need to be copied from the correct directory in the command prompt of Sedai Linux, however I was never able to access the command prompt. Either the current version of Sedai Linux has an issue or I was dong something else wrong; the 0.FAT file inside the .img file downloaded from Sedai Linux website was not creating the necessary partitions on the boot drive when it is flashed/imaged. I was unable to access the command prompt. Pressing F1 after boot would result in a black screen, and I believe this partition issue is why.

If this happens to anyone else, what you can try is flashing the latest Raspberry pi OS onto a drive, booting it, then turning it off. Then flash Sedai Linux on the main partition. Alternatively just create the partition yourself via disk management. I was able to go to the command prompt and move the files from my usb to the boot drive!

Por Manuel

Ascended (18252)

imagem de Manuel

02-10-2021, 09:34

Great, enjoy! Also, any reason you are not using the latest release 17.0?