Yup....seems to be working and Scrape is running as we speak. I read some other threads and it appears most do not shut the pi down; is that true? Any concerns with heat or with having the Ethernet left connected?

@BenWlson it's actually not in the experimental menu: it's in raspi-tools:

https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#where-did-the-desktop-go

I find the default.cfg

tried to edit but was full of strange symbols, so i deleted it, and now all works fine.

Thany you all guys !:)

Looks like that did it, hilarious because I could have sworn I didn't do that before and it worked. Rookie mistake thanks a ton!

That sux. Its not that big of a deal really. Could be worse I guess ,like you said.
Edit: Did a clean install and did not install the touchscreen drivers. Problem solved

@senkun

Yes, i am using wifi. And it seems so, that if it finds the network at First try, everything is fine exept the emulationstation cutting the video.

And i Have allready disabled the USB ROM service, and it only got rid one of the initial two identical fail errors.

And i Will try that delay sequence. Is the value in seconds?

Is editing the fstab the only way to get RetroPie to mount a USB drive then?

@wetriner said in Use of external hard-drives (exFAT) for SAMBA share and rom-storage?:

In smb.conf in /etc/samba, there's a section at the bottom with all your shared directories. For example:

[configs] comment = configs path = "/opt/retropie/configs" writeable = yes guest ok = yes create mask = 0644 directory mask = 0755 force user = pi

All you should really have to do is follow this as a template and change the path, comment, and name. Your usb external hard drive probably gets mounted to /media/usb, although there's probably a by-id directory that you could use in case of wanting to distinguish between two or more drives.

You can store roms on it of course. The question would be really how you would want to implement the ability to use them. You could mount your usb drive straight into your roms directory, so it would just override everything on the sd if plugged in. You could also create a symbolic link to a subdirectory in each of your rom folders, so your hard drive roms would show up as a directory within each system's gamelist. Or you could make a copy of each of the systems you want in es_systems.cfg and have those point to something like /media/usb/snes.

so the exFAT format isn't problematic after all?

@MaroonOut09 well yes that too

@BuZz thank you sir!!! Ok, so now, SOME of the Atari games are working, 2 Genesis games load but the controller does nothing once it's on the actual game. As far as the Atari, I'm wondering if I just got some bad roms? As for the Genesis, Master System, and NES, I'm still at a loss.

@senkun said in File boots back to emulationstation, what gives?:

@Moco said in File boots back to emulationstation, what gives?:

This only effects certain files but when I click on it, it goes to a black screen and then back to the emulation station file list. Any way to fix this?

Eh? Nothing gives and nothing to fix here. When this happens it just means either (most likely) an incompatible file, or a corrupt file. So the fix would be first to try another emulator, or to get a working file.

Thank You! Getting a new file worked!

I'd thought cover art might be copyright, but would screenshot images? It's a little murky but a names only list for FBA, MAME, etc would be really useful as a starting point at least.

I expect I'll likely just have to do things the long way, going through each each game, tidying those that don't get anything from the scraper.

Mrdo now runs after a install using either the latest binary or source.

Myhero still crashes.

Listening for input, updating variables, other things... It may still render the screen even when "idle" too. 5% is pretty idle anyway.

I'm not actually that familiar with the ES code base.

Oh aren't I the stupid one.

Completely misunderstanding what 'hardcoded' means in terms of controls.

Guess I just have to wait until they're unhardcoded...