Another thing you should check is your flash drive, those things can wear out after a while (they are based on a chemical process, so like batteries they get used up). I have seen symptoms like improperly copied files before, on older devices. JPEGs that are half garbage and so on. Flash drives are cheaper than software, so that might be a better place to start—though Chronosync does have a trial period.
ta; will do.
Problem hasn’t reappeared with new flash drive; fingers crossed.
Could a ‘recover project’ feature be added to Scrivener? This might only be an option with errors like “The project you are trying to load uses an older format and cannot be opened…”, and it wouldn’t guarantee full recovery, but at least the user wouldn’t be faced with the prospect of losing a complete project.
It is still an excellent piece of software.
Donncha
There are already some substantial recovery mechanisms in place (check in your Binder for recovered items, these are bits of the project that Scrivener found in the package file and doesn’t know what to do with) and in your Documents folder, which might contain bits of projects that are in trouble as well. The next version of Scrivener will be even more robust about this kind of stuff.
The problem with projects that have blank documents and so on is that, well that’s actually what they consist of. If you open up the project bundle and read the actual RTF files that make up a project, they’ll be blank too. So there really isn’t a good way to recover from that, short of using back-ups from when the project was healthy. If your old Flash drive was writing incomplete or corrupted RTF files, there isn’t much Scrivener can do about it, I’m afraid.
2.0 has an “Import Scrivener Project” feature which will work with corrupted projects that cannot be opened too - it won’t be able to import the structure of corrupted projects, but will at least recover the files, file titles, synopses etc.
All the best,
Keith