Problems with some PSX roms

VahnXDean

@markyh444 i'm redoing the tests now and it seems that the image was really the problem. i just need to do some tests with my PSX roms to confirm it. Just one more thing: i was in a hurry to test if the image was the problem, and my PSX roms were taking too much time to be transfered to my notebook while i was doing the backup, so i decided to do a backup of my micro SD card using the Win32diskimager, and then format my card to install the correct image. But now i don't wanna restore the backup in my SD cause i don't wanna mix anything of the previous image with the new one. Is there any way for me to access my backup roms that are in the backup file without the need to restore them in my SD?

markyh444

@vahnxdean if you restore the SD it'll overwrite the correct image you already have. You might be able to open the IMG file, but you'd need to do this off a Linux platform as the partition with the games and config can't be read in Windows.

I've not done it myself, but if you have a Google about there might be a Linux tool to do that.

VahnXDean

@markyh444 i will try to find this tool, i just need to see which roms are there, so i can download them again.

what i should search? tool .img linux on windows?

markyh444

@vahnxdean I've got no idea.

Sano

Best option is to use a linux live distro.
Then use fdisk -l to spot the offsets of the partitions and mount it with correct options (see here : https://raspberrypi.stackexchange.com/questions/13137/how-can-i-mount-a-raspberry-pi-linux-distro-image), or use kpartx.

chipsnblip

@vahnxdean or if you are willing to set up a linux-based virtual machine, you can mount the image partitions from a terminal like this for example:

display partitions on the image:

sudo fdisk -l /path/to/image.img

multiply the block size (eg. 512 bytes) by the starting sector (eg. 124928) and you have your offset:

expr 512 \* 124928

make temp directory to mount the partition:

sudo mkdir /mnt/tmp

finally mount the partition:

sudo mount -o loop,offset=63963136 /path/to/image.img  /mnt/tmp

when you create the virtual hard disk, be sure it's large enough to hold the OS, the .img (unless it's stored in a shared folder on the host OS), and the mounted partition(s). a live distro as mentioned above is a good option.

Sano

Busted :D
But you definitely deserve an upvote here :)

BuZz

@chipsnblip You can make this a little simpler without having to work out offsets by using kpartx

eg

kpartx -a /path/to/image

more info: http://www.forensicswiki.org/wiki/Mounting_Disk_Images#kpartx

Sano

Aaaaahhh.
After a few months not posting here, I realize I really missed this feeling of being invisible sometimes :)
Just joking guys, nice to post here again !

Back to the topic, I sometimes do a ls -R /home/pi/RetroPie/roms/ > roms.txtin order to have a listing of all roms in my setup, in case of emergency.

chipsnblip

@buzz thank, never knew about that. i found kpartx in the package 'multipath-tools' in the AUR

BuZz

@chipsnblip It's a useful tool. I only discovered it last year or so, and much simplified my scripts for building images etc.

VahnXDean

Man, i know nothing about Linux, so i think i will just leave this backup away and download my roms, there aren't many roms anyway, so no problem with that.
Would like to thank everyone, my retropie is running perfectly now:
@mitu
@jonnykesh
@markyh444
@Sano
@chipsnblip
@BuZz

Dont know what is more awesome, raspberry/retropie itself or its community :)