Cannot run SD Snatcher, MSX2 [SOLVED]

[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!

[Folly]

@Zering
Others work fine. Perhaps they just don't work then.

[Zering]

.2d files was it? I'll see if I have any.

Edit : Just loaded 177.2d
It's running. Maybe one of your bios is wrong?

[Folly]

@Zering
Will have look at it tomorrow.
Indeed i saw 2 different turbo files.
Thanks.

[Folly]

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

@Zering
Will have look at it tomorrow.
Indeed i saw 2 different turbo files. (Sharp x1 discussion)

Well , doesn't work. will try something else later on.

@Zering in [Cannot run SD Snatcher, MSX2 [SOLVED]]
Should we maybe see about bringing the issue to the attention of the core developers? (SD Snatcher discussion)

Seems these issues are already submitted :
specific:
https://github.com/libretro/blueMSX-libretro/issues/92
general:
https://github.com/libretro/blueMSX-libretro/issues

[Zering]

@Folly Is that core still maintained?

[Folly]

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

@Folly Is that core still maintained?

@Zering
Indeed it seems a long time ago.

But a few moths ago the libretro cores were wiped from github.
So they restored old backups.
Everything is behind now.

Last commit was from 2 april 2020. So it's still maintained.