Skip to content

macOS System

Discussions on system-software-related topics…

Click [and click and click …] to install

Tiger boxIn comparison to other platforms, installing software on OS X is a breeze. Usually, you just drag and drop the program from the disk image to its destination, and you're done. Even some complex programs can be a snap to install -- Office 2004, for instance, has its installer hidden in its code, and it's smart enough to run the first time you launch any Office app. So even though it installs stuff to a bunch of places, it's transparent to the user.

The third option is Apple's installer, which helps guide the user through the software installation process. The installer is the ideal solution for programs that need to install things in many spots, and require administrative access to do so. And while using the installer is still a very simple process, I still find it a frustrating process at times.

As an example, consider my recent installation of a new version of Snapz Pro X, the indispensible screen capture tool. Please note that this is not intended to be a slam on Apple's installer or Snapz Pro X (which I rely on every day!). Rather, it's just an example of how the process can be a bit frustrating and confusing, along with a couple of suggested improvements.

[continue reading…]

Should Apple applications be movable?

Tiger boxA quick entry tonight, just because the subject came up recently in this hint regarding iSync. In particular, the hint (and comments) note that iSync will fail if the application is moved into a directory whose name contains spaces. I had added an editor's aside about moving apps in OS X, and my personal belief that it's a Bad Thing to do. As noted in the second comment, it's not necessarily an issue with using applications -- they'll (more than likely) run fine from most any location. Instead, it's an issue with Apple's updaters failing if the application they update isn't in the usual spot.

Although it's my philosophy not to move Apple's applications around in OS X, that doesn't mean I'm happy about it. I have multiple partitions on my drive (partition vs. don't partition; that's a subject for another day!), and have one set up particularly for all my applications and utilities (called Apps). I put everything on that partition -- it makes it easier, for instance, to erase and install OS X if I have the need. As of result, the only things you'll find in my boot drive's Applications and Utilities folders are Apple's programs, along with anything that just won't run if it's located elsewhere (Tony Hawk Pro Skater 4, for instance, fails if it's not in /Applications). Everything else lives on my Apps partition. As much as I'd love to move Apple's stuff out of there, after reading about the issues people have had with upgraded applications not working, I've decided to just let sleeping Mail applications lie.

[continue reading…]

How [not] to upgrade to Mail in 10.4


Thank you, Andy Warwick! I'm leaving the following article online, just so I remind myself how much time I wasted on this. However, the comment from Andy (#9 in the chain) pointed me to what I was doing wrong. So for anyone who hasn't imported their email yet, the trick to using the Mail for OS X import function is this: simply point it to your old user's Library/Mail folder, no deeper.

I still think Apple's language could have been clearer (see my #10 comment), but I retract the other nasty things I said about the import routine. When pointed at the correct folder (I just tested it), it worked like a charm. Good job, Mail team. Now how about making the import screen read simply "Please navigate to the previous Mail folder"?

This is a follow-up to my The Art and Science of OS X System Upgrades article. I'm (still) in the process of upgrading my main drive, having just finished migrating my email archives last night. Why did it take so long? User stupidity plus, in my opinion, some poor functionality in 10.4's Mail import routines.

As noted in the earlier article, I had chosen to do an upgrade install on my main drive, but to not automatically copy over my user's folder (due to all the cruft in it). It was this decision that ended up costing me many hours of email migration labor. Why, you might ask, did it take so long?

After I got 10.4 up and running, before doing much of anything else, I launched Mail and set up my two primary accounts, just so I could keep up with email while doing the rest of my work. Mail may have asked me about importing old email when I first launched it, but I don't think it did -- my ~/Library/Mail folder was empty, since I hadn't moved the old Mail folders over. Apparently if you allow the user information to migrate, Mail will automatically import your old Mail messages. Ah, I should be so lucky...

[continue reading…]