Where did you put the file? The path is relative to the XML file.
I placed the ROM in the systemroms folder, with the rest of the others.
Ok, I confirm that if I add the ../systemroms/ path to the filename, it works fine. Thanks for the tip!
But that's a bit counterintuitive, since none of the filenames of the existing XML files have pathnames, and it would suggest that the XML folder should be populated with ROMs instead of the specific systemroms folder.
To avoid confusion, maybe the ../systemroms/ path should be added all filenames on the bundled XML files then?
It has always been like that. These filenames are there only for reference. I just confirmed locally here that the feature works as it has always worked.
Just checked too. It works when removing the filename and leaving only the sha1 field, indeed. I thought the sha1 it was there to check for the integrity rather than finding the ROMs. Well, something new that I learned about openMSX
It has always been like that. These filenames are there only for reference. I just confirmed locally here that the feature works as it has always worked.
But could the "../systemroms/" be added to the default reference filenames? This way it will make the it more intuitive for those who need to edit the XML files.
It has always been like that. These filenames are there only for reference. I just confirmed locally here that the feature works as it has always worked.
But could the "../systemroms/" be added to the default reference filenames? This way it will make the it more intuitive for those who need to edit the XML files.
I'm not sure I like it. It's only for rare special cases like yours that you want to have it adjustable anyway. And then you can easily adjust the path if necessary.
Putting it on ../systemroms/ suggests to add ROMs to the system installation path. Also not the best idea in all cases IMHO.
About the layout: we had the name '50on' in the past, I think. But for some reason I have to look up we renamed it to ansi. I think this was still in the atarulum era.
EDIT: I do see we renamed it from ANSI to 50on in 2004... but somehow it got renamed back. Will find where and how that happened.
I don't konw if is really a bug but at least I've seen that Open MSX has problems managing ".CAS" Files. I mean...
If I use a ".CAS" File with OpenMSX and for example I type a BASIC list and I try to save it in the ".CAS" it doesn't work. An error message that "the end of the tape has been reached" appears and I can't save anything in this ".CAS" file. But all of this works fine in other Emulators (for example Blue MSX)
And another doubt I have: is it possible to create a ".CAS" File empty?
Saving to .cas files is not supported in openMSX (and also can't work in general). Saving to .wav is fully supported.
For more details see this section in the manual.
Ok. I had seen that I can save to a ".wav". But it seems strange to me that I can't do the same ina ".cas" File.
Have you thought about the possibilit of doing that in your next release? I supposse it should'nt be too much complicated because as I've previously mentioned in Blue MSX works fine. ;-)
