On Parallels’ site, when I clicked the “Try It Free” button, I was greeted not with a download, but with a dreaded email harvester:
Unless I was willing to provide an email address, I was not going to get the demo. To Parallels’ Marketing department, I’m sure this is viewed as a huge win: “Look, if we require an email address to get the demo, we’ll build a massive mailing list of potential buyers!”
But to a prospective customer, what this harvester says is “we really don’t care about your experience, we want to harvest your email address.”
An email harvester is only as useful as what it harvests. And from me, and I suspect many others, it harvested a “I only use this for junk mail” email address. So while Marketing is collecting a huge list of email addresses, that list is littered with any number of useless addresses.
Contrast this approach with VMWare’s Fusion demo download: Click one button, and the download begins. In the past, VMware also collected email addresses, but it seems they’ve realized that building a huge list of mainly worthless addresses is, well, worthless.
Unfortunately for Parallels, using the demo is even more annoying than downloading it, “thanks” (again) to the Marketing department.
After getting my iPhone 6 in early October, I was initially excited by all the cool tech in my new phone. Until I tried to sync it, that is. I eventually got so frustrated that I emailed Tim Cook for help. From that email, I wound up talking to Apple’s engineers, who eventually solved my sync issues—it turns out they were related to duplicates of long-ago-purchased songs.
And for a while, things were great in iPhone 6 land. Then I ripped a few new CDs, and noticed that they didn’t show up on the phone. Uh oh. Even worse, when I looked at my iPhone in iTunes, the Music section contained hundreds, if not thousands, of the dreaded gray dotted circles.
This seemingly innocent symbol means that the indicated song did not sync—the information about the song made the journey to the phone, but the song itself did not. Argh! Read on to see how I muddled through this issue, with some advice that may, or may not, help you with your own sync issues.
If you don’t want to read everything, here’s a tl;dr version:
My iPhone sync issues returned, along with a huge-fake-but-limiting amount of data shown in Other.
There’s a known-to-Apple “very slow performance” issue in iOS/iTunes that can make some iPhones sync very slowly (fixes have been made, but not yet released).
A factory restore failed to complete until I rebooted the iMac.
After the restore, the sync worked, but I still had a huge Other category.
After the iOS 8.1.1 update, the huge Other category vanished.
I had to manually unsync/resync a number of songs to clear their gray dotted circles.
It may help to do a voodoo dance, sacrifice three Nokia phones, and rub your stomach while patting your head before syncing.
Read on for the gory details…except maybe for that last item, which I totally made up.
Updated and republished for the OS X 10.10.1 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 OS X 10.10.1 as of November 17th, 2014. Note that this release marks the 84th release of OS X (counting major, minor, and released-then-yanked updates). Wow.
Note: Click the ⓘ symbol to read Apple’s release notes for a given update.
I’ll admit it: I’m a desktop image (nee wallpaper) addict. I love to use a wide variety of images, and change them often throughout the day, just to keep my work environment fresh. On my two external displays, I use iPhoto images—general photos on one, kid pictures on the other. But for the main iMac screen, I prefer to use photos taken by others—typically stunning landscapes and cityscapes from all over the world.
With the arrival of my 5K iMac, however, my existing collection was no longer sufficient. Yes, they were all 2560×1440 images, which matches the “apparent” resolution of the Retina iMac. But in order to make that image fill the Retina iMac’s screen, it’s first scaled up to 5120×2880, then displayed by OS X at 2560×1440. As a result, my desktop images aren’t nearly as sharp looking as they were on my old 27″ iMac’s display.
As an example, here’s a segment of two versions (2560×1440 and 5120×2880) of the Sydney Skyline, as screen-captured when set as my Retina iMac’s desktop picture. As you move the divider bar right, you’re revealing more of the 2560px version; move it left, and the 5120px version takes over.
After scrolling back and forth a bit, you might be thinking these pictures are identical, and I’m just seeing things. While I may be seeing things, the pictures are not identical. (Compare some closely-spaced lights and the crispness of vertical lines in each image to spot the differences.)
Read on for a closer look at the image, which really shows what you’re losing by using a 2560x1440px desktop image on a Retina Mac…as well as a list of places I’ve found that have 5120x2880px images available.
For those who aren’t familiar, Console (found in Applications > Utilities) is an application that shows you what’s happening beneath the lovely skin of OS X. Open the application, and you’ll see a combination of status and error messages from any number of sources.
If you’ve never looked at Console before, you might be surprised by just how much stuff gets written there. But with the release of Yosemite, things have really taken a turn for the worse—the amount of stuff written to Console is greater than I recall for prior OS X releases.
As a test, I set up a new Yosemite virtual machine, installed ScreenFlow (and nothing else), then launched and interacted with a number of Apple’s apps for two minutes while recording the screen. The results are quite sobering; here’s what two minutes of Console logging looks like, reduced to a 10-second movie:
As you can see, there are a lot of Console entries in just two minutes.
Most cloud services tell you that their data stores are safe, that your data is encrypted in transit and on their drives, that employees don’t have access, etc. For the vast majority of the stuff I store in the cloud, this is more than good enough for me—the data isn’t overly sensitive, and if someone were to hack their way in, all they’d get are a bunch of work and personal writing files and some family photos.
For other files—primarily financial and family related—those assurances just aren’t enough for me. But I still want the flexibility and security that comes from having a copy of these files in the cloud. So what’s a paranoid user to do to take advantage of the cloud, with added security, but with a minimum of hassle?
The solution I came up with involves using local encrypted disk images and a shell script. Using this script (and some means of scheduling it), you can automatically encrypt and back up whatever files you like to a cloud service.
I happen to have two external drives connected to my iMac—one that reads and writes the usual mix of CDs, DVDs, etc., and another that includes Blu-Ray playback (but not ripping). Today I discovered that you can use both drives at once (sort of) to speed up multiple CD rips. Here’s how it works.
When you have two drives in iTunes, you’ll see one CD icon in the iTunes 12 bozo bar—that’s my name for the row of device controller buttons seen at right.
Click on the CD icon, though, and you’ll see both inserted discs are available:
There really isn’t a trick to using two drives at once in iTunes, other than saying “Yes” when this dialog appears onscreen:
iTunes won’t actually rip both CDs at once, but it will queue the second CD up, and start ripping it automatically when the first one finishes. As soon as you see that changeover, click on the CD icon and switch to the just-imported CD.
Eject the just-imported CD, insert the next CD to rip, and say “Yes” again when iTunes asks if you’d like to import it. Repeat as necessary, until you’re done. I imagine that if you had three CD drives, this would work just as well—I can’t test that assumption, though.
While not fully automated batch ripping, this process does let you make relatively quick work of a stack of CDs—for those of you who (like me) still prefer such relics of a prior age.
Note: The following is my unofficial eulogy for Mac OS X Hints; IDG has not announced any plans regarding the site, though I would hope they’ll leave it online, even if no new hints appear in the future. The site is now officially in read-only mode; there will be no new hints. So it’s officially comatose, at least.
While it can be hard to tell exactly when a web site has died, the signs are fairly obvious. It’s been over 45 days since the last new hint appeared on the site. There is no way for new users to sign up for an account. There’s been one new comment posted in the last two days. A sidebar box proudly proclaims Latest Mountain Lion Hints. The site design, logo, and icons were last updated when I worked for Macworld, over four years ago. To paraphrase a Star Trek character, “it’s dead, Jim.”
To be fair, it’s a bit more Monty Python “I’m not dead!” than officially dead, but really, the site is a dead man walking. Now that I’m done with movie analogies, let me explain why the passing of Mac OS X Hints isn’t a bad thing. (Note that Mac OS X Hints’ passing is in no way a reflection of its management by Macworld. In fact, the opposite is true: I believe the site would have ceased to exist years ago without their involvement.)
The simple truth is that the need for OS X hints has tapered off to near zero over the last 14 years. And that’s a good thing.
Fourteen years ago today, I launched Mac OS X Hints, with this simple post. The Mac OS X 10.0 Public Beta was only a couple months old, and many Mac users (myself included) were feeling lost in the land of Unix and Terminal. (Despite anything Apple said at the time, Terminal was very much a required aspect of using Mac OS X in those early days!)
At the time of launch, I knew nothing about content management systems or PHP; I knew enough HTML to be dangerous, and very little about anything else—including design, as you can see from the image at right.
That image, courtesy of the Internet Archive’s Wayback Machine, was taken one month after launch. Could it be any brighter and uglier? Probably not. While I did many things wrong during that launch, I did get a few things right…
The site was all about the community; it was my intent from day one that it would be a users helping users site, not a “me telling the world what to do” site.
The content management system I chose, Geeklog, has proven to be very long lived—fourteen years on, and it’s still what powers the site. In all that time, we had (I believe) exactly one hacking incident. Not bad.
The site had a laser focus on hints; I’d do a pick of the week, but outside of that, it was all about the hints.
In looking back, never in my wildest dreams did I imagine the site would flourish to the point where it would actually change my career. But it did, and for that, I’m eternally thankful to everyone who helped make macosxhints.com what it was. So happy birthday, Mac OS X Hints!
If there’s one downside to my new Retina iMac, it’s that it completely lacks FireWire ports. While my main data storage is a Thunderbolt RAID array, all my backups (Time Machine, offsite drive, boot drive clone, and extra paranoid backups) are done on FireWire drives.
My setup precludes using Apple’s Thunderbolt to FireWire adapter. (Because I use two external non-Thunderbolt displays, they end any sort of chaining capabilities. With some rewiring and an expensive Thunderbolt dock, I can sort of work around that problem—but those docks are pricey.)
The money-is-no-object solution is, obviously, to replace all the FireWire drives with Thunderbolt drives. Given I drained the computing budget to purchase the Retina iMac, that’s not going to happen any time soon. ($400 for a 4TB drive, and I’d need three of them plus a smaller drive for the boot clone.)
After some digging, I managed to convert from FireWire without buying new hard drives, and spent just over $100 in total. The solution? The more-than-fast-enough USB3 bus in the new iMac.