@edmaul69 said in Can't get Wonderswan to work:

@wilsoncqb1911 the advantage of having that one is you can arrange the systems in any order you want. Then when you install a new system, just copy that systems info from the one es_systems.cfg to the other placing it where you want it.

Thanks for the explanation as to the purpose of that file. I read that I could've edited it to include the new systems, but the route of simply deleting it seemed easier than editing it each time I added a new system. I'm not sure I care about the order that the systems are presented, so I likely won't miss the potential utility. Thank you for letting me know what it does.

@capeman, thanks for the encouragement. It's currently hooked up via VGA to an flat panel monitor. Given the age, I'd say maybe it has DVI, but unlikely to have HDMI. My plan was to use the existing cable with VGA to HDMI adapter.

Any thoughts regarding the remote access part?

Yesterday I turned on the RPi without any USB controller plugged in. The arcade controls worked perfectly in ES. I runned a Megadrive game and the arcade controls were recognized as player two. I wasn't able to go back to ES with start-select on the arcade controls. When I plugged in the USB SNES controller I could go back to ES with start-select on that controller.

Any way to "fix" this?

I'll have to wait a few days or so and see how this all works out. The USB adapter is Amazon, so fast, but the SFC controller is eBay, so you know. The seller claims the crack does not in any way affect the controller's actual usage. From the pictures it may be fine as long as it's sufficiently glued (and presumably it already is.) I prefer not to give out my address unless I get downright desperate anyway and the controller was the cheaper part of the two. I do still really thank you for the offer though.

