Can't load Atomiswave titles

construkt

Forgot to mention... Running pi 4 with retropie 4.6 and hursty's super sweet theme if that is at all relevant.

Krakatoa

How did you configure you es_systems.cfg for atomiswave?

  <system>
    <name>atomiswave</name>
    <fullname>Atomiswave</fullname>
    <path>/home/pi/RetroPie/roms/atomiswave</path>
    <extension>.zip .lst</extension>
    <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ atomiswave %ROM%</command>
    <platform>atomiswave</platform>
    <theme>atomiswave</theme>
  </system>

mitu

The error seems to indicate that file .zip file cannot be opened. Is it a proper zip file ? Can you run

zipinfo -vv /home/pi/RetroPie/roms/atomiswave/dolphin.zip

then post the output.

construkt

@Krakatoa

I just put:

<system>
<name>atomiswave</name>
<fullname>Atomiswave</fullname>
<path>/home/pi/RetroPie/roms/atomiswave</path>
<extension>.cdi .chd .cue .gdi .sh .zip .CDI .CHD .CUE .GDI .SH .ZIP</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS dreamcast %ROM%</command>
<platform>atomiswave</platform>
<theme>atomiswave</theme>
</system>

I copied the dreamcast one and changed the names around. It's what I did for CPS1-3 with fba, so I figured that would work. I don't have .lst files. The contents of the zips are all .bin and .u# files. The original zips I had didn't have the bins either, just the .u#

construkt

@mitu said in Can't load Atomiswave titles:

zipinfo -vv /home/pi/RetroPie/roms/atomiswave/dolphin.zip

Yeah that's what I can't figure out. The zip seems to be fine to my eyes and I've tried multiple versions. Here is the output: https://pastebin.com/Gjg3FSaz

mitu

Yes, the zip looks file; what permissions are set on the file and the parent folder ?

construkt

@mitu

https://pastebin.com/11RmTeUR

I'm not sure how much the pi:root matters rather than pi:pi. I don't really know how to change that. When I used a chmod command to set it to pi:pi it still stayed pi:root.

construkt

Oh, it didn't show my /roms permissions. You can see that here: https://pastebin.com/Ap0uA5gW

mitu

Are you running your ROMs from an USB hdd/stick ? That might explain the permissions issue. The pi user has rights to read/write, though root as group doesn't make sense - should be pi.

construkt

@mitu I'm running roms from my NAS on unraid. Nothing else is having this problem, though.

I just picked up a 3rd party image where I know they work and see what they are doing differently. So far what I have noticed is that they are using .bin and .lst files and for some reason their es_systems.cfg basically has 2 systemLists in it.

mitu

I'm running roms from my NAS on unraid. Nothing else is having this problem, though.

Can you post your mount options ?

I just picked up a 3rd party image where I know they work and see what they are doing differently. So far what I have noticed is that they are using .bin and .lst files and for some reason their es_systems.cfg basically has 2 systemLists in it.

.lst are not recommended by upstream for Naomi/Atomiswave, the supported format is compatible MAME ROMs.

construkt

@mitu my mount options? Like my fstab?

I'm still really new to all of this, I've just been spending so much time on it that I'm actually picking some of it up but a lot of Linux still escapes me, haha.

mitu

@construkt said in Can't load Atomiswave titles:

my mount options? Like my fstab?

If you're using that to remotely mount your ROMs folder from the NAS, then yes.

construkt

@mitu here is my fstab file: https://pastebin.com/YzELhXCn

mitu

You should change the

//192.168.2.101/retropie-mount/home/pi/RetroPie/roms /home/pi/RetroPie/roms cifs guest,uid=1000 0 0

to

//192.168.2.101/retropie-mount/home/pi/RetroPie/roms /home/pi/RetroPie/roms cifs guest,uid=1000,gid=1000,noserverino,nounix 0 0

construkt

@mitu said in Can't load Atomiswave titles:

//192.168.2.101/retropie-mount/home/pi/RetroPie/roms /home/pi/RetroPie/roms cifs guest,uid=1000,gid=1000,noserverino,nounix 0 0

Holy hell, that did it.

Thank you so much for your time. This was killing me. I felt like it was a permissions issue, but I could not for the life of me pin down why this would be an issue but nothing else was causing me trouble.

mitu

It wasn't a permission issue, the noserverino is the option that matters here - that's why it was added to the docs.

construkt

@mitu I did a lot of reading around in those docs, but since I didn't require a user/pass for access I didn't know how much of that I should cut out of the line so I browsed forums until I found an example of someone doing what I was trying to.

Duly noted, though. Just another thing added to all the stuff I've learned about this stuff in the last couple months. After fixing that, Daphne works as well for me. I knew it was going to be some little minute detail. Thanks again, you're a lifesaver.