Invisible Drive on OS X

The hard drive icon on my OS X’s Finder was no longer appearing on my desktop; here’s how I fixed it.

I happened to sign on to my desktop Mac and noticed something very strange, the Harddisk icon was no longer on the desktop.

Other clever tricks for looking at the file systems showed the file was most certainly present, although Finder operations were treating the volume as if the hard disk was hidden or invisible. The drive was there when I used terminal and did $ ls -l /Volumes

Finder Preferences showed that icons should be shown, but just the drive icon wasn’t appearing.

Then I found this aritcle, which suggested firing up the Script Editor and running this script:

tell application “System Events”
set visible of disk “NameofDisk” to true
end tell
tell application “Finder” to quit
delay 1
tell application “Finder” to launch

I believe I got myself into trouble by accident when I did the last disk repair using Disk Warrior or Disk Utility. Somehow the operation marked the drive as invisible. Undoing it was as simple as asking the system to make it visible again.

Clever Bulk Rename Trick in Windows

Stumbled into a clever way to rename a bunch of files to have the same prefix and a sequential numbered suffix… from the Windows GUI no less.

Ever want to rename a bunch of files to the same prefix, but have an incremental count after them?

From Explorer, select all the files that you want to bulk rename, right click, and select Rename.

While all of the files will be selected, only one is editable. Give the file a name, let’s pretend for the sake of discussion you typed ABC.jpg.

All of the rest of the files will be renamed ABC (1).jpg through ABC (n).jpg, where ‘n’ is the number of files minus one, since the first one doesn’t get a number.

Knowing this, you can do some clever stuff. Create one bogus file renamed to ZZZZZZZZ.TXT at the end of your list; select all the files, and bulk rename them as shown above. Then delete the bogus file, it should be the only one without a number, and you’ve just made a sequence of files.

Is AVG killing windows Remote Desktop?

Today terminal services stopped working, and I could no longer remote in to my Windows box. At the moment, speculation suggests it appears to be a false-positive by AVG.

This morning Anti-Virus Guard,AVG (not the free version), decided that TRMSRV.DLL in the System32 directory was threat and copied it out of the directory.

The result was that Terminal Service no longer works. That means that software like Remote Desktop Connection 2 (RDC), can’t connect, although the machine responds to pings and Samba requests.

Placing a exception in AVG to not check that directory (sounds bad, eh?), and restoring the file from another machine seems to have temporarily address the problem.

I wonder if AVG knows about this.

We’re also seeing that Cygwin and the System Restore Point is also among the collateral damage.

UPDATE 11-Nov-2008: Looks like AVG is now flagging Windows as a virus.

LIBLDAP2 Not Installable

Unable to find a solution related apt-get failing on Ubuntu while trying to upgrade packages depending on the libldap2 (>= 2.1.17-1) package, I figured out what was causing the problem… additional repositories in my /etc/apt/sources.list file. Here’s what I did to finally be able to upgrade cleanly.

Warning this is a very geeky entry aimed at apt-get users of Ubuntu, readers seeking humorous content should skip this post. Remember, this is a technical blog.

If you’re still with me, then I suspect you’ve just been plagued by the message:

Depends: libldap2 (>= 2.1.17-1) but it is not installable

I’m using Ubuntu 8.04 LTS Server Hardy Heron, specifically on a 64-bit AMD system.

Normally, when I do an $ sudo apt-get update things go very smoothly, but not today. Here’s what I got.

The following packages have been kept back:
alpine dovecot-common dovecot-imapd dovecot-pop3d libpq5 postgresql-8.3 texlive-base-bin trac

The following packages have unmet dependencies:
alpine: Depends: libldap2 (>= 2.1.17-1) but it is not installable
dovecot-common: Depends: libldap2 (>= 2.1.17-1) but it is not installable
Depends: libpq4 (>= 8.1.4) but it is not installable
libpq5: Depends: libldap2 (>= 2.1.17-1) but it is not installable
postgresql-8.3: Depends: libldap2 (>= 2.1.17-1) but it is not installable
texlive-base-bin: Depends: libpoppler0c2 (>= 0.4.2) but it is not installable
trac: Depends: python-genshi (>= 0.5) but it is not going to be installed
E: Broken packages

