Cannot run SD Snatcher, MSX2 [SOLVED]

[Folly]

I don't mind but we are drifting away from the topic.

About our topic. Actually it might be the case that the "sdsnatcher" module needs a specific rom. I saw the name "swm.rom". I think i was called that way. SWM could be short for SoftWareModule.
Will try this out when I have the time.

[Zering]

@Folly Maybe we should have an 'Old Japanese Computer Games Appreciation Thread' ^^

That makes sense about bluemsx, so you think what hasn't been integrated are the rooms themselves? That would make sense considering the legality of it.

[Folly]

@Zering said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Folly Maybe we should have an 'Old Japanese Computer Games Appreciation Thread' ^^

That makes sense about bluemsx, so you think what hasn't been integrated are the rooms themselves? That would make sense considering the legality of it.

Good Idea to make a new topic !

Will try these roms if it will help.

[Folly]

@Zering

My R+R worked OOB.
It's an XDF file.

Don't know wat that is.

[Zering]

@Folly Oh. I converted it because the documentation clearly stated lr-px68k only read .dim and .m3u well.
Good to know it works.
I'll write up a thread tonight!

[Folly]

@Zering said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Folly Oh. I converted it because the documentation clearly stated lr-px68k only read .dim and .m3u well.
Good to know it works.
I'll write up a thread tonight!

I run my files directly from the Desktop with my own script. So I am not bounded by extensions. If you run it from emulationstation .xdf is not there in /etc/emulationstation/es_systems.cfg . So you have to add that.

<path>/home/pi/RetroPie/roms/x68000</path>
<extension>.dim .hdf .hdm .2hd .d88 .m3u .DIM .HDF .HDM .2HD .D88 .M3U</extension>

[Zering]

@Folly Adding it will make it appear in ES sure, but how could I check to see that the emulator is capable of using those files?

[Folly]

@Zering said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Folly Adding it will make it appear in ES sure, but how could I check to see that the emulator is capable of using those files?

Well it should run then, i think. :-)

My file contains also a .hdf .hdm. Tried the .hdf, but it seems like it will also load a floppy. not sure how this works.

[Folly]

@Zering

Again, no succes with bluemsx and SCC

[AdamBeGood]

@Zering said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Folly Adding it will make it appear in ES sure, but how could I check to see that the emulator is capable of using those files?

X68000 definitely works in ES with XDF, I thought it might it not but it was fine on mine.

[Zering]

@Folly said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Zering

Again, no succes with bluemsx and SCC

How exactly did you attempt to use the roms?
I assume lr-bluemsx would be looking for those roms in a very particular place.

[Folly]

@Zering said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Folly said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Zering

Again, no succes with bluemsx and SCC

How exactly did you attempt to use the roms?
I assume lr-bluemsx would be looking for those roms in a very particular place.

Placed them in the BIOS directory together with the others.

[Zering]

@Folly I'm assuming that's where bluemsx on your PC looks for those roms?

[Folly]

@Zering
The file I presumed it would be the one, is just an arabic msx type :

$ grep -r "SWP.rom"
MSX2 - Al Alamiah AX-350/config.ini:0 2 2 4 42 "Machines/MSX2 - Al Alamiah AX-350/AX350SWP.rom" ""
MSX2 - Al Alamiah AX-370/config.ini:0 2 2 4 20 "Machines/MSX2 - Al Alamiah AX-370/AX370SWP.rom" ""
MSX2 - Arabic/config.ini:0 2 2 4 42 "Machines/Shared Roms/SWP.rom" ""

It was a nice try/idea. But I don't think it's the solution.

[Zering]

@Folly Should we maybe see about bringing the issue to the attention of the core developers?

[Folly]

@Zering said in Cannot run SD Snatcher, MSX2 [SOLVED]:

@Folly Should we maybe see about bringing the issue to the attention of the core developers?

That would be a good idea.

[Folly]

Sharp X1 is working.
But compilation .2d disks hang in "disk menu", any ideas ?

[Zering]

@Folly I'm not sure what you mean. Could you send a screenshot?

[Folly]

@Zering

[Zering]

@Folly I think I had that once because the lr core looked for the bios in the wrong place.
If it's not then I honestly don't know!