This is correct.

The 3DO always resets when a disc is inserted. Games therefore expect a saved game in the NVRAM to be there. So set the NVRAM storage to "shared" and just play the game as normal.

The only reason for multi disc support in the emulator is to make the NVRAM shared. Not an useless feature but I've been busy with other things.

(note: I'm the maintainer of Opera)

@Chadmon10 said in Retropie won't boot into a rom, tries, then goes to command line.:

/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ megadrive "/RetroPie/roms/megadrive/Sonic The Hedgehog 2 (World).md"

You forgot the ~ in ~/RetroPie/roms/megadrive/Sonic The Hedgehog 2 (World).md.

@dankcushions Yeah, you are right, that will probably be less and less relevant.

Still good to include instructions in this post as well ;-)

Thanks for your time and for your reply!

@Freddy00 Driver installation with sudo ~/Retropie-Setup/retropie_setup.sh should work. If you want to review the compile log see zless ~/~/RetroPie-Setup/logs/rps_2019-03-15_194311.log.gz when back on commandline (your date and time may vary).

You can type lsmod alone, you should spot the mk_arcade... driver loaded.
(If the command still is not found you should install kmod, but it should be already there, so there should no need to issue sudo apt-get install kmod.

Then, and only then when lsmod shows the module, proceed with https://github.com/recalbox/mk_arcade_joystick_rpi#auto-load-at-startup edit the mk_arcade_joystick.conf and change the map=1 to map=1,2. Save the file, reboot and then you can configure your joysticks with emulationstation.

If you use the retropie_setup.sh method you should succeed. If not please do post the build log as noted above.

PS: I would refrain from following the Github tutorial from A to Z, a) it is tailored towards another Retro-Distro (Recalbox), b) if you get stuck it's hard to help and c) last but not least this is a forum about Retropie-Distro (and not Recalbox).

@mememinister , I am trying to do the same thing but can't get my mapping working manually. Only through the ES menu Configuration Input. Do you do your mapping in es_input.cfg or in retroarch.cfg? My retroarch.cfg gets ignored or at least that is what it seems like. Do you have a little manual how you did the mapping?

@edmaul69 Ah, that was it. I switched it to:

Launch menu joystick control (currently: Disabled)

and now it works.

I can press Start and get into the runcommand menu. Thanks!

@obsidianspider ok i found the issue!!!!!

i had copy/pasted the config line within /etc/udev/rules.d/10-retrogame.rules (i create this manually rather than using the adafruit install script)

was checking the config file and noticed that the config contents looked odd

SUBSYSTEM=="input", ATTRS{name}=="retrogame", ENV{ID_INPUT_KEYBOARD}="1"

at first glance it looked fine, but when i typed another double quote next to the exsisting ones, it looked slightly different!! so i re-typed all the quotes, and everything is fine and dandy again!!! :)

Hum, I edited the retrogame config file and remove all buttons that weren't wired yet, and it seems to work !
I don't understand why it was working when the dtoverlay was off though... But I can go on to another issue now :)

Regards

I just wanted to update this post as I fixed the issue. I had installed the Adafruit-Retrogame manually and forgot to add the rules (see end of this guide https://github.com/adafruit/Adafruit-Retrogame)

now it's working, hope this helps fix similar issues.

@rachuism at first sorry for delayed answer..... If you hash your password then special chars are hexed and your problems may be solved with your WIFI PW.

You can read this thread and follow instructions.
Here the PW is automatically hashed.

You see in the example the passphrease "Secret Key" was hashed to "5bee4223648102a29c09b2b52bbd2fc920c4d90ced9292781477d1bf219b753a"

You can also use this side to generate hashed values..... Be careful! You give your SSID and your PW to a xenos. I tested with the values provided in the thread linked above and the output from wireshark resulted also "5bee4223648102a29c09b2b52bbd2fc920c4d90ced9292781477d1bf219b753a" .... so this works so far!

Knowledge is power!