I spent a good portion of last week attempting to recover about 30GB of movies that had been deleted from a Mac with a 60GB hard disk. When a file is deleted its normally left intact on the hard disk except for a marker saying its space can be reused. This means that deleted files can be fairly reliably recovered, so long as the space hasn’t since been used for other purposes. We found the movies were missing only a few days after they were deleted, and they took up half the hard disk, so I was fairly confident they could be in part recovered.
Of course that’s great in theory but in practice how I was I going to recover those files? A quick bit of Googling discovered three programs that will attempt to recover deleted files on the Mac:Boomerang, FileSalvage, and Data Rescue II. I downloaded a trial copy of each and set to work. Here’s how they performed:
So in my testing Data Rescue II was the clear winner. Don’t read too much into this, as I was only looking for movie data; one of the other programs might work better for a different type of file. However, if you’ve deleted some files that you want to recover I would start with Data Rescue II, then try Boomerang, and only then try FileSalvage (and go to bed while it’s running). Finally, if you have two Macs a firewire cable and target disk mode will make the whole recovery process a bit simpler.
Now what I want to know is: why would a Mac developer invent their own user interface widgets unless they really want that amateur feel to their product? Is there something about Cocoa programming that makes it easier to create, say, your own tab component than use the system one?
Update: More thoughts on Ravelry
From my study I can pick up about six different wireless networks. They all have simple names: the name of the router (good old
Belkin54g is always up and always open), the street, the owner. But in West Hollywood that is not the way they roll. How about
fuckyougetyourownnetwork, or my favourite,
Lesbian_Dildo_Vagina_Party? Is this a cultural thing? In all my time in the UK I’ve never seen a network with names like those. On the other hand I am pleased to see one of the networks is named after me. What are the networks around you called?
Over the last weekend, and sporadically this week, the computer that hosts untyped.com and Untyped’s email server has been under attack from a network of spam bots. It doesn’t appear that we’ve been targeted specifically. Rather, it seems that the bots are scanning for email addresses to spam, presumably to propagate the bots. It took down our email server over the weekend, but we’ve since taken steps to combat the flood of traffic. However, if you sent us an email and are waiting for a response, you might want to send it again.
We’d don’t know what bot is attacking us, but there is a good chance it is the “Storm Worm”. I didn’t know of the Storm Worm before we were attacked; my reading since then indicates it is a truly massive network, with the potential to cause a lot of trouble. This Wired piecediscusses how Estonia was taken off the Internet by a massive bot net attack.
I use Amazon S3 as an off-site backup for data on my desktop
computer. S3 has two principle advantages: there’s no upper limit on
the amount of data you can transmit or store, and it’s very cheap…
sometimes a little too cheap.
Two days ago I received an auto-generated warning from S3 about my
Greetings from Amazon Web Services,
AWS was unable to charge your account based on the payment
information you provided. Please update your payment method
information using the Your Web Services Account section of the AWS web
Amazon Web Services
There were a few extra details in there that convinced me that this
wasn’t spam, but that was the gist of it. I logged on to my account to
find that my balance was a whopping $0.01. A single cent!
I checked my credit card details and they seemed to be okay. I
re-entered them to be on the safe side, and then emailed AWS asking
them to re-try the payment and let me know if it failed again. I
received this response:
Thank you for contacting AWS regarding the payment issue related to
your August 1st bill. We have found that some credit card issuers
decline charges of $0.01 (USD), especially when the amount is
converted to another currency. AWS is working on a solution for this
issue. In the meantime, please contact AWS
directly at firstname.lastname@example.org if this issue should occur again.
The $0.01 (USD) charge on your August 1st bill has been forgiven,
and your account is in good standing.
A month’s backups, totally free of charge – that’s value
for money. I shall be recommending S3 to all my friends.