After my recent short walk I have 3 16Gb SD cards full of photos, which I moved to my computer with MultiComander. The first two cards went flawlessly, but I've run into dreadful issues with the third, where the images are corrupt. Well, corrupt on the first copy/move (mostly).
What I did, which is what I've always done (maybe not any more though
), is to move the files from the card to the computer. Some of the moved files ended up like this (reduced): Now, what that implies to me is:
- The original move produced some corrupted files. Caused by?
- MultiCommander?
- Windows?
- Hard Drive?
- The camera wrote corrupted files.
- Bad Card? But it's not consistent?
- Naughty camera? It's not the most perfect environment for a camera in the hot and cold, sometimes rain, and jolted when I fell over... But the timing of the corrupt files doesn't correspond with any of those events.
- The recovered files may not have been the final file the camera wrote? Maybe the camera used the card as a temporary storage when combining images?
- The recovered files are not named the same as what was moved, so I'm not sure what that means?

If a JPEG expert is interested they can access the original, non-reduced, files for comparison here (warning - they are large files). When I edited them with IrfanView (eg to resize), IrfanView would complain that the file format was corrupt: extra data where it shouldn't be, or missing data; which to me sounds like the file has been written incorrectly (either by camera or software during the copy):
I'm going through, slowly, and re-copying them when necessary and I think that in the end I should not have lost very many images (though with 9,500 I can afford to lose some and not be too upset
), but the why of this problem is troubling me... anyone with any ideas?The main lesson I learned is that Move as a file action is not the best idea when there are lots of files and it may be best to check first before removing them from the origin location (but in my defense: this is the first time that something like this has ever happened).











Logged







But have you found it to be every file or random?





