Hello,

thanks to all of you.

Now I nderstand that I dont need to edit emulator.cfg, just lanch runcommand.

Thanks

Francesco

@adambegood Thank you i did think it might be that. Thanks for your reply

@mitu Ok I will have a look on that. Thank you

@kay-Row Create an account - where ?

@sergioggo96 said in Pegasus Frontend scraping issue:

But once i boot pegasus with this theme Switch OS it doesnt appear anything. Any suggestion?

I'm not familiar with Pegasus and its themes, but are you sure you've run the 'generate' gamelist step in Skyscraper, after it downloaded the artwork for your games/roms ?

@Clyde said in Adding roms directly:

@UberLumby said in Adding roms directly:

@UberLumby never mind lubuntu is giving me permission denied when copying files to the retropie sd LOL

Linux distinguishes users by their user id (uid). If your uid on Lubuntu is different than that of pi on RetroPie (normally 1000), you won't have write access to it even if the username on both systems is the same, e.g. you made a pi user on Lubuntu just for that.

Vice versa, you would have full access if the usernames are different but the uids are equal, say "pi" on RetroPie and "lubuntu" on Lubuntu both had the uid 1000 on their systems.

You can see the uids and gid (group ids) of files and directories with the -n ("numeric ids") option of ls:

$ ls -n drwxr-xr-x 6 1000 1000 4096 Apr 28 02:38 RetroPie drwxr-xr-x 7 1000 1000 4096 Sep 19 19:01 RetroPie-Setup

If your uid and gid differ on RetroPie and Lubuntu, you could change the ownership of the directories only temporarily, and change them back after working with the files:

sudo chown -R lubuntu /media/lubuntu/retropie/home/pi/retropie/roms/dreamcast # use your username or uid for "lubuntu" here. # Do your stuff. sudo chown -R 1000 /media/lubuntu/retropie/home/pi/retropie/roms/dreamcast # Provided that pi's uid is 1000 on RetroPie

To me this is more "elegant" than the chmod way, as it doesn't mess with the files permissions. But this may be mere preference. And as with chmod, be sure to not to use it globally as it can mess up thinks equally bad. Use it only on directories where all files and subdirs have the same uid from the start.

Okay noted thanks! My rom folder IS gonna be okay I hope hahaha

@XEntombmentX Make sure you understand what that entails - you'll have to maintain the custom configuration manually. Each time a new system is added (you install a new emulator) you'll have to manually copy the new system entries from the system config to the custom one.

@XEntombmentX Ah shucks that happened to me the first time too.
For future reference, when done transferring files, right click the disk in the manager and select "Flush Cache to Disk" and then it's ok to remove the drive.
I should have mentioned that.

Glad it solved your initial problem.

@YFZdude So I was able to get SSelph's scraper to work, but after a while, it started giving me "hash not found" errors and a "panic: runtime error". I've been searching for solutions for this, but I've found next to no information on the issue and the github page doesn't seem to be active. I'm gonna try Skraper and see if that gives me better results.

Thanks very much! I didn't find that in the docs but I appreciate your link.

@supppp please read the pinned support topics and open a new topic providing the details requested.

Addendum: You could (re-)compress the uncompressed .cue and .bin pairs (or multiples) to the CHD format with will often shrink them up to around 50% of their former size and put them into just one file you can drop into your roms/psx directory. In my experience, those CHDs will run in 80-90% of the cases.

This one-liner will do that with all cue files and their corresponding bin files in the current directory.

for i in *.cue; do chdman createcd -i "$i" -o "${i%%.*}.chd"; done

Important: This will cut off the filenames after the first dot for the output CHD filenames. Remove one % from "${i%%.*}.chd to cut only the last extension for compatibility with filenames with multiple dots.

Beware though that this will only work with single-disk games. For storing multiple disks in one container you'll need the PBP format, which is also supported by Retropie's PSX emulators.

That said, be sure to check https://retropie.org.uk/docs/Playstation-1/ to see which emulators support CHD if you want to go that road.

@Brandon12345678 It works now. Thanks for your help.

I was instructed in one of the threads on here to make an alias to the folder on the usb drive containing the roms and just replace the folder in the retropie roms folder with the same named alias. That also works. One thing that I like about that is I could at any time just delete the alias and replace with a folder to return it to reading off the sd card, or you could have part of a folder on the usb and part on the sd (if you don’t mind having two subfolders in ES).

@danyo
Got it running. Thanks!

If your roms are already on a Linux/unix/mac, you can use these scrips: https://gist.github.com/ReallyVasiliy/32c33be595408d353e37999ce305ea4d

You need to save each file on the target system, and give them execute permissions (in the terminal, run “chmod a+x move”).

move: moves the roms specified in the file <arg1>, which are contained in directory <arg2>, to a new directory <arg2>/<arg1>. An example terminal command could be:
$ move somewhere/Clones.txt /userdata/roms/fbneo
Will move files specified in Clones.txt from /userdata/roms/fbneo to /userdata/roms/fbneo/Clones

The remove script has the same arguments but simply deletes them permanently instead of moving.

@MartyH1988

First try to follow all these steps (all of them from the top!):
https://retropie.org.uk/docs/Wifi/

Then to transfer roms over the network follow these steps:
https://retropie.org.uk/docs/Transferring-Roms/#samba-shares

Make sure you place the roms in the right folders! Read the documentation. For example for the SNES:
https://retropie.org.uk/docs/Super-Nintendo-Entertainment-System/#roms

If you cant find the network share, perhaps try this way of accessing your pi through SFTP.
https://retropie.org.uk/docs/Transferring-Roms/#sftp

I've been unable to connect to the network share on my pi. For me it turned out I'm having a problem that windows 10 had certain group policies disabled that blocked the share. The fix was explained here. Though, I didnt like the idea of leaving insecure policies open, so I decided to transfer roms with SFTP. Or alternatively, using an old windows 7 laptop, which could access the share.

@mitu Hi, that's great info thanks. I presume that if it isn't writable, then pastern.com will allow me to change it?

The weird thing is that it was working so well, and then for no reason it stopped. Also, it is allowing me to do the first edit (ie try another emulator) and seems to write it to the config file, but then won't let me further edit it. Its the same in every emulator - PS1, SNES etc. Got me confused!

Will try what you suggest tho. Thanks again, appreciate it.

Glyn

There's also an easy way to transfer your ROMs automatically from an FAT32 or exFAT formatted USB stick. I don't know if NTFS will work with this, too.