I received an email from a user this morning, asking if Name Mangler was compatible with Catalina, as he’d seen a report telling him it was 32-bit. This was an odd thing to read, because Name Mangler 3 has been 64-bit from the beginning, way back in 2013.
I asked what report he was looking at, and he told me it was from the Legacy Software tab in System Information. I decided to see what the report had to say about my machine, so I launched the app (Option-click the Apple icon in the menu bar), went to the Legacy Software tab, and saw this…
Updated and republished for macOS 10.15.1; skip it unless you really really care about all the macOS releases. Originally published on November 14th, 2005.
Below the break is a table showing all major releases of macOS (previously Mac OS X) from the public beta through the latest public version, which is macOS 10.15.1, as of October 29th, 2019—the 129th release in total.
Note: Click the ⓘ symbol to read Apple’s release notes for a given update.
I have no plans to move my main iMac to macOS Catalina, at least for the forseeable future. There are two key apps I use—Fujitsu’s ScanSnap scanner software and the Many Tricks’ accounting app—that are both 32-bit. In addition, there are changes in Catalina relative to permissions that make it somewhat Vista like and slow down my interaction with the system. (My MacBook Air is my “production” Catalina Mac, and I have an older retina MacBook Pro that I use for Catalina betas.)
But Apple really wants people to update to Catalina, so they let you know about Catalina…constantly, it seems. In System Preferences > Software Update, you’ll see this…
And while that’s annoying, it’s not nearly as annoying as the red “1” dot they stick on System Preferences, which will stare at you forever. I complained about this on Twitter, and as is often the case, some very bright people had solutions to the problem.
I wrote about the Intel® Power Gadget back in 2015—it’s a little app that reports on your CPU’s performance in a few categories. I still run it on occasion, and noticed that my version was a couple years old.
I downloaded the new version, and discovered that it now has a built-in software update check (hooray, though it doesn’t appear to be automatic), they’ve improved the graphs’ appearance, and added a new Utilization chart; here’s a new (left) vs. old comparison:
If you like CPU stats, it’s great to get them right from the source, and I think the nicer-looking graphs (and new Utilization chart) improve on this already-useful geeky tool.
I recently bought a set of PowerBeats Pro, which I generally love (more on the headphones in a future post), but today, while trying to register my product with Beats, I ran into a clear example of form trumping function.
To register your Beats, you need the serial number; Beats provides a graphic that shows you where to find it…
Way back in the late 1990s, HBO aired an amazing miniseries called From the Earth to the Moon. Produced by Tom Hanks, the 12-episode series covers most of the key events in the Apollo program, including the Apollo 1 fire, the first moon landing, the Apollo 13 crisis, and much more. In total, 30 of the 32 astronauts in the Apollo program are represented onscreen during the series.
I’ve watched it at least a half-dozen times, and up until this summer, every viewing was at DVD resolution—eventually upscaled on higher-resolution TV sets, but still not the greatest video experience.
This summer, however, HBO re-released the series after remastering it in HD. They also reworked many of the special effects to take advantage of advances in that field over the last 20 years. If—like me—you’re a physical media person, you can pick it up for only $23 from Amazon…or if you’re fully digital, you can get it from the iTunes Store for $30. (Yes, a physical copy with media and packaging and shipping1and it includes a digital copy! is $7 less than a series of 0s and 1s written to a file. What a wacky world we live in.)
The visual changes are dramatic, as you can see in these shots from the two versions.
Warning: The following is nothing but a rant—no charts, no photos, nothing but text—about a piece of security absurdity I ran into the other day. I am 100% in favor of strong security in general regarding financial matters, but when it’s false security that does nothing more than inconvenience legitimate users, that’s when I get mad…and that’s exactly what this was: a security absurdity.
My daughter Kylie recently got a part-time job; her employer uses ADP to process its payroll. When her first check arrived, it was actually a debit card—which we didn’t want to use—so she had to write herself a check (using a blank they provided), which she could then deposit.
Because Kylie had a busy day ahead of her (school then work then a post-work thing), I told her I’d write the check for her, then she’d just have to sign and deposit it. But to make the check usable, I needed a six-digit authentication code that ADP provides via a phone call. And that’s when I entered a hellhole of security absurdity thanks to ADP…
While it’s not the world’s loveliest box…ok, so it may be the world’s ugliest box…
…it’s been rock solid since day one. However, it’s aging and its CPU won’t be supported in an upcoming pfSense release, so I decided to replace it. (That way, I’ll have a spare if the new one breaks…at least until that unsupported version of pfSense is released.) Here’s the new box…
That’s a Protectlifanless Firewall Appliance with a quad-core Celeron J3160 CPU, 4GB of RAM, and 32GB of storage. And yes, it’s just a bit smaller and more elegant than my old box—the entire thing is roughly the size of my old box’s external cooling fan.
Say I’ve resized a window to the dimensions I want. Is there a way to figure out what these are so I can create a resize action in Moom?
Basically, the user wants to save a window size as a custom action, to make it easy to reapply that action to any window. (If it were just one window in one app, you could use Moom’s Save Window Layout feature to save that layout for easy recall.)
There is a way to see this info in Moom, but it requires enabling our debug log and digging through a bunch of output. As an easier alternative, I was certain that AppleScript could do this; I fiddled a bit on my own, and did some web searching, which led me to this thorough post on StackExchange.
Using the very first bit of the first script there, I came up with this version:
Of course, me being me, I decided I’d spend a couple hours making it more useful, even though I probably won’t use it all that often. So I modified it to work for whichever app is frontmost, and made it run from Keyboard Maestro. I then assigned it a gesture trigger with my mouse, so I can easily see any window’s dimensions with a simple mouse movement.
We were fortunate enough to have an Apple ][ in our home, and I remember reading Softline for their game reviews and ads for currently-released games.
It was those ads that caught my eye as I browsed a few issues. Consider Missile Defense, a fun semi-clone of the arcade game Missile Command. To give you a sense of what games were like at the time, here are a few screenshots from the game (All game images in this article are courtesy of MobyGames, who graciously allow use of up to 20 images without prior permission.)