You know, even though I'm going to do that and hopefully solve the problem in a bit of a roundabout non-solving manner, I am still sort of curious about the iBuffalo. Given that a powered USB hub might help one person and that sort of thing, I sort of wonder if it could be more of an issue of something like it actually doesn't use enough power. Maybe the powered hub compensates by being more consistent in handling its lower power usage. It makes me sort of wonder: what would happen if you increased its usage just a bit, maybe getting it closer to 10mA? Perhaps some sort of resistor placed somewhere or something like this? Given that I bought one of these specifically to dedicate to the RPi and they are already modified (I trimmed down the turbo and clear buttons to be less than flush with the casing so they absolutely can't be pressed by accident under any circumstances -- though if I push down with a finger I can still do it if I really want which I likely never will) I sort of wouldn't mind if I had to do something like that, but honestly I have no clue what to really do in that respect.

EDIT: I tested the Saturn-style USB gamepad I had found (hate that 8-way, but it works) and it came up as 2mA idle as well. So I guess it's not power usage since it's the same. I have no clue why the heck the RPi produces this problem and a PC does not.

I got the adapter and SFC gamepad, so I'll be giving them a try on the RPi later. They work great on a PC in an initial test other than the gamepad being pretty old and worn (the d-pad in particular doesn't have the snap to it that it should. I wish I could switch these from the iBuffalo but of course they're quite different on the inside.)

@jacobjub if you use both you need to reinstall both. Otherwise you need to reinstall the one you use. Or just install both to be safe. Or you can copy your config from fba system

0_1500952766821_fea34ccb-a779-4f8a-813a-6cae3208178f-image.png

Hey all,

I was digging around about my issue I posted yesterday, and stumbled upon this. Maybe this could be th eissue on why my MSX roms aren't loading? How did you guys go about fixing your problems?

https://retropie.org.uk/forum/topic/11819/msx-or-msx2-roms-won-t-load-bluemsx

runcommand.log:
bash: /opt/retropie/supplementary/joystick-selection/js-onstart.sh: No such file or directory
Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-bluemsx/bluemsx_libretro.so --config /opt/retropie/configs/msx/retroarch.cfg "/home/pi/RetroPie/roms/msx/Knightmare III - Shalom (J).rom" --appendconfig /dev/shm/retroarch.cfg

@jacobjub as stated above. When you select a game in emulationstation and you get to the blue screen, just wait. It will eventually load. If that was your problem good. From there people can help you with anything else. I personally use lr-vice. I have had no issues with it at all.

I would like to thank each and every one of you who has tried to help me understand the MAME system. It means a lot to me. I have learned a lot and now have MAME working. This wouldn’t have been possible without all of you. Thank you so much!

@simonster said in Separating ROM categories?:

https://retropie.org.uk/docs/EmulationStation/

I've never really seen a full blown tutorial on how to do it .. as there's a few different ways to accomplish it ....some more detailed than others. Most of the time when you see them split out, the person who made the image did alot of reading and tinkering to figure it all out.....

easy method

Let's take "PC ENGINE" and "TurboGrafx-16" as examples. They both use the same emulator .. but let's say you want them in different folders.

First thing is you have to define the TurboGrafx-16 as it's own system within the es_sytems.cfg file.

Here are the two entries in the file you'd have.

<system>
<name>pcengine</name>
<fullname>PC Engine</fullname>
<path>/home/pi/RetroPie/roms/pcengine</path>
<extension>.pce .ccd .cue .zip .PCE .CCD .CUE .ZIP</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS pcengine %ROM%</command>
<platform>pcengine</platform>
<theme>pcengine</theme>
</system>
<system>
<name>tg16</name>
<fullname>TurboGrafx 16</fullname>
<path>~/RetroPie/roms/tg16</path>
<extension>.pce .zip .cue .PCE .ZIP .CUE</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS pcengine %ROM%</command>
<platform>pcengine</platform>
<theme>tg16</theme>
</system>

Notice that they're almost the same....but the TG16 entry has specified a different /roms/tg16 folder. After adding in that extra system XML code, you'd now restart your system. Then, you could put your TurboGrafx-16 roms into that new folder /roms/tg16 and ES would see them as their own system.

(note: you can keep the es_systems.cfg in its original place or in a secondary location - pros and cons to doing each way)

more detailed method

If all you did was #1 method, next time you do an full RetroPie "update all packages" ... there's a good chance your changes in the es_systems.cfg will be overwritten.

A way to keep that from happening is to make a new "emulators" configuration folder just for the TG16 system in /opt/retropie/configs directory.

You could copy the "pcengine" folder and make the new one be something like "tg16".

If you do #2 method, you'd need to update the es_systems.cfg file for the TurboGrafx-16 to "use" this new emulator configuration.

<system>
<name>tg16</name>
<fullname>TurboGrafx 16</fullname>
<path>~/RetroPie/roms/tg16</path>
<extension>.pce .zip .cue .PCE .ZIP .CUE</extension>
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS tg16 %ROM%</command>
<platform>pcengine</platform>
<theme>tg16</theme>
</system>

Notice the <command> line is now different and it tells RetroPie to use the new "tg16" emulator folder instead of the "pcengine" emulator folder.

Method #2 is somewhat more detailed, but doing it this way, your changes in the es_systems.cfg file won't be overwritten. (at least that's been my experience).

There's more detailed ways and changes you can make of course. It just depends on how in-depth you want to tinker with RetroPie. You could split out all of the various MAME categories (Atari Classics, Midway, Classics, Cave, etc) in the same way.

Thanks. I switched out of the OMX player and now it works!

I've had troubles with a couple of cards before appearing corrupt. This is how I fixed it (going from memory here, as I am at work).

On an Ubuntu box, put your card in, and pull up the "disks" utilities (how to get there varies on your Linux interface). Choose your SD card. Delete all the partitions that are on it. Format it as FAT, but don't choose the "quick" option, choose the one that writes all zeros to the drive.

Then, still on your Ubuntu box, use the utility called "etcher" I think (again, going from memory here) to write your Retropie image to the SD card. This utility is slower, but (in my experience) far more reliable than Win32DiskImager.

Last time I did this, the process took over two days. But, it did resurrect a 128GB card from the dead, which is working just fine in my friend's Retropie right now.

Hope this helps someone.

@steptoe I have seen builds of people having their outlets built into their machines but they never really show how it is really done which is what i would like to do with this as well but the thing is i need 2 USB ports on it as well for the Pi and for a 120mm fan i plan on installing and of course one of the plugs i would be using for the monitor.
The other thing is i need something like the first link you showed which i can never really find a proper tutorial on how to set that up cause that is something i plan on doing also.
Oh ya and also my build will be slightly different with the option of the arcade stick being pulled out from the machines because my stick i am still trying to build is a USB one and plan on putting a 4 USB hub in it so it would be easier to hook up other controllers/joysticks.

You could try this tutorial (at own risk): http://www.instructables.com/id/RetroPie-Overclocked-Raspberry-Pi-3-for-Video-Game/

Just thought I'd throw this out there and mark this as resolved. For anyone looking to do what I did which is fully configure your RetroPie, then remove your controller configuration for a clean backup solution (Where you can then restore and configure whatever controller you want as it came Out of the Box) all you have to do is this.

Configure your Raspberry Pi fully (with RetroPie) Make sure all settings are exactly as you'd like with splash screen, themes, core configs, scrapes, roms Delete any save files for the cleanest backups Go to RetroPie > RetroPie Setup > Manage Configurations > EmulationStation > Clear input Configuration Exit to ES, press start on controller and Shutdown System Remove MicroSD card, and insert in computer Create your backup with your favorite backup software, then "Pi shrink" it

Hi meleu - thanks for your reply :-)

Sorry for the the lack of info. I thought it was enough to answer this.

I also thought retropie options were "version based" and not "distro based" or whatever it is called - too many geeks spoil the soup, you might say ;-)

But yes- I forgot the version - it is 4.2.12

Is there, by chance, another way to this - with making kodi quit to retropie afterwards?

@flyingtomahawk

Many thanks, I think i will stop wasting my time and just go with rom set for lr-fbalpha.