The Robservatory

Robservations on everything…

 

Create a savable list of 32-bit apps

Apple has announced that 32-bit apps have a limited future on the Mac: They’ll be fully supported in this fall’s High Sierra release; macOS’ 2018 release (“Really High Sierra”) will “aggressively warn” users about 32-bit apps, and I would assume, they won’t work at all in the 2019 version of macOS (“That Was My Skull!”).

But how do you know which apps on your Mac are 32-bit and which are 64-bit? MacObserver has an article that discusses the easy way, via the System Information app—just look in the Software > Applications section, and you’ll be able to see a list of apps and a 64-bit Yes/No column. But seeing the list is all you can do—you can’t easily save the list for future reference, for instance, nor can you copy/paste the info to another app.

So here’s a geekier solution to generate a list of your 32-bit apps, saved into a text file for easy future reference. Open Terminal, and paste this command:

system_profiler SPApplicationsDataType | grep -B 6 -A 2 "(Intel): No" > ~/Desktop/non64bit.txt

This does the same thing as the System Information app, but it dumps the data in text form; the greater-than sign redirects the output to a text file named non64bit.txt, saved to your desktop. The grep is used to show only the 32-bit applications (the full line reads 64-Bit (Intel): No), and the -B and -A options are added to capture the lines before and after that line in the output.

This is probably not overly useful to most people, but I wanted a way to capture the list of apps, as I have over 290 32-bit apps on my machine, and it takes a while to run the System Information report each time.

Back to posting…after fixing a snafu

I actually intended to start posting again a few days ago, but I was running into a couple of issues with the site: It was incredibly slow (annoying, but survivable), and the editor box was missing when I added a new post (which made posting quite tricky). I tried the usual troubleshooting steps—made sure everything was updated, disabled plug-ins, even briefly changed the site’s theme to see if it was a theme issue. No luck with anything.

Then I enabled WP_DEBUG on the site, which is something you should never do on a live site, as it will fill every page with tons of mostly meaningless warning and error messages. But in my case, I had to see what was happening when I tried to load the new post page. What I saw was troubling…

WordPress database error: [INSERT command denied to user '#######'@'###.###.###.###' for table 'wp_options']
INSERT INTO wp_options (option_name, option_value, autoload) VALUES ('_transient_timeout_jetpack_sync_constants_await', '1502403204', 'no') ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)

WordPress database error: [INSERT command denied to user '#######'@'###.###.###.###' for table 'wp_options']
INSERT INTO wp_options (option_name, option_value, autoload) VALUES ('_transient_jetpack_sync_constants_await', '1502399604.7325', 'no') ON DUPLICATE KEY UPDATE option_name = VALUES(option_name), option_value = VALUES(option_value), autoload = VALUES(autoload)
...
...

This went on and on, with screenfuls of such errors. Uh oh. Web searches found lots of possible causes with fixes, but none that worked for me. So I logged into 1and1 to check on the database…and I didn’t have to get any further than the summary screen to see the problem, as revealed in the image at right: The site’s database was using 150MB of the 100MB allocated to it—whoops!

100MB is not a lot of space, and it’s not what I get when I create a new database on 1and1—the limit is now 1GB. So why so puny? Basically because I’ve had robservatory.com since 2005, and never ever updated the database! I have no idea how long it’s been over the limit, but apparently it was finally over the limit enough that no more data could be written to the database.

The problem is that 1and1 can’t just bump the size of the database; you have to create a new one and migrate your data over to it. Thankfully, that’s not overly hard (read the rest if you’d like to know how I did it; documented for my own future sanity). After I moved to the new database, my edit window was back (hooray!), and as an added benefit, the site got much faster: The database is now hosted on an SSD, and the site’s not throwing 5,000 errors per second any more.

And now, I can get back to real blog posts.

(more…)

A useless analysis of macOS (OS X) release dates

Updated and republished for the macOS 10.12.6 release; 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.12.6, as of July 19, 2017.

Note: Click the ⓘ symbol to read Apple’s release notes for a given update.

(more…)

Two ways to navigate column-view folders in Finder

If you use a column-view Finder window, and prefer to use keyboard navigation, here’s a trick you may not be aware of—even though this dates back to the original release of Mac OS X. If I hadn’t started the Mac OS X Hints site, I doubt I would’ve known this…

To drill down into Finder folders via the keyboard, you use the Right (down) and Left (up) Arrow keys-don’t worry, that’s not the tip, because that’s totally completely obvious. The tip is this: After navigating into a given subfolder (and optionally selecting an item in that folder), the Shift-Tab key combo will navigate back up, but leave your “path” to the subfolder visible. Think of this like a “breadcrumb” trail that shows your navigation. (By comparison, if you use the Left Arrow, Finder “closes” each folder as you exit it, leaving you with nothing selected once you reach the top.)

One you’ve used Shift-Tab to navigate all the way back out, pressing Tab will navigate back down the highlighted path. Alternatively, pressing the Right Arrow key will jump immediately to the rightmost-selected item. Here’s how that all looks in action—first is the normal arrow key navigation, then navigation using Shift-Tab and Tab.

You may not need/want the breadcrumb path all the time, but when you do, just remember to Shift-Tab your way out of the current folder. Using the arrow keys and the Tab/Shift-Tab keys together provides two complementary methods to navigate your column-view Finder windows.

