William borrowed my camera to go on his honeymoon. He also lost the photos with a poorly timed crash & drive reformat. So he wants to borrow the card and recover the data. Thankfully I have not used the camera since he returned it despite thinking I should.
Luckily I ran across A Computer Repair Utility Kit You Can Run From a Thumb Drive.
I didn’t like the setup of Photorec as it runs through the command line. Navigating the tree was confusing at best. It did recover 1,166 photos / 3.62GB for me.
Not trusting a single method, I also tried Recuva. That worked a little better. It reported 1,395 files found. However, 177 were unrecoverable. Getting 1,218 pictures / 3.78GB back was 52 / 160MB better than Photorec. Though many of the “recovered” pictures just say: Invalid Image. Maybe they really are Raw?
While trying to use Restoration, it crashed the first time. Not sure why. It was fine the next time, though it only found 4 photos.
Filename: Photorec doesn’t restore files with anything like the original name. Recuva and Restoration do.
Meta Data: OSes and image editors know about the EXIF data in pictures. All the Photorec pictures have date taken. Most of the Recuva pictures do. Guess I could see if only 52 pictures are missing the EXIF? That might explain why Photorec lost some of them.
All in all, it was an fun experiment. I am not curious how these stack up against of the proprietary software? Why pay $40 when these are better?


WordPress Error: This file cannot be used on its own.
April 13, 2008 in Blog Software by Ezra S F | No comments
In posting a comment to a friend’s WordPress blog, it came up with the error:
I was responding to a comment, so I doubted that he broke his blog between making a comment and my response. So I went looking though my own install. Essentially, at a shell I used
to locate the file involved is wp-comments-popup.php. This file contains code which checks for the HTTP_REFERER variable has specific values equal to the path and file name for the comments page. If this is not the case, then it should throw this error. The file mentioned in the error is wp-comments.php.
Its seems that I had configured my web browser not to pass the HTTP referrer to web servers, so the check failed and threw this error.
Maybe the WordPress developer who designed this has no idea about the ability of web browsers not to send a referrer. Searching for the error on the WP site yielded nothing. From the tons of comments about people hitting this error, lots of people turn off sending referrers.
Solution for those leaving comments: If you attempt to leave a comment and see this error, then enable referrers. WordPress actually has a decent article on enabling HTTP referrers for a number of different pieces of software.
More friendly error for WP blog owners: Edit wp-comments-popup.php. Change
to