Sorry, we don't support 3rd party images or pre-sold 'consoles' . You'll have to ask the vendor/seller for support.

@mindwave

Win32DiskImager is what I use as well to backup my RPi images.

This site has an easy to follow guide: https://howchoo.com/g/nmexndnlmdb/how-to-back-up-a-raspberry-pi-on-windows

@busywait That did it. Thanks!

@mitu Ok, thanks)

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

@chrisw99 said in SD card write cycles:

It was more a generic question about the lifecycle of an SD card if it's in a Pi as there always seems to be stuff being written even when idle.

Things get written to logs when events happen - it's not an issue to cause excessive write tearing. Unless you have a problem which gets logged continuously in the logs (such as under-voltage warnings), the normal operation on a Pi will not negatiely impact the negatively the sdcard lifetime.

You could configure logging to RAM instead of persistent storage (with something like Log4Ram) if you wish.

@mitu

Thank you Mitu

Just thought about it since you mentioned the USB3 methods of storing and backing up roms

Thank you for the tip

@YFZdude

Thank you for advice

Also

Really appreciate the advice from everyone who commented on this post

Thank you all

I will try to be the most careful as I can while shopping online ;)

@djshenanigans You can use the File Manager (from the RetroPie system in EmulationStation) to copy your ROMs to the SD card, from the USB stick. Just rename the retropie-mount folder on the USB, so it's not automatically mounted over the ROMs folder by RetroPie. After plugging in the USB stick, the files there should be available under /media/usb0.

@xtv said in Read psx roms off SD card & USB:

One solution could be splitting this into two subdirectories, like A-J and K-Z, one of them being a symlink to the USB drive.

That would be a simple visual solution to "hide" the separate-location structure. You could also split it on release year or franchise to help hide the fact.

@pojr Cool, glad you got it! I meant to mention that one as well as I has tried it, but it didn't fix
the issue for me.

@mitu I wanted to circle back, you were right. In the terminal, I typed df -h / this got me the info on the SD card. So, that resulted in 118gb Space, 113gb used, 0 Space available, 100% used up.

I thought this was odd, my SD card should be close to 128gb. Anyways, I deleted a bunch of games, etc and ran the same command and got the following:

118gb space, 103gb used, 10gb space avail., used 92%

So like I said, you were right!

Thanks!

Also, what's Ether? Never heard of it. I used Win32DiskImager only because Etcher doesn't work on Windows Vista. I hate Win32. I need some sort of easy alternative like Etcher.

@mitu Cool! Thanks a million for that I appericiate it. Yeah the wonder of Chineseum arcade controller sets from Amazon... every time the keyboard encoders are ever so slightly different with some showing as something like Micronek (Microtek) and some as Dragon something.

Thanks again

@backstander I tried that didnt work as well. I have a feeling my SD card just isnt upto scratch.

I got myself a Pi 4b now with a 64GB micro sd card, the "dtparam=sd_overclock=100" and it works fine. Consider this case closed, cheers for all the input though guys :)

I don't think the SD card capacity has any role in this, more likely the emulator versions are different on the systems you're testing. Reicast seems to have issues in the latest versions with controller inputs - configurations that worked before are not working at all right now.

@BennyProfane
I saw some people on internet saying that 64Gb SD Cards need some special treatment, in order to be compatible with Raspberry Pi, I don't Know, but if you say it works, I'm not worry :P

Thank you for your help! :)

@Lloltic Every card is a little different. That being said, if you have a card formatted in one format it will show a different amount of disk space in another.

It sounds like you have downloaded/backed up a pre-built image and are trying to burn it to a new card. The best thing you can do is burn it to the SD card and see if it will fit. Let the application tell you it won't, not your eyes. The other suggestion is to use PiShrink to shrink it down.

Keep in mind if it is a 3rdparty image you'll be hard-pressed to find support for it here if you do get it going.