Ralf’s Blog

I recently installed the upgrade to Thunderbird 3.0 on our main PC. In my account, all was fine afterwards, but my wife had a very strange problem: All previously stored passwords seemed lost. TB 3.0 asked for the passwords of all accounts that she had, both IMAP and NNTP. When I started TB 2.0 (which I reinstalled for investigating this issue), all was fine again — apart from the password for the NNTP account, which was incorrect or missing, so I entered it again.

I noticed that now that TB 3.0 was installed, there was a file signons.sqlite in the Profiles folder in addition to the well-known signons3.txt file. I figured that the SQLite file was probably the new password store, which was migrated from the pre-3.0 password store in the TXT file. I further figured that during the migration something probably went wrong (eventually the missing/incorrect/corrupt NNTP password?), so I removed the SQLite file and started TB 3.0 up again. Upon starting up, it recreated the SQLite file, and this time all worked well.

So, if you folks have a similar problem, try the approach I described here. It should not be risky at all, since the TXT will always be the “master” file when migrating from 2.0 to 3.0, so removing the SQLite file will have it re-created again upon next startup.

Two months or so I ordered the Snow Leopard DVD for my Macbook Pro. Finally I had the time to perform the upgrade from Leopard. Before actually doing so, I tried to create a disk image of my current Leopard installation. So I booted the Snow Leopard DVD and ran “Disk Utility” from it. Because the target of that disk image was an external hard drive shared by my team, I wanted to create an encrypted image.

Regardless of whether I selected “128-Bit AES” or “256-Bit AES” as an encryption method, I immediately received the following error message on screen:

Unable to create "Macintosh HD.dmg" (Cannot allocate memory)

What is this trying to tell me? No space on hard drive? Impossible, since the external hard drive is a 2 TB empty drive. Moreover, “memory” usually refers to “main memory”, or “RAM.” So is Disk Utility actually trying to read the whole 200 GB hard drive into the RAM, then encrypting it, and then creating the disk image from it?! I can’t believe that anyone would be that stupid to design a disk imaging program like this…

I finally changed the image format to “Compressed”, and presto, it worked!

Anyway, why, oh why is it so hard to generate “user friendly” error messages? And why does this happen under Mac OS X of all operating systems, supposedly being the “user friendliest” OS in the universe?

This is not the first time I receive such useless error messages in OS X. Hey Apple, care to finally make your homework???