@why Please format your posts when posting logs / configs

https://retropie.org.uk/forum/topic/3/read-this-first

I guess the question is then that if I have modified or copied files to locations such as /opt/retropie/emulators/retroarch/shader (which isn't a path that a Samba share can see and is located on the USB HDD not the SD Card) how do I make sure this is all backed up aswell??

I'm probably wrong as I am a Linux moron but I thought that when I followed the instructions here https://github.com/RetroPie/RetroPie-Setup/wiki/Running-ROMs-from-a-USB-drive that it placed a lot of configuration settings on the USB HDD that can't be copied with the Samba share??

For example, I know I have made changes to files such as /etc/emulationstation/es_systems.cfg which I assume are now located on the USB HDD but I cannot see these files through the Samba share. How do I backup files such as this??

@ruxton_bruce Yes, that works too, but it can come up again in another libretro core (like lr-fba-next) and you would have to add it to that config too. I was suggesting it for ALL.

@Belum

I was just about to recommend checking to see if your Raspberry Pi was located atop an ancient Indian burial ground, but I couldn't remember if you're supposed to walk toward or away from the light to troubleshoot that problem.

@Riverstorm thanks i'll take a look

Something like this:
http://alexba.in/blog/2013/01/06/setting-up-lirc-on-the-raspberrypi/

There are alot of tutorials on how to set lirc with an infrared remote in a linux system, you just have to google it.

Mine works perfectly fine. Only keyboard i own besides my very mini bluetooth one.

@meleu Hello:

Yes I agree. The temptation to do a script update is so alluring though!

I got the desktop version of RetroPie re-installed and working just fine. I think I will steer away from clicking the update scripts options for awhile.

Thanks again,
BC

@dankcushions said in Some FBA roms not working in latest build of Retropie/LR-FBA-next?:

fba-next recently got updated to a new set, with a new neogeo.zip, which might explain your problem.

@dankcushions and @Floob you nailed it. I actually had a hunch that it might be my neogeo.zip. I had all the right files in the neogeo.zip, but I found a complete FBA .2.97.38 romset (I previously just downloaded some FBA roms from website, still the correct version though), and looked at it's neogeo.zip.

When I placed that neogeo.zip file on the pi3, everything worked! Problem solved. I drilled down even further through trial and error, and found the bad file in my old neogeo.zip was "sm1.sm1". If I replaced it from the new neogeo.zip, that solved it as well. So frustrating, but I figured, as did @dankcushions and @Floob, that it had to be something with the neogeo bios....

Thanks guys, truly appreciate the help!

I ended up flashing the image (for the 3rd time) and ordering some new controllers and no issues now

I would aslo check to see what the buttons are programmed for say button "a" is connected to the "t" key on a keyboard, retropie wont do anything because it thinks you are pressing "t" instead of the key that is programmed of retropie

@Floob said in Mame easiest way ?:

If it doesnt violate the rules here, it should be fine.
https://retropie.org.uk/forum/topic/2/forum-rules

Sorry I did read through it which covers for lack of a better word "code" in the form of files. I guess my more direct question is the supplemental material connected to MAME such as pictures of actual arcade material and sound samples would they be considered in violation such as Progetto or Mr. Do, several good Italian ones, etc. A few times I didn't link to them as I wasn't sure if this type of material is ok?

Well gParted is a Live Linux system :)

So part 1 is as I wrote - Resize Partition (maybe 0,5 Gigabyte)
On the gparted system you can also try to use the fdisk -l command... That should also work.
So you can also use Linux Reader for Windows and then create a 100% fitting image without chunk size calculation :)

Nothing is easy :)

You could see if its responding to jstest

Thanks for the help everyone.

The issue for me configuring my controllers came down to an edit I made to the following config file, a while back on an earlier version of RetroPie when trying to find a way to enable multiple players:
/opt/retropie/configs/all/autoconf.cfg

I had changed the following value to 4:
reicast_input

This change broke my controller auto config as the only options are 0 or 1 - which I now know is for enabling input auto configuration.

@EdwardMurphy said in N64-Controller, D-Pad & Analogue Stick recognized as the same:

I already bought two other controllers.

Always an elegant solution. Glad things are working now.

@MancunianLee Yeah, that's how you do it, but I recommend keeping a spreadsheet or some notes about what ROMs came from where. For instance, I have a list of the games I have loaded in Arcade, and I list the ROM set version they came from and the emulator I am using to launch them.

With all of your ROM files sitting in Arcade, you need to go through them one by one with the runcommand and pick which emu you want to use to launch each game. You can pick a default to cover most of them, but those that vary from your chosen default will need to be set once using runcommand.

I find it very handy to have the Arcade group, especially for friends that want to play, but have no idea what it means to run FBA for NeoGeo games for example. All they need to know is that they are launching the Arcade version of a game and it's not important to the player what emulator happens to run it best. You set all of that up for them.

@cyperghost said in Can my usb device have data on it already?:

Can we pin this post? Or add the symlinking inkl. bash to the wiki?
The info in this thread seems to be very valueable.

personally i'd prefer we only have one method of mounting USB drives in the wiki so less to support. no point having two if they both achieve the same thing.