Fatdog64-700-save file corrupt on hard reboot-how to fix?

[dbabits]

Fatdog64-700.
I had to hard-reboot due to OS freezing on closing of laptop's lid. This is tracked in a separate issue.

Now, upon reboot my save file was skipped, Fatdog booted without it,
and the save file shows with big exclamation mark in file browser, and with all ???? in ls -l output where perms and size would be.

The savefile is on NTFS partition, which is not damaged.
How can I fix it, or at least salvage some information out of it?

[jamesbond]

Try to see if you can open the file by clicking it (or, from terminal, do "filemnt /path/to/your/savefile". If you can open it then hopefully you can copy files out of it.

But honestly, I doubt that you can do that (the ???? you've got when listing the savefile is a very very bad sign). Try to boot Windows and run chkdsk on that NTFS partition. Hopefully you're not doing this on Windows 8 boot partition - or you are in for a very nasty surprise

EDIT: Please post questions related to Fatdog only in Fatdog thread. Kirk and I we don't monitor all the threads in this forum as they are mostly for Puppies; questions posted elsewhere may not get noticed and may not get a reply.

[Ted Dog]

I have same problem with lid close, I use a few work-arounds from disabling suspend.sh (easiest to do), to adding killall X in that same script, or changing suspend type from mem to standby.
Search for my resent posts, I am actively working on understanding / fixing this issue I can't untrain decades of mindless lid close behavior