Linux FatDog64 not reading savefile on mmcblk0 drive

[mzee]

I have been trying to get FatDog 64 to read its save-file on a mmcblk0 drive.
When installed to a conventional SDA drive there is no problem.
When installed to a mmcblk0 drive it can not find the file
I have tried adding "savefile=direct:/dev/disk/emmc0p1/fd64save.ext4"
OR
"savefile=direct:/dev/disk/by-partuuid/(UUID as revealed by "blkid")/fd64save.ext4"

savefile=direct:/dev/disk/by-partuuid/UUID="1017-D8D9"/fd64save.ext4

Should the UUID="1017-D8D9" have no quotes?
Should it be a PARTUUID number, not UUID?

Linux keeps the geriatric brain working!

[piroska]

https://askubuntu.com/questions/6278...ead-superblock

[mzee]

https://askubuntu.com/questions/6278...ead-superblock

The partition with the 'savefile' is the only one, and contains the whole OS. It writes to the file Ok when you shut it down, but for some reason will not read it when booted. If installed to a conventional drive, SDA, SDA1 etc there is no problem. If I put the 'savefile' on a USB drive, sdb, sdb1 etc, no problem.

The 'savefile' reads & writes Ok in the file manager. Is there a way of including an instruction to treat emmc0p1 as SDA1?

[MushHead]

I'd doubt that the quotes are required around the UUID portion.
You can just try "ls -l /dev/disk/by-<thing>/" for the available values of <thing> from the shell to see what the correct path is (tab completion will be your friend here). Those paths are just links to the underlying /dev/sdX "real" block device.