ROM loading from outside root broken on ctr (3DS).

[vaguerant]

755a39a back in January 2019 broke ROM loading universally on the ctr (3DS) platform, including in the subsequent stable releases, 1.7.6 and 1.7.7. Attempting to load any ROMs at all results in errors that the ROMs were not found and the UI dropping back to "No items", unless the user places their ROMs in the 3DS SD card root--in which case everything works fine.

This same issue appears to affect MAME2003-Plus as well, but I went back to the earliest stable which included Plus on 3DS and it behaved the same as all versions have for me, so I'm not sure if that core ever had a known good commit to even work from to find the cause. I didn't bother bisecting the Plus version for this reason.

[markwkidd]

What about other cores? Have you tried anything other than MAME 2003 and Plus?

On Sat, Jun 8, 2019 at 6:47 AM vaguerant notifications@github.com wrote:

755a39a https://github.com/libretro/mame2003-libretro/commit/755a39a243f305cf689c87c973a35034b6f5c0fe back in January 2019 broke ROM loading universally on the ctr (3DS) platform, including in the subsequent stable releases, 1.7.6 and 1.7.7. Attempting to load any ROMs at all results in errors that the ROMs were not found and the UI dropping back to "No items", unless the user places their ROMs in the 3DS SD card root--in which case everything works fine.

This same issue appears to affect MAME2003-Plus as well, but I went back to the earliest stable which included Plus on 3DS and it behaved the same as all versions have for me, so I'm not sure if that core ever had a known good commit to even work from to find the cause. I didn't bother bisecting the Plus version for this reason.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/libretro/mame2003-libretro/issues/442?email_source=notifications&email_token=AEVGC5VNNI4CH3CGSYALCR3PZOL3ZA5CNFSM4HWHCTIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GYMHEVA, or mute the thread https://github.com/notifications/unsubscribe-auth/AEVGC5SZOAR37QSKLUYJXZ3PZOL3ZANCNFSM4HWHCTIA .

-- Mark W. Kidd http://facebook.com/markwkidd (606)536-0115

[vaguerant]

Everything else is fine, including other arcade cores like fbalpha2012 and MAME2000 (using their relevant romsets, obviously). This issue has apparently been known for a while on unofficial discussion boards like GBATemp, but nobody seems to have reported it before now.

EDIT: Here is a link to a GBATemp discussion about this issue beginning on April 16 in case anything reported there is useful in resolving the bug. Note that I consider at least some of the information in that thread unreliable.

• a user attempting to help responds that RetroArch on 3DS does not support compressed ROMs, but this is untrue in mine and other users' experience.
• a different user replies that the MAME2003 build from 1.7.5 stable (the most recent stable which predates the offending commit) works fine, which is true. The original reporter states that that version still doesn't work for them--personally, I suspect the original reporter actually tested MAME2003-Plus, which has exhibited this behavior since release on 3DS and would not be fixed by rolling back to 1.7.5 stable.

[mahoneyt944]

Backported fix from 2003plus

[mahoneyt944]

This has been officially fixed if there's any issues please start a new issue. Game on!