The right tool for a (floor) stripping job

I haven’t posted here the last couple days; between work, family, and a little remodeling project, time has just vanished. And as my blog reflects things going on in my world, today’s post is decidely non-tech related: It’s about the remodeling project.

We’re re-doing our kids’ bathroom with a mix of our own work and outsourcing the stuff I know I’d do poorly (tiling the shower, refinishing the tub). On the “own work” side of the ledger was “remove old linoleum floor,” as we have some water damaged sub-floor to replace in the shower area, and we hated the linoleum in general. When I peeled up the linoleum, it left huge sections of glue and paper backing behind:

I had no idea how to remove this gunk, so I bought a few tools at Home Depot: A carbide-tipped scraper that looked like a larger putty knife, a “pull to scrape” device, and a heat gun.

(more…)

Selective pruning of old rsync backups

In yesterday’s post, I described a couple rsync oddities, and how they’d led me to this modified command for pruning old (older than four days) backups:

find /path/to/backups/ -d 1 -type d -Bmin +$((60*4*24)) -maxdepth 1 -exec rm -r {} +

After getting this working, though, I wondered if it’d be possible to keep my backups from the first day of each month, even while clearing out the other dates. After some digging in the rsync man page, and testing in Terminal, it appears it’s possible, with some help from regex.

My backup folders are named with a trailing date and time stamp, like this:

back-2017-05-01_2230
back-2017-05-02_0534
back-2017-05-02_1002

To keep any backups made on the first of any month, for my folder naming schema, the modified find command would look like this:

find /path/to/backups/ -d 1 -type d -Bmin +$((60*4*24)) -maxdepth 1 -not -regex ".*-01_.*" -exec rm -r {} +

The new bits, -not -regex ".*-01_.*" basically say “find only files that do not contain anything surrounding a string that is ‘hyphen 01 underscore.’ And because only backups made on the first of the month will contain that pattern, they’re the only ones that will be left out of the purge.

This may be of interest to maybe two people out there; I’m documenting it so I remember how it works!

How to not accidentally delete all your rsync backups

With my Time Machine-like rsync backups running well, I decided it was time to migrate over the cleanup portion of my old script—namely, the bit that removes older backups. Soon after I added this bit to my new script, though, I had a surprise: All of my backups, save the most recent, vanished.

In investigating why this happened, I stumbled across two rsync/macOS behaviors that I wasn’t aware of…and if you’re using rsync for backup, they may be of interest to you, too.

(more…)

Kwikset’s smart lock may require another purchase

Just a heads-up for anyone thinking of installing the well-reviewed Kwikset SmartCode 916 Touchscreen Electronic Deadbolt (and probably other similar Kwikset locks): Check your current deadbolt installation to see if you actually need more than what’s included in the box.

In the box is one deadbolt (the “A” in the image at right), which assumes your deadbolt screws into a chiseled cutout in the edge of the door. But if—like me—your deadbolt isn’t screwed into the door but just inserted in place, you need “A2,” a drive-in deadbolt. This part isn’t in the $190 lock kit, nor is it sold (best as I could tell) at Home Depot or Lowes or Ace Hardware.

Check your door before you order your lock, so you can add on a drive-in deadbolt if your door is non-chiseled. Me, because I didn’t know about this, I didn’t check. So I made a 40-mile round trip to Home Depot for a chisel set, then spent an hour chiseling out the door so the included deadbolt would fit.

Mission accomplished, but I think it’s pretty dang cheap of Kwikset to not include both deadbolt styles in a $190 lock kit! (Or perhaps even better, they should design a deadbolt with a removable screw-in plate, then one deadbolt would serve all customers.) So, yea, I had a frustrating Sunday morning!

Frankenmac 2017: Fix distorted images at power on

When I originally set up Frankenmac 2017, I did so using an old 1920×1200 monitor, and everything looked fine from power on through booting to macOS.

But then, when it came time to get Frankenmac ready for production use (much more on that in a future post!), I connected it to my widescreen Dell 4K display, and was greeted with the ugliness that is a stretched Apple, as seen at right. This problem would fix itself relatively quickly during the boot process, but it was annoying.

Even more annoying was that the same distortion was present in the Clover boot loader that you see every time you power on the machine. In light of all my other issues, solving this problem was near the bottom of the priority list. But once I’d done everything I could on that front (again, more about that soon), it was time to tackle the distortion issue.

The solution turned out to be relatively simple, though not even vaguely describable as obvious. After much web searching, I wound up in this forum thread, where I found many possible solutions. Some seemed incredibly complex, but finally, on page four, I found a simple fix that worked—no more distortion, in either the Apple logo or the Clover screen:

If you’re experiencing distorted images on your hackintosh, here’s the fix that worked for me:

  1. Power up and enter BIOS (usually by hitting the Delete key)
  2. Find the Windows 8/10 Features setting—on my Gigabyte motherboard, it’s in the BIOS Features section. Set it to Windows 8/10
  3. Once you do step one, a new option, CSM Support, will show up. Set it to Disabled.
  4. Confirm that Secure Boot is set to Disabled.

And that’s that—with those changes (for me at least), the distortion was gone. As a side benefit, the boot screen is at the full resolution of the display, so there’s no more jaggies and everything looks properly scaled. Ah, correct aspect ratio bliss!

The Robservatory © 2017 Built from the Frontier theme