Unfortunately, where ever I went, I didn’t find a solution. [1] [2] [3]

The ‘recommended’ solution is: $ sudo apt-get -f install
This did not work for me, nor others.

Neither did: $ sudo apt-get dist-upgrade

At this point, I went on an apt-get remove and apt-get autoremove binge. This didn’t help either.

This got me into a horrible loop, where packages sysvinit-utils, sysvinit, and initscripts needed to be installed, but could not because:
Unpacking sysvinit-utils (from …/sysvinit-utils_2.86.ds1-47~bpo40+1_amd64.deb) …

dpkg: error processing /var/cache/apt/archives/sysvinit-utils_2.86.ds1-47~bpo40+1_amd64.deb (–unpack):
trying to overwrite `/usr/share/man/man1/mesg.1.gz’, which is also in package sysvutils

I even tried manually installing packages one at a time. Didn’t work. I was even so desperate as to move the file mesg.1.gz elsewhere. That didn’t work.

Then I tried the following and things got a little better:

$ sudo apt-get clean
$ sudo apt-get autoclean
$ sudo apt-get check
$ sudo apt-get purge
$ apt-get -f upgrade

But I now had a problem where packages, specifically alpine, depended on on libdlap2, and it was telling me that it couldn’t install it, so upgrading wasn’t possible.

I made the mistake of $ sudo apt-get remove alpine, which would not let me undo that mistake by reinstalling.

My hunt brought me to libldap2-dev, but while this installed, it didn’t help alpine’s dependencies.

Even with the super-duper do-everything command, nothing helped:

$ sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get dist-upgrade -y

Then it dawned on me, perhaps some of the repositories that I added to /etc/apt/sources.list were giving conflicting dependencies. Luckily, I annotated heavily what I had ever added to this file.

There were only two things: Subversion, and Mono. Here they are. You want to comment out these lines:

## Subversion obtained from https://edge.launchpad.net/~clazzes.org/+archive
deb http://ppa.launchpad.net/clazzes.org/ubuntu hardy main
deb-src http://ppa.launchpad.net/clazzes.org/ubuntu hardy main

## Mono added by request of FogBugz installation
## http://www.fogcreek.com/FogBugz/docs/60/topics/setup/UnixGettingYourServerRead.html#deb
deb http://www.backports.org/debian etch-backports main contrib non-free

Then, I did a $ sudo apt-get updatee, followed by a $ sudo apt-get dist-upgrade, then a $ sudo apt-get dist-upgrade.

All of my problems were solved. No package dependency problems what-so-ever, and I was able to install alpine, and all the others, bringing me up to the latest and greatest.

Finally, I uncommented my sources.list file back to the way it was and tried the upgrade again. No errors. Everything was fine.

The solution was that something, and I don’t know which one, was causing conflicts. Reverting back to the virgin sources.list file state was enough to get Ubuntu happy to do the upgrades.

Unfortunately, since re-commenting the lines didn’t reintroduce the problem, I’m unable to tell you which repository caused the problem in the first place.

Loathing Dell, Hating Symantec

A password to uninstall Symantec Antivirus…?

In trying to repair a Windows laptop which was acting really slow and appeared to be riddled with problems, I discovered it was running Norton / Symantec Anti-Virus.

Ugh.

It’s been shown with benchmarks that this software kills PC performance. And, in other tests, AVG, which costs less, catches more, without being a resource hog.

So, I go to uninstall Symantec, which can be a chore unto itself. But this time I was greeted with a new source of irritation.

I got a dialog box which said “Please enter the uninstall password”. Great. Just great.

So, given that this OEM laptop had paid support by Dell, I figured I’d ask.

The answer I got back was “I wasn’t aware there was a password to uninstall.”

While Dell was dodging the support question, I found this very helpful article:

http://www.mydigitallife.info/2007/05/05/hack-to-removeuninstall-symantec-norton-antivirus-sav-client-without-password/

In it, it said change the value of this registry key, HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\Administrator Only\Security\, from 1 to 0 with RegEdit.

I tried it. It worked. No problems. Problem solved.

So, I tell the Dell Support person the point is moot, I got past it, and shared the link with him so that future customers with the same problem could have the problem solved. Isn’t that how it’s supposed to be? Learn something, and share — that way others don’t waste time down the path you traveled?

Dell’s tone instantly changed, they didn’t seem happy I got past it. And, then he tells me that Dell support doesn’t give passwords, or tell how to override them, even for OEM installed stuff; they would not be sharing the information, no matter how useful.

So, did they know about the password and just feed me a line? I was certainly left with that impression.

Incidentally, I’ve been told by an IT person, the next time I encounter the password box, enter: symantec

You’ve got to be kidding me.

iChat Problems: Fixed

Got Leopard? Find that iChat isn’t working? Do you run Parallels? Guess what, that may be it. What? You’re not running Parallels at the same time you iChat? Not relevant, Parallels has network services active even if the client isn’t. Here’s the workaround to get you chatting…

iChat and Parallels
While trying to iChat using Leopard to a system running Tiger, I ran into a problems that I never had using OS X 10.4 before: bad video quality to downright refusing to connect.

With a little research, I ran across this article and that was enough to resolve the problem.

Here’s how to get iChat working on OS X 10.5
…if you’re running Parallels.

See, turns out that Parallels, I’m using 3.0 Build 5582 (Dec 5, 2007), appears to be running some services, even when the virtual machine is active, that gets in the way of iChat.

Get out of iChat.

Go to Apple / System Preferences…, select Network, and click on Parallels NAT and change the Configure drop down to Off; then go to Parallels Host-Guest an change the Configure drop down to Off. Press Apply.

Get back into iChat and try again. For me, it instantly fixed the problem.

OS X 10.5.1 Finder Crash – repeatable

Found a very simple way to crash the Finder in OS X 10.5.1 – while repeatable for me, do other people’s desktops do the same thing? (No data loss, just Finder windows close.)

I’ve just discovered that I can crash the Finder, not that this inhibits anything in that it instantly restarts…

  1. Pick any FOLDER that’s on your desktop. Press Command-I to get info.
  2. In the bottom right is a pad lock, click it, and enter your password so you can change permissions on the folder.
  3. To the far left of the padlock is a plug sign. Press it.

For me, I instantly get an error on the console that the Finder exited abnormally with a bus error; this is usually a pointer trying to access memory that it’s forbidden to. The CrashReporter logs the event, and Finder restarts, closing the Info window that was just open.

While I can reproduce it effortlessly, can any one out there?

Comments on: Leopard is the New Vista

PC Magazine’s Oliver Rist has a harsh observation: Leopard is the New Vista. And what’s worse, he may be right. Here’s the Waltomatic take on each of his five points. Who’s the winner?

Today I was forwarded a review of OS X entitled: Leopard is the New Vista, and It’s Pissing Me Off.

LUV OS XI think it’s safe to say that I’m a fan of Apple, in general, as I find their hardware, environment, and tools far more productive for my development, office, and home needs than I ever did using Microsoft or its products.

I think it’s also fair to say that I’m willing to also point out when things don’t work:

Oliver Rist, raises some very good points in his treaty on Leopard’s recent similarities to Vista’s screw ups.

Here’s my take on his five points.

Vista Similarity 1: Wait for a Service Pack—Perpetually


Rist is right in saying that “[With Tiger] Everything. Just. Worked. Period.” I’m also quite in agreement that with Vista, even “a year after its shrink-wrapped release” it still has problems, driver issues, and “doesn’t work with 50 percent of new software.”

But I wonder how far back he’s actually recalling. Historically, I recall that each early version of Apple’s OS had serious kinks. Is comparing Tiger 10.4.9 with Leopard 10.5.1 actually a valid Apple to Apple comparison? (excuse the pun)

I’m with Rist if he thinks it should be, but accept the reality it isn’t. In my mind, Apple changed a number of things about the OS that they didn’t have to. Stability, size reduction, and additional hardware support will always earn high marks on my reviews. Unless the new glitz is functional, it doesn’t do much for me; but more on this in a moment.

At the moment, I’m tolerant because historically Apple has made right in reasonable time. By 10.4.3 and 10.4.4, I was quite happy. Given that I suspect Apple’s real purpose was not to make GUI fluff, but to pave the way for resolution independent graphics and new Core Animation, I’m surprised how well things held up.

Microsoft, Direct X improvements aside, gets no such pass, because as a whole, I still have problems with the OS, and it’s been around longer, and had more people working on it.

That said, I’m also aware that a good number of the Microsoft blue screens of death aren’t Microsoft’s fault — directly. When drivers do bad things, it can topple an OS. Of course, this leads me to wonder why Microsoft didn’t manage their kernel layers a bit better.

Knowing this actually provides some insight for Leopard as well. Everyone understood how Tiger worked. Too well, perhaps. There were quite a number of OS resource tweaks that delivered amazing integration and features. I was certainly one of the advanced users.

However, Apple assumes, and I think rightly so, that if you intend to do an upgrade in place, then if you’ve changed the operating system out from underneath them, you roll the dice. A number of people were bit by Unsanity’s Application Enhancer that didn’t upgrade at the last moment before installing Leopard.

Keeping up to date with OS X third-party applications is just as hard as it is on Windows. That’s why I eventually plopped down the money for Version Tracker Pro. Had I not, I would have been one of those that the new install would have taken out. Diligence is king.

Even so, my problems with an Upgrade was slightly broken features, like the password working after a screen save (despite the settings to the contrary), and performance. I later learned that the former was a permission problem on the preference, and the latter was a library extension that didn’t work with Leopard and just tried to keep reloading itself.

My solution was to do an Archive and Install. All of my options were preserved, just like an Upgrade in place, but because the OS was virgin fresh, my system behaved wonderfully.

I give Apple this round, simply because a “fresh install” with Microsoft is so destructive.

Oh, and yes, once you’ve touted something as a “new” feature, like 64 bit, you can’t do it again for the next release. That’s cheating.

Vista Similarity 2: Needless Graphics Glitz


Leah, my iPhone girl.I love eye candy as much as the next guy, and in my operating systems too.

However, I question the real value one gets out of it. As long as it doesn’t get in the way, that’s great. If it communicates more information subtly, that’s great too. Incidentally, what I mean by that is effects, like Genie, which show where your Window is going when you minimize it, is useful.

All these different preview modes, sliding covers, and non-sense, I could really care less about.

Though, I have to admit I’m a closet user of them. Sometimes it easier to quickly view an image to make sure I’ve got the right one, or scan the contents of a document because a poorly chosen filename was used. I’d like to think Apple could have done this without the big production.

What really gets my goat, however is that Tiger had transparent Windows. Then it went away! That really made me mad, because I was using them since I had a small desktop.

So, that made me go find Virtue, in order to have multiple desktops. My gosh, I loved that product. Where else could you have different backgrounds, on a 3D cube, and get to them by keystrokes, mouse maneuvers, or tilting or laptop or waving your hand over it and triggering the ambient light sensors!

But then Apple went and created Spaces. With no real future, Virtue is going away – – and killing off a fantastic sales tool for me. With no competition, I don’t see Apple adding these things back.

And, only now, are we starting to talk about the transparency I had before. Argh!!!

So, while Vista is pretty, and Apple is pretty, Apple got by for having slightly more than fluff for fluff’s sake. Apple gets to take this round, begrudgingly.

Vista Similarity 3: Pointless User Interface “Fixes”


I’ve got to say, again, I agree with Oliver. The new dock may look pretty, but Apple had an uncanny way of letting me know what was going on with those nice, readable from a distance, black, unobtrusive triangles.

Do I have a way to get them back?

Can I switch an put the dock on the side and get something more acceptable looking? Yes, but then again I don’t want it on the side.

It’s crappy decisions like this that cause people to write utilities to hack the operating system which cause the initial instability problems in the first place.

Using Vista as the example, just because something is pretty doesn’t mean it’s enjoyable to use.

Having said all of the above, I have to admit that many of the things I initially didn’t like, I quickly grew to use. They bother me less.

Let’s just say in this round, the bell rang, and there was no winner.

Vista Similarity 4: Nuked Networking


I groan when I see Microsoft operating systems splinter over stupid artificial limitations like how many network connections can be concurrently inbound or outbound. I shake my finger at any operating system which can’t handle jumbo packet sizes or let me switch between 10/100/1000 ethernet speeds.

But I do accept that Windows shares, using Samba, can be difficult with Microsoft deliberately sabotaging protocols to force a homogeneous network with them being the vendor. Embrace and Extend. Anti-Trust. Bogus interoperability. Halloween Memos. I just can’t take the message that Microsoft is out to help me seriously anymore; too much bad history; too little progress. DRM, WGA, poison pill updates, spying – that’s the reason I left Microsoft.

While I recognize that Apple and Microsoft are in a cat’n’mouse game for accessing Windows resources, I do have a complaint to put on Apple’s shoulders.

And that is: just because I have a network, doesn’t mean I want to network. Unless I’m trying to comb my network’s machines, don’t bring them all to my Finder. I don’t need that. I know what kind of network traffic Microsoft generates.

On the other side of the coin, VNC is now built in. And, well, wow. Apple, you did well there. It’s almost as if Apple knows I’m slowly expelling Microsoft and replacing it with Unix systems.

But that doesn’t change the fact that when I do need access to a Windows box, and I’m using my Mac, I want it to be just as seamless. Just the other day, I tried to copy a file from a Windows share to my local desktop to work with a local copy. Locally. (Sense a theme?)

The Windows box said “that file is in use” (because someone had the network Excel file open) and wanted to know if I wanted a read-only copy. The Mac, however, simply said Permission Error and never told me why.

Apple: I need error messages to not be so abstract. Give me a way to Option-Click on them or something and dump the error.h code; in short, if I’m smart enough to fend for myself, let me. Or, just make it work.

I assume people have already heard that if you Move (not copy) a file from one resource to the other, if the destination is full and aborts the copy, the source file still gets deleted (the other half of the move). I hope that’s fixed.

Now, the sheer fact that Microsoft has a horrible time with other OS’s (and depends on them playing by their rules), the final score for this one goes to Apple. Though Apple got lucky.

Vista Similarity 5: Bundled Apps as New Features That Suck


Oliver and I may start to part ways at this one, although not that far.

All the standard home and media applications Apple bundles with their OS are really top notch in my opinion. In fact, I buy iWork in addition to iLife. It’s Apple’s Pro applications that use a interface that I find very dated. And ugly.

But the feature we all seem to gripe on is Time Machine.

My first experiences with Time Machine were horrible. The system would seize up, and, well to be fair, I have to admit that this all went away after I did an Archive and Install, rather than the Upgrade in place over my existing patched OS Tiger.

And, while I applaud the concept of Time Machine, I don’t like that I can’t force it to kick off when I want. Or that I can’t easily point it at a common server. Or use it wirelessly.

But my biggest beef is why in the world Apple just didn’t hold off, wait until ZFS was working the way they wanted, and delivered something that managed things directly with the filesystem itself.

In addition to Time Machine, I find myself using SuperDuper and Carbon Copy Cloner to make quick, efficient backups, that are also bootable.

What I think Oliver might have missed is a subtle difference.
– With Time Machine, everything is backed up.
– Not that Time Machine backs up everything.

Let’s cover that a little closer. Time Machine does do a full backup, but then everything from then on out is incremental. And intelligently so. In fact, you can even go wandering around the files on the backup disk directly, should you choose to.

The way I’m reading things is that the review gives the impression everything is always backed up. That’s just not so.

Would I like to be able to tell Time Machine to only back up what I want it to? Yes. Please.

Would I like to only delete the things I intend to? Of course. But, realistically, it’s when I delete an important system file, and Time Machine has a copy, that I’ll suddenly become more forgiving of why it does what it does.

All his GUI gripes with Time Machine are dead on. However, when you get Time Machine working (via a clean Archive and Install – which keeps your preferences, data, and applications, btw), it does work as advertised.

It’s close. Time Machine’s integration is trivial. But over all, I think Vista’s backup, is better in the long run. Vista wins this round.

Oliver, I think, in this case was guilty of throwing the baby out with the bathwater. To be ticked off at the first version of a new application that could have been better, is justified. To extend that assessment to all bundled apps, as he does in his title, is not.

What the world hates is that after buying the OS, you still can’t do much with it. With Apple you can. And, with most Window machine purchases, you get a lot of crapware. Apple, you don’t.

In fact, I think Apple misses the mark. QuickTime Pro should be bundled with the OS, and if they were really on top of things, iWork as well. I’d gladly even pay the full retail price rolled into the cost of the machine. Why? Because can you image if everyone’s machine out of the box shipped with software that could do Office related stuff? You’d have a killer do-all platform from time the machine was powered up. There’s no way Microsoft could do that.

So, while Vista won this round, I’m gonna give Apple half-credit, since I think it was an unfair contests.

Walt’s Final Score


Apple 3.5 / 5; Vista 1 / 5.

I’d still rather use OS X Leopard than Vista any day of the week.

Walt gives OS X Leopard a thumbs up, even though it still needs some work.

Five Things I Can’t Do with OS X Mail’s RSS

With the new OS X release of Leopard, there were amazing improvements in Mail. One of which was the addition of RSS feeds. Here are five things I can’t do with RSS in Mail that I wish I could… Apple, are you listening?

I notice with OS X 10.5 (Leopard)’s new Mail integrated RSS reader, once I have a feed there’s a few minor annoying limitations that aren’t available.

OS X Mail RSS1) While I can review what the RSS feed URL is by hovering over it, I can’t copy it to the clipboard.

2) If the RSS feed location changes, I can’t change the feed’s URL.

3) I’d love to be able to drag the RSS icon to a browser and have it open the page.

4) Or, I’d like to be able to right click the feed and have it open it in a browser or my default RSS reader (NetNewsWire).

5) Drag the RSS feed icon, or an article from the feed, into an open Mail message to share the URL.

I hope Apple will enhance the feature capabilities soon.

Four Complaints of Leopard

OS X 10.5 – sweet, sexy, cool… and four annoying problems that are bound to get fixed soon.

Before we begin, let me say that I like Apple and that I had a very smooth transition to OS X 10.5 Leopard. I had the foresight to upgrade all of my applications, thanks to Version Tracker Pro pointing out what needed upgrading. And, I also had the foresight to update Unsanity’s Application Enhancer before doing the OS X upgrade.

Things couldn’t have been smoother. Shortly after inserting the disc, I was running the upgrade, and my desktop, data, applications, and settings were all preserved perfectly. I’ve never had that kind of experience with Windows.

That said, there are four complaints I have regarding Leopard.

UPDATE: Phil Wherry points out that I overlooked the obvious: Command-Drag the .Mac icon off the toolbar. This works with any icon.

Additionally, there’s some serious value in looking at notMac.

One: Dot-Mac is in-your-face. There’s a new icon in the status bar at the top for .Mac, and you can’t get rid of it with the preference pane unless you sign up for a trial account. Then the preference pane gives you the option.

Come on Apple, that’s so unlike like you.

Here’s why I don’t want .Mac in a nutshell: I have Linux, and it does a better job. I can secure FTP, secure copy, and rsync; it has Apache, Lighttd, and a host of other web servers; it has Sendmail, Postfix, and other mail options; it has DNS, ssh, X-Windows and other services; it has Samba; it has multiple accounts, with permissions; and it has far, far, far more than 10GB of disk space. For those of us with Unix experience and servers of our own, we don’t need .Mac, therefore, we don’t want it on our desktops. It comes across as an overly inflated service that can be mimicked by simple services included in the standard install of Ubuntu. And it’s free.

Sure, some people don’t know how to set it up, and they might want it, but don’t force it on my desktop.

Two: The Finder’s Sidebar has much smaller icons. Plus, for example, the desktop icon doesn’t mimic the desktop wallpaper I’m using. I liked large, findable, easily clickable icons.

Three: It feels like it boots slower. Yes, once I’m in it, it feels very snappy. And, intellectually, I know that a one time short wait is worth far more than perpetual ongoing stalls, though emotionally, to be honest, I haven’t gotten used to it.

Four: Stability. Yes, that’s right, I said stability. As in, it has problems.

My first experience was when someone handed me a disk with .JPG images dumped from their camera; a disc verify hadn’t been done, and unbeknown to me, it has a read problem with one or two files. Guess what – when cover flow hits them, it crashes the Finder.

Now, good on you for restarting the Finder, but I’d much rather it didn’t crash in the first place. At least my machine is still usable.

Which, incidentally, is more than I can say for Time Machine. It has serious glitches.

Using a directly connected firewire drive, I backed up my machine using Time Machine. And, as I worked, I let it run in the background.

Two problems there.

One, Spotlight appears to be finding things on my backup and on my main drive. Oh, that may sound handy, but not when you’re trying to launch an application. And certainly not when you right click a file and see two copies of things with the Open With… menu.

Two, Time Machine can sometimes take a good moment to backup the system. Especially if you’re using Virtual Machine technologies and your image file changes; that thing is huge. Time Machine dutifully starts to back that up, so I get up to take a break while it does its thing in the background. That causes the machine to fall into sleep mode, and that’s where the real problems begin.

When you wake the machine back up, Time Machine looks like it’s still backup up, but you’ve got just a spinner doing it’s thing. Worse yet, if you go to start any applications, they appear to start, bouncing the icon in the dock, but then nothing happens.

Almost.

According to both top and the Activity Monitor, a process is started, although the desktop doesn’t show any applications. You can see them with Command-Tab, but you can never get the application to come to the foreground. You can’t quit. You can’t force-quit. You can’t get rid of them from the command line using kill, either. Any open applications you have do continue to run, though.

That’s when you discover that your log has crazy reports about messages being sent to selector 0, and then you find out that Apple / Restart… doesn’t work either. Killing tasks with Command-Option-Esc simply reports “Application Not Responding.”

The solution, known to many Unix folks, is to ssh into your machine from another system, and issue the sudo shutdown -r +0 command. That does work. It also gives the illusion everything was just fine on shutdown, so Apple doesn’t get an error report.

However, don’t use Time Machine, and all is well with the world.

Concluding Thoughts
Does any of this worry me?

No.

I’m certain that other users are experiencing the same thing and deducing what causes the behavior, and that everyone is filling out the report-this-problem-to-Apple dialogs that appear.

Most certainly, Apple with issue a patch or two, and by 10.5.1 or 10.5.2, all will be well, and applications will come out with minor updates to fix problems. All will be well soon enough, and each of these problems will get addressed.

While minor bumps are expected with any major new release, this is certainly a much better experience than what happened with us and Vista.

I’m sticking with OS X 10.5 to ride it out, but to my Mac friends and followers without solid Unix experience, I’d say don’t let go of 10.4 just yet. One more pass from Apple’s magic wand is still needed.

ASIDE: Third Party App Problems Encountered So Far
SnapZ Pro is using CGSCreateCString, CGSCreateBoolean, CGSReleaseObj, and CPSPostKillRequest; these are obsolete and degrades system performance.
Parallels is using a forked process, when it should be using exec().
Firefox is reporting memory deallocation issues.
Version Tracker Pro crashes when it quits.

UPDATE 27-NOV-2007: Well, those smaller icons have grown on me. I’m liking them now, and before where they just sat there, I’m using them more often. Booting still seems a bit slower, but realistically, I don’t now, and never did, really have to reboot the Mac.

Furthermore, as I write this, 10.5.1 has come out, as well as many package updates. Version Tracker PRO works fine, Firefox has had an update, as have a number of utilities. I’d have to sat the Mac is quite usable and stable.

My recommendation is not to do an Update, but either an Archive and Install, or a migration from another machine/backup. This seems to clear things up quite well.

A lot of people seem to be treating this as a bash the OS post. It’s not. It required some serious digging to find stuff that was a little off. Unlike Vista, which instantly tried my patience and provoked my anger for many months.