Mokka mit Schlag » Mac

Mostly the Migration Assistant in Mac OS X works, but there are some surprising things that don’t come across and have to be reinstalled manually. So far I’ve noticed:
(more…)

I spent yesterday rebuilding and repairing my main desktop Mac. Fingers crossed. It may be fixed now. It seems to have had some pretty serious volume structure problems on the main disk. The Finder kept hanging, and every time I did something that touched every file on the disk (like backing up) the process would hang. I had to boot off another disk to fix it, which meant I had to find my Tiger DVD and remember some old passwords. And then there was lot of time waiting around while files copied, Tiger installed, and TechTool tried to repair things. In any case it was quite boring and not very productive. I did catch up on my comic books though.
(more…)

Amazon is listing Retrospect 6.0 for the Mac as discontinued by the manufacturer, though they still have some in stock. Hmm, looks like maybe they just don’t have the new 6.1 version yet, because I do see that on EMC’s web site. Furthermore, I notice that “Customers with Retrospect 6.0 can use their existing license code and download Retrospect 6.1 for free from our Updates section.” No need to push the panic button just yet.
(more…)

Loop Rumors reports that “Unlike today’s Mac Pros, the cooling system will direct hot air through vents at the top of the machine, much like Apple’s Cube of yesteryear.”

I expect and hope that Loop Rumors is wrong. The problem with vents on top is that I (and many other users) put things there.

Putting the exhaust vents on top blocks useful space. By contrast the space on the back of the machine where the vents are now is relatively free.

Eddie Hargreaves has a nice write-up of nine Windows features Mac OS X should adopt. I agree (or at least don’t disagree) with eight of them. However the one I part company on is #5, “Refresh keystroke/toolbar button for Finder windows”. Eddie explains:

Nearly every major revision of OS X has touted an “improved Finder” and one of the improvements has been the updating of folder contents. But there are still occasions where a file has been updated and its appearance in a Finder window goes unaltered. Windows toolbars have a refresh button that can be used to update the contents of the window. Since Apple has already copied the concept of making Finder windows look and act like browser windows (forward/backward buttons) they should add a refresh or reload button. They wouldn’t even have to create a new toolbar button icon, since they could just use the one from Safari. They could even use the same keyboard shortcut, since Command-R is currently unused in the Finder. Ideally, a refresh button shouldn’t be needed in the Finder at all, but we’ve seen four major revisions of OS X and it still hasn’t become unnecessary.

Sorry. That is totally the wrong solution to the problem, and totally a Windows way of thinking. You do not put an extra button in to make the computer do something it can and should do automatically. If there’s a problem with auto-detecting the need for refresh, then you fix the underlying problem so auto-refreshs happen automatically. You do not complexify the interface. The product is done when there’s nothing more to take out, not when there’s nothing left to put in.

Apple’s catching some flak for charging $1.99 (down from the $4.99 initially rumored) for turning on 802.11n functionality in existing laptops. They claim it’s the result of Sarbanes-Oxley accounting rules that prevent them from adding new functionality to an existing product. This interpretation of the Sarbox rules has been challenged,.

I’m not an accountant or a lawyer, but I suspect Apple’s wrong here. Regardless, though, I’m inclined to give them the benefit of the doubt in this case. I do believe Apple genuinely believes, rightly or wrongly, that Sarbanes-Oxley requires them to charge for this. However, Apple does have a dishonest track record of charging $20 shipping and handling fees for “free” updates. If they really want to be clear that this is just a technical fee they’re required to charge, not another scheme to extort money from customers to make an already purchased product work well, there are two things they should do:

1. Reduce the fee to $1.00. This is the generally recognized nominal price for indicating that you have to charge something, but don’t really want to. For instance, it is what juries award in damages when they want to indicate that the plaintiff is legally right, but is basically a putz and is wasting their time with a trivial suit they were largely responsible for in the first place.
2. Make sure the updater is not copy protected, and look the other way as it is freely distributed on file sharing networks.

$1.00 is still annoying, but I think that price would make clear to everyone that Apple really doesn’t want to charge for the update. They’re just being forced to by their interpretation of the Sarbanes-Oxley laws.