openMSX can't find ROM

Expert (114)

21-05-2014, 15:36

Hi, when I start openMSX like this:
$ openmsx -machine Philips_VG_8235
It replies:
Fatal error: Error in "Philips_VG_8235" machine: Couldn't find ROM file for "Memory Mapped FDC ROM" roms/vg8235_disk.rom.
However, the "missing" file is inside the directory mentioned and has the same rights and owner as the openMSX process.

diederick@zaphod:~/.openMSX/share/machines/Philips_VG_8235/ $ ls -l roms/
totaal 84
-rw-r--r-- 1 diederick users   184 10 apr  2010 SHA1SUMS
-rw-r--r-- 1 diederick users 32768 10 apr  2010 vg8235_basic-bios2.rom
-rw-r--r-- 1 diederick users 32768 10 apr  2010 vg8235_disk.rom
-rw-r--r-- 1 diederick users 16384 10 apr  2010 vg8235_msx2sub.rom

hardwareconfig.xml:


 
        
          false
          1
          
            roms/vg8235_disk.rom
            1bf0696816b242081e1041a16e5ff73710792865
          
          
	  Philips

This problem seems to have started with openMSX 0.10.1. Am I doing something wrong or is this a bug?

By Manuel

Ascended (19227)

21-05-2014, 16:28

openMSX finds ROMs in 2 ways.
1) the preferred way: it finds the ROM by sha1sum and looks for it in share/systemroms Check if the ROM indeed has the sha1sum 1bf0696816b242081e1041a16e5ff73710792865
2) the old way, only interesting for ROM developers: look up by filename, overriding the sha1sum. For this, put the ROM in the location and with the name as specified in the XML file, in this case roms/vg8235_disk.rom relative to the XML file. The XML file is in share/machines now, not in its own subdirectory anymore. Looks like you used this method, but this breaks with the change of moving machine configs out of their own subdirectory.

My advice: put all these systemroms in ~/.openMSX/share/systemroms and never think about it again. (This is already the recommended method for over 5 years...)

I do wonder why you have machine configurations in ~/.openMSX/share/machines; they should be installed somewhere else (on system level) by your distro or by make install. Unless you want changed machine configurations, you don't need to copy them there.

By diederick76

Expert (114)

22-05-2014, 20:18

It is entirely possible my setup is at least five years old. Odd though, how what worked perfectly in 1.10.0 doesn't work anymore a minor version later.

Still, I looked into /usr/share/openmsx/ and found the sha1sum differ from mine, so I created a new setup according to the documentation and now it works again.

Thanks!

BTW
1. It seems the xml fragment in my first post in this thread isn't rendered correctly.
2. Should I mark this post as solved? If so, how?

By Manuel

Ascended (19227)

22-05-2014, 22:03

Hmm, good point, this was already changed in 0.10.0. I have no idea how it could ever have worked with 0.10.0. Are you 100% sure it did? Perhaps you only ran it with 0.9.1 (and earlier) and never with 0.10.0?

Note that share/systemroms can also be in your homedir, in ~/.openMSX/share/systemroms. No need for root permissions to put the roms there.

The new 'setup' you talk about; it's just putting the systemroms in one of the share/systemroms places, right? If you are looking for the correct roms, a zip file here might be interesting: http://www.msxarchive.nl/pub/msx/emulator/openMSX/

By diederick76

Expert (114)

23-05-2014, 11:19

Hm, maybe not 100%. I just used my old setup for a long while, and if something works I usually don't look back to the documentation.

So that's probably why I didn't even know about the default xml files in /usr/share/openmsx/ . So even though the sha1sum in my own xml was correct, it didn't look for that disk rom, but the default one, which explains why it couldn't find it.

To be clear, in the new setup I talked about I use those defaults, but use ~./openMSX/share/ for overrides, which appears to work. My real VG-8235 has 1024 KB RAM, so that's what I put in ~./openMSX/share/machines/Philips_VG_8235. I'm not sure where I got that disk ROM, but as far as aI can tell it works like the real one, so I added its sha1sum as well. And that works.

And thanks for the link!

By Manuel

Ascended (19227)

23-05-2014, 11:26

OK, what you did is exactly how it was intended. Use global stuff and override in your user dir.

By Paulo Volkova

Expert (104)

22-06-2014, 07:38

Manuel.

After update "openmsx-0.10.2-155-ge6086f1-windows-vc-x86-bin-msi" and run "Test MSX Hardware", the window "Not working hardware" displays the following message:

machine: Daewoo_CPC-51_Zemmix_V
extension: Casio_KB-10
extension: Casio_KB-7

These machine/extensions are new in openMSX. Where can I find the roms "cpc-51_basic-bios.rom", Casio KB-7 and KB-10?
Thanks.

By CX5Mer

Champion (327)

08-10-2014, 18:09

This sounds quite like the problems I'm having using openmsx 0.10.0 on my Raspberry Pi! See the topic about this.

By Manuel

Ascended (19227)

08-10-2014, 19:29

SO, we continue the discussion there. It's not the same problem, because Paulo here can run many other machines and was just missing a few system ROMs of newly added machines.

By Paulo Volkova

Expert (104)

29-05-2015, 06:24

Manuel.

Where can I find the rom with the file name "DA1024D0365R.rom" (Panasonic FS-A1F)?
I can't find this rom nowhere with the same sha1 hash. Any ideia?
Thanks.

By Manuel

Ascended (19227)

26-06-2015, 21:39

There might be an interesting zip file on http://www.msxarchive.nl/pub/msx/emulator/openMSX/