Note: Updated and republished for 10.6.4’s release; skip it unless you really really care about all the OS X releases. Originally published on November 14th, 2005.

Below the break is a table showing all major releases of OS X, from the public beta through the latest public version, which is 10.6.4 as of June 15, 2010. Note that this release marks the 55th release of OS X (counting both major and minor versions, and skipping two ill-fated updates). Wow.
More »« Less

It was my turn on the Macworld video blog-go-round again this week. The topic I chose is “working with multiple Macs in one home.” The end result is a 10-minute clip covering a number of third-party tools that make the process easier, and a couple of general usage hints.

Due to the huge number of downloads, the size of the macworld.com video is 320×240. But if you want, you can see grab the original 640×480 version right here. Warning, it’s 185MB in size (I didn’t work very hard to compress it, so the quality is good, but it’s huge).

After struggling for many months to solve an odd color fading issue with videos I encoded using H.264, I decided to get serious about solving the problem.

After much Googling, I found an answer and wrote it up for macworld.com, in case others are being afflicted by the same problem.

Much like my work with the Intel Core Duo mini, you can now read about the new Mac Pro (parts one, two, three) on macworld.com.

I spent the better part of a week poking around inside the machine, running benchmarks, playing with Rosetta and native apps, and testing games (both Rosetta and native). While not quite as in-depth as the piece on the mini, there’s still a lot of content to be read.

OS X uses a multitude of cache files–as an example, my user’s Library/Caches folder contains 164 top-level items, most of which are folders containing more folders. In total, there’s presently 1.18GB of cached data, just for my user. Wow.

Most of the time, this is a Good Thing, as it makes the system more responsive, as it’s quicker to retrieve something from cache than to calculate or redownload it. However, it can also be troublesome at times. Like this morning, in my case.

I fired up Mail, and despite the fact that it was running perfectly last night, it was glacial. Folders took multiple minutes to open. Moving a message was a 15 minute process, if it worked at all. Even worse, though, was that when Mail was having its fits, the Finder was completely unresponsive. I could click on some folders, but others would bring the Finder to the land of permanent spinning rainbows. Trying to mount a disk image resulted in more spinning rainbows.

So I restarted, and tried again–it had been quite a while since the last restart. But I had the exact same symptoms. Unresponsive Mail and flakey Finder. I spent a few minutes trying to figure out if I’d changed anything or not, even though I was positive I hadn’t touched the system while sleeping :).

Then, after another restart and repeat of issues, I thought I’d try deleting Mail’s cache folders. Inside my user’s Library/Caches folder, I opened the Mail folder and deleted everything, then emptied the trash. Launched Mail again, and…voila, it was perfect! Speedy as its ever been, and the Finder didn’t have fits while Mail was running. Everything was basically back to normal–all because I deleted a series of temporary files that are supposed to do nothing more than make data access quicker. Go figure!

This is the first real cache trouble I’ve had on OS X, but it is a relatively common source of issues for others. Since cache folders exist in many spots (your user, the top-level Library folder, and the System folder), you might want to look into one of the cache cleaners, such as Cache Out X or Tiger Cache Cleaner (among many others), to make the job simpler.

I think I may add a general cache emptying routine to my crontab, just to make sure it happens somewhat regularly, given how much trouble this one incident caused.

The recently-released OS X 10.4.7 update included a not-announced Dashboard widget update feature which silently checks to make sure that your widgets are valid. I agreed with the need for such a feature, but wrote about how I think Apple could have implemented things a bit better.

Ever wondered about the various settings in the Font smoothing style pop-up of the Appearance System Preferences panel? Thanks to a recent crash, I was forced to revisit the font smoothing settings, which I literally hadn’t looked at in years.

I found the results of my tests somehwat interesting, so I wrote them up for macworld.com.

I’ll start off with an admission: I’m a relatively clueluess user of the command line in OS X. Sure, I know my way around the basics such as ls, cp, mv, and I have a working knowledge of vi, and a basic understanding of some of the more advanced programs. But that’s about it—minimal shell scriping skills, no knowledge of regular expressions, and only the most basic understanding of pipes, redirection, combining commands, etc. So I find myself regularly amazed by the power of what (for a Unix wizard) would be an amazingly simple task.

Such was the case yesterday. Earlier in the day, I’d had a bit of a scare with our family blog site (like robservatory, it runs on WordPress). Due to a mix-up on the administrative end, the WordPress database for the site was deleted. Historically, I’ve been very paranoid about backing up the macosxhints’ sites. But for whatever, reason, that same paranoia didn’t extend to my two personal sites. Hence, I had no backup to help with the problem. Thankfully, the ISP did, and the family blog was soon back online without any loss of data. But I resolved to not let this happen again without a local backup of my own.

More »« Less

Well, it does when you’re talking about installing 10.4 from the retail DVD, and then upgrading it to 10.4.3. I re-partitioned a portable FireWire drive tonight, so that I could put both 10.3 and 10.4 on it for testing purposes. I haven’t clean installed 10.4 since the release back in April, and I hadn’t really noticed just how many megabytes of updates there have been. Suffice it to say, there’ve been a lot! Seven packages the first time around, then five more after that.

To Apple’s credit, I guess?, it only took two restarts to get the system up to date. But I shudder to think about those who lack broadband access to the net; even a moderately-speedy DSL connection would groan under the weight of these updates. Approximate download times for 311.6MB:

So what does one do if you only have modem access? From my memories of my 56Kbps days, the modem more routinely connected at about 44Kbps, meaning probably something like 15 hours of download time. And I don’t believe Apple allows user groups to distribute update CDs any more (do they?). Anyone out there still on a modem connection? If so, how do you stay current with 100MB+ updates becoming routine nowadays? (Note that this doesn’t just apply to Apple’s updates; even updates for things like Quicken, Acrobat, etc. are swelling into the multi-megabyte size).

Last weekend, I was working on a relatively large–OK, a huge–17.8GB QuickTime movie. This was the raw capture of 35 or so minutes of flying time in X-Plane.

I had the original movie open in QuickTime Player, and I had also exported a notably smaller (200MB) H.264 version, which I was playing with in Motion. Then, for no apparent reason, all heck broke lose–both screens on my system suddenly went 70s psychedelic on me, as seen in the grab at right of a portion of the screen (click for full-size).

In addition to the messed-up colors, things were also not in the right spot on the screen–you can see this with the location of the Smart Folders object in the large screenshot. The system seemed to be working fine; I just couldn’t make anything out on either screen–except the menubar (but not the menus themselves). So I used Command-Tab and the ‘Q’ key to quit various running apps, including QuickTime and Motion.

After quitting nearly everything I had running, the screen returned to nearly normal–the only remaining issue was that objects’ shadows were really messed up, showing pieces of other windows instead of a fuzzy gray/black shadow. I logged out and back in, and that fixed that issue.

What this reminded me of, more than anything, was mucking about with my Apple ][ back in the day–if you “poked” some data into the wrong memory locations, you could mess up your display in quite a creative manner! It almost seemed like that’s what OS X was doing–I had used all the available RAM, so it started using the video card’s RAM for storage instead. Yes, I know this isn’t possible, and it’s in no way what happened.

Anyway, in five years of OS X usage, this is by far the oddest visual distortion I’ve ever seen, so I thought I’d share. I was quite impressed that the system itself was still usable–I have yet to restart since that incident, in fact, and all has been fine after the re-login.