Before the Shadow Play

Category: OS X

  • Keep OCLP up to date, or recovering from an overenthusiastic software update

    I had the misfortune to have to learn this (and how to fix it), so I’m documenting it here for the next person who does this to themselves.

    We open on a Macbook Air 2012, updated to Sonoma 14.0 with OCLP. All is well. The machine runs…okay. It would probably be happier on Ventura, or Monterey, but because of reasons, I had updated it all the way to Sonoma so that there was no question of compatibility with the primary machine it was replacing while I was on travel.

    I used the machine on travel, and definitely found that it’s not quite up to the task at Sonoma, to be dealt with at a different time. The real issue was that I did not update OCLP to 1.5.0 as soon as that release was out. This meant that when Sonoma 14.5 was available and the machine auto-updated…it broke.

    Symptoms were that the trackpad and keyboard worked right up until login completed, and then did not work at all. Couldn’t run the browser to download the OCLP update, nada.

    Normally, I’d shrug, erase the disk, and reinstall, but this was a bit of an issue because I had files that I wanted to get off this device. (Yes, I know, I should have had backups, but I worked on the plane while I had no internet, and I hadn’t had the machine up long enough for Backblaze to finish a new incremental before the software update ran.)

    I tried a number of things: safe mode, doing a reinstall from Internet Recovery (we’d like to install El Capitan! sorry, your disk isn’t usable because I don’t recognize this filesystem)…and got nowhere. This was beginning to look bad.

    Then I remembered I had a Carbon Copy Cloner backup on one of my externals. Hm. Thought this was the Air’s Sonoma, but seems to be Mojave from my Macbook Pro 2012. Trying to boot it can’t be worse than what’s going on now, so booted, held down option, and there was “Mojave” in the picker list. Chose it, crossed my fingers…and it booted!

    I was able to download the latest OCLP (1.5.0), install it, run it, reinstall OCLP to the Air’s disk, and most importantly, reinstall the root patches. After that it was clear sailing: I shut down, restarted from the Air’s internal disk, and I was back in business on Sonoma 14.5.

    The primary, most important lesson: run OCLP periodically and make sure it’s up to date! If I had done that as soon as I got home, the 14.6 upgrade would have Just Happened and everything would have been fine.

    The secondary, also important lesson: disable automatic updates on your OCLP machines, and don’t update until you’ve verified that the most recent OCLP is installed and handles the version of the OS that you’ll be installing manually when you’re ready.

    The third lesson: after you have a working install of whatever OS with OCLP, make a bootable backup immediately. If I’d had that to hand, it would have take 15-20 minutes to fix the issue. As it was, I spent almost a full afternoon trying to fix the installation before trying the Mojave backup that wasn’t even for the affected machine. (I think I used up my luck for a couple months on that one.)

  • OCLP experiences on a 2012 MacBook Pro

    TL;DR

    OCLP works fine, if you don’t forget your damn firmware password. If you did, persist even if the Apple Store tells you your machine is “obsolete”. Mobile Kangaroo San Jose rules. Oakridge Apple store, not so much.

    The history

    We’ve owned a 2012 MacBook Pro 15″ since about 2014, when Shymala finally outgrew her 2009 MacBook Air and needed a faster, bigger, and better machine. We chose the 2012 MBP because everything was still upgradable (memory and disk). She used it for a good six or seven years before she wanted to upgrade to something lighter and (most importantly) faster — OS and application upgrades had vastly slowed it down, and it ran hot most of the time.

    First upgrade

    The machine sat around for a couple years until I got let go from WhiteHat and I realized I had no personal computer at all. (Resulting in the loss of a lot of my personal files, sadly, because I did not learn the canonical lesson: a work computer is not “yours”.) So I got the machine out of storage, and yeah, it was slow, and not up to what I wanted to do with it. I upgraded the memory to the theoretical max (16GB, which it supports, just not officially), and swapped out the drive for a Crucial 2 TB SSD.

    It was like a brand new machine! It ran the then-current OS perfectly. It did run a bit hot sometimes, but it was fast enough to compete with her old machine, and nearly as good an experience as the new laptop from ZipRecruiter (also an Intel machine in the early days of my tenure).

    We had added a firmware lock to the machine because there was some concern about it getting stolen while Shymala was living in Brooklyn, and we wrote it down. Or so we thought. OS updates were installing, everything was fine up to Catalina. The machine was left behind on updates past that, but generally this wasn’t an issue, as it was still doing what was needed.

    The first stirrings of trouble were when Big Sur came out, and the new version of Xcode required it. This made the machine less useful by quite a bit. I could still use it for streaming and music production, and it ran Second Life fine; Photos worked, Acorn worked, so basically it was still great for everything but iOS development. I didn’t really need to do any development at the time, as the RadioSpiral app was working and stable, so I left it.

    Come 2023, I was laid off from ZipRecruiter. They were nice enough to let us all keep our laptops, and in the interim I’d gotten an M1 upgrade, so I was okay for staying up to date with the OS and Xcode.

    The scramble and the block

    This came in handy in October 2023, when I got a note from Apple that said, essentially, “dude, you’re not updating your app, and if you don’t do it now, we’re going to remove it. You have 90 days.”

    And I haven’t updated the app since Swift 3. Oops. I spent a couple weeks catching the app up to date and in the process I realized that I now had only one machine that I could do the work on. I needed to use Xcode 15, and the minimum OS was Ventura, two past Catalina. I was okay, because I had one machine that could run Xcode 15, but I thought I’d better see if I could come up with a backup. If something happened to the main machine, I was going to be SOL.

    Fortunately, Open Core Legacy Patcher was now available. We’d used it once successfully to update a 2015 Air all the way to Sonoma — ran Word and OBS beautifully, and that’s what we needed it for — but I didn’t want to waste the disk space it’d take to run Xcode on it (it only has a 256 GB SSD. On this machine, that is upgradeable, but I wasn’t feeling like doing the delicate surgery necessary, and it was really supposed to be dedicated to Shymala’s work while on travel. I am not a speedy iOS developer, and sharing a laptop is never a great experience.

    So now I needed to unlock the firmware on the 2012 Mac. At this point I discover that both I cannot remember it and all the records of what I think it is are wrong.

    I go to the Apple website, and check with Apple support on what my options are. They tell me I need the original receipt. Well. It’s 12 years later and multiple moves, and I definitely do not have a copy. Fortunately my tier-1 Apple support rep was able to push this up the chain and managed to find the purchase order in the archives. (Side note: Apple level 1 support reps — at least the ones on chat — rule.)

    Good, we’ve crossed that hurdle. I set up an appointment at the Oakridge Apple Store — they’re in the neighborhood, so they’re by far the easiest to work with — and took the machine in. The receipt was fine, and the tech tried a couple time to run the unlock software, and couldn’t get it to work. He declared that the machine was obsolete, and that Apple couldn’t help.

    Well. That was a bummer. I went home, and put the machine aside for a while. A couple months later, when it was clear I’d be traveling to Malaysia, I came back and said to myself, “okay, level 1 support was sure this would work. I should try again, but somewhere else.” I chatted with level 1 again, and my rep was enthusiastic about getting it unlocked. She scheduled a call for level 2 to call be back…and I missed the call because of another meeting. No problem, I thought, I’ll call back.

    So I call back. Level 1 phone support is not the same as level 1 chat support. I’m sure the rep was doing her job as she was supposed to, but essentially she blocked me from level 2, told me my machine was obsolete, and basically to buzz off and stop wasting her time.

    This seemed like a major set back but I had another option up my sleeve.

    A little bit previously, we’d had Shymala’s LED Cinema Display fail to come back on after a power surge, despite it being post the surge protector. We’d taken that to Oakridge, and they declared it dead, and that it’d have to be replaced. We decided to try an indie shop just to see if they could do something the Apple Store couldn’t. San Jose Mobile Kangaroo was the closest non-Apple store, and we figured that if they could fix it it’d definitely be better than spending $4K to replace the monitor, or take a chance on someone else’s used one. Their techs were able to get it reset and working again just fine in less than a day, and it didn’t seem like they’d had any trouble at all.

    So the firmware reset seemed like something to try them for. Worst case they couldn’t do it either, and I wouldn’t be in any worse shape. Took it in, and by golly, they were able to reset it right after Apple gave them the OK. (I suspect it was because they used Ethernet directly instead of via a USB dongle, which was how the Oakridge store tried it.) At any rate, I had a fixed machine. It did run me $125, but that’s a ton cheaper than buying another machine that could run newer OSes.

    OCLP experience

    OCLP was not seamless on the 2012 machine. On the 2015 machine, it was dead easy: download the installer for the OS, run OCLP to build the installer USB, boot from the installer, install, machine reboots itself a few times, done.

    On the 2012 Mac, it was…bumpy.

    The USB stick built fine, but when I booted, I ended up at the recovery screen. Tried in safe mode. Recovery screen. I tried a couple other different things and ended up crashing my Catalina install to the point that I’d broken the boot record on the HD and had to use Internet Recovery to reinstall Catalina.

    Okay, well. Not great. Got the machine back up and tried again, this time with Big Sur, as I though maybe I’d tried to go too far too fast…still back at the recovery screen. Well, what the hell. Let’s try recovery. Pick an account, password…and “Install Big Sur from USB”. Well, shit. I could have tried this before! Okay. Chose that option — and Big Sur starts installing, and succeeds! Woo hoo!

    Conclusion

    I’ve now rebuilt the Ventura installer and followed the instructions, going through recovery again, and Ventura is now installing on the 2012 Mac. I’m going to finish up, port everything from the M1 Mac over to the 2012 one, verify it’s all working, and then I can delete the old Catalina partitions and just use Ventura on the new machine. [Note: while writing this, we’re on the third reboot after the initial install, all seems to be going okay. Fourth boot while writing that sentence, but I’m pretty optimistic]

    I probably could have gone all the way to Sonoma, but I’m going to stay backlevel for now. My strategy on the 2012 Mac is going to be “update as little as possible other than security fixes” unless something pushes me forward (most likely Xcode).

    I’ll have my backup machine, and I’ll feel safe taking the M1 with me on travel — and if at some later point I can’t upgrade the Intel Mac further, it’ll work fine as a Linux or BSD machine now that it’s unlocked.

    Also: if I do a firmware lock again, that goes straight into 1Password, which would have prevented 90% of all these gyrations in the first place. $125 is a bit expensive to learn that lesson!

  • Photoshop 2024: Clearing the “Recent” tab in the “New Document” dialog

    First, shout-out to ShineX Media for setting me on the right track for this.

    If you use modern versions of Photoshop, you’ve probably noticed that in the “New file…” dialog, there’s a “Recent” tab, which is the default one that comes up. If you’ve been using it to create files in different shapes and sizes and formats, you’ll notice that it gets pretty cluttered up, and it’s easy to accidentally, say, pick something with the right dimensions but wrong DPI and then waste a chunk of time working on an unusable document.

    Adobe has provided no built-in way to clear this. People have been asking since 2016 for a solution.

    The one documented on the Adobe site, go to the preferences and turn this version of the dialog off, is like the old joke:

    • “Doctor, my shoulder hurts when I raise my hand above waist level.”
    • “Well…don’t do that.”

    I mean, it’s a solution; it’s just not a very reasonable one.

    I spent a fair amount of time googling around and finally found a reference to Shine X Media’s video that explains how to do it for Windows; essentially you close Photoshop (very important to keep PS from just rewriting the file again), go looking through the AppData directory for a file named MRU New Doc Sizes (MRU is Most Recently Used), and remove it.

    On the Mac, this lives in "${HOME}/Library/Preferences/Adobe Photoshop 2024 Settings/MRU New Doc Sizes.json", and you can simply use the Go… option in the Finder to navigate to the Adobe Photoshop 2024 Settings directory and drag it to the trash.

    Again, make sure Photoshop is not running!

    This is confirmed to work fine on my 2024 install under Sonoma. Happy and clean open dialogs to you!

  • iTunes Swedish Death Cleaning

    If you haven’t heard of “Swedish Death Cleaning”, the idea is that when you finally do drop dead, it’d be polite to not saddle whoever is taking care of your stuff with a big job of “is this important? should I keep it? should I just give all this away, or throw it away, because it’s just too much?”. Also, living with just the stuff that actually means something to you on a daily basis, as opposed to “I may want this someday, so I’ll keep it in my live gathering dust and generating clutter.”

    I definitely need to do more of that in my physical life, but this weekend I embarked on it in my digital one. Like most people, when I finally had iTunes and no longer had an actually “how full are my shelves?” physical limit, I started hoarding music. I had a lot of stuff from my old CD collection, music I’d bought from iTunes, the StillStream library from when I was maintaining the music library for that station’s ambient robot, music from friends who’d lent me CDs, stuff I’d borrowed from the library and timeshifted into iTunes to listen to “later”, free releases from Amazon…basically a huge pile of stuff. Worse, I’d put all this in iTunes Match, so even if I cleaned out my library, turning iTunes Match on again would just put all the crud back.

    In addition, my partner didn’t have a music library at all because her internal disk on her laptop was too small to keep all of her work and optional stuff as well. There was an offline copy of her old music library, and it too had also grown over the years from music lent to her, music I thought she might like, etc. She wanted to be able to pack up her CD collection and put it into storage, and maybe get rid of some of it as well. So we needed to take our old libraries and clean out anything that we didn’t want, and then see what each other might have that the other person might want afterward.

    I spent a couple evenings last week ripping the CDs she didn’t have online yet into a separate library, so they wouldn’t be part of the existing mess, and then went through and did the following in a brand new library:

    • Anything she actually owned got copied in. iPhoto’s ability to let me photograph the discs on the shelf and copy the text off of them came in very handy to make sure i got them all.
    • Anything I didn’t find in the library on that pass got ripped into this new library.
    • The not-previously ripped CDs in the secondary library were copied in.

    At this point, she had a clean “definitely mine” library. Now it was time to clean mine up. I had done one pass already to strip it down, but I wanted to make sure that I both cleaned out my iTunes Match library and made a conscious decision, “keep or not” for anything in there that I didn’t already have in the stripped-down library.

    The easiest way to do this was to to create a brand new, empty library, and connect that to iTunes Match, after turning on the “I want lossless copies” option — this is apparently new in Ventura, and is very welcome. Once this synced up, I could download and copy in only things I knew I wanted to keep. This meant I would actually have to look at the music and say, “do I really want to listen to this again?”, but not having to pull it out of an existing library would help.

    In addition, my partner had asked me to give her a copy of music of mine that I know she likes; we share a liking for world music, and several different other artists. After a little thought, I came up with the following:

    • There’s probably music in iTunes Match that we both want, and there’s definitely music I want. So let’s do this:
      • Create a new folder on a scratch disk that will contain music to add to her library.
      • Do the same for music I want to add to mine.
      • Drag those into the favorites in the finder.
      • Drag the Media folder from my target library to the sidebar as well. This will let me quickly check to see if a given release is already in my library , and if it is I can skip downloading it altogether, unless I want to give my partner a copy.
      • As I process each release in the Match library, I do the following:
        • If my partner would like it, download it.
        • If I want to keep it myself, open a Finder window using the Media folder shortcut and check if I have it.
          • If I do, simply delete it from the iTunes Match library (which also takes it out of iTunes Match).
          • If I don’t, download it.
        • If I downloaded it, right-click on one track in the iTunes list, and “Show in Finder”. This pops up a new Finder window with all the tracks for the release in it.
        • Command-Click on the folder name in the top bar of the window and go up one level to see the release in its enclosing folder.
        • Drag the release folder to the sidebar aliases for the “music to add” folders as appropriate.
        • Delete the tracks in iTunes. This removes them from the iTunes Match library, and iTunes Match as well.

    This took the better part of two days to finish, but I now have two cleaned-up music libraries, and an empty iTunes Match. I am considering whether to retain iTunes Match, mostly because it’s not a “backup” — it’s just a convenient way to share music across my devices, and doesn’t guarantee I’ll get the original file back.

    I’ve probably lost fidelity on some of the tracks I added to Match, and it’s possible some of them now have DRM. I will do another pass at some point and see; I’m not sure if it really makes a lot of difference to me right now, but I can always play them through Audio Hijack and re-record them to remove the DRM if I decide I want to.

    We also wanted a list of “what you have that I don’t” for both the final libraries; I was able to do that with Google Sheets, but I’ll post that as a separate article.

  • Useful shortcut for cleaning up files

    Useful shortcut for cleaning up files

    The situation

    I’m in the process of moving from one computer to another. My old 2010 MacBook Pro is still running very well with a replacement SSD for its internal disk, but it’s stuck at Catalina and won’t be going any further, mostly because the firmware has a password which I’ve lost, and Apple can no longer unlock machines that old.

    So if I want to do development in a recent Xcode, and I very much do, I need to upgrade. One side-effect of my recent layoff from ZipRecruiter was that they let me keep my machine, so I now have a 2021 M1 Pro that will run Ventura. (It’s possible that I’ll never need another machine, given that Apple machines stay supported for ~7 years; in seven years I’ll be 73, and either dead or unlikely to be programming on a daily basis.)

    The problem here, though, is that the internal disks are considerably different sizes. The old machine’s internal disk was 2TB, because that was the biggest affordable SSD I could get at the time. The new machine’s disk is 0.5 TB, and a straight copy from the old machine to the new is not an option — the immutable law of storage is that if you have it, it fills up — so I need to clean up the stuff I’ve got on the internal and move it elsewhere.

    I’m using a mixed strategy for this:

    • Anything on the internal disk will be there because it has to be.
    • Anything I want to keep and be able to access, but that doesn’t need to be available right now is going on Dropbox. (I will have to back this up separately; I’m going to work out a script to back it up with Backblaze.)
    • Anything that I need quick access to will go on an external 2TB SSD, which I will back up with Backblaze.

    So far, I’ve done the following:

    1. Gotten a copy of my most recent backup of the 2 TB internal disk from Backblaze on a 4TB spinny disk. (Costs me the price of the spinny disk, but worth it.)
    2. Copied the failing spinny disk copy of my old backups to an external SSD. (In hindsight, it should have gone to the empty space on the spinny external; I may do that later).
    3. Started walking through the SSD copy of the old files to clear space on the SSD for the files I want from the Backblaze spinny disk.

    The actual meat of this post

    So fine, I’m cleaning up the SSD. The actual thing I want to note here is that I have a collection of ebooks on that external that I want to file onto a folder in Dropbox. Problem is that a lot of them are probably already there, and the drag, get the duplicate dialogue, dismiss it, trash the file process is tiresome on the hands. I discovered a significantly faster way, and I’m noting it here for anyone else who might be doing something similar.

    1. Open the source folder (for me, that’s the “books” folder on the SSD) and the destination (that’s a categorized and subfoldered “Books” folder on Dropbox).
    2. For each file in the source folder, use the Finder search field in the Dropbox window, limiting the search to just the “Books” folder on Dropbox, and start entering the name of the source book.
    3. If the book is there on Dropbox, you’ll find it — and if there a duplicates, you can clean up the duplicates right from the search results.
    4. If it’s not there then it can be dragged over to the appropriate folder in “Books” on Dropbox after clearing the search field.
    5. In either case, the book is now either found or filed, and can be removed from the source folder.

    This is way faster and easier on the hands than dragging and dropping the books one at a time.

  • I Only Wanted to Use My Time Capsule…

    I Only Wanted to Use My Time Capsule…

    A while back, I disconnected my Ethernet-connected Time Capsule because it was no longer working at all well for Time Machine backups. Somewhere in the update March of Progress, Time Machine became very sensitive to network drops. It may have been that way all the time, but we now have a lot more people with networks (I count 25 right now, as opposed to maybe 10 when I first moved here), and I think there’s simply more interference that Time Machine simply isn’t able to handle.

    I have found that regular mass-storage seems to work okay — I have an AirPort Extreme with an external 2 TB disk attached, and that seems to work fine as an external backup and organization disk.

    So I figured, why not switch the Time Capsule over to just being a big dumb network filestore, and not try to use it for Time Machine anymore? And it was kind of in the way when it was hard-wired, so setting it up like the Extreme should be fine.

    It was not fine.

    I was able to hard-reset it okay, but the current AirPort Utility (both on the Mac and the iPad) would not attach it to a non-Apple network. It was simply no go. After a lot of thrashing around, I found that AirPort Utility 5.6.1 should be able to fix this, but I couldn’t get it to run on my Catalina machine (I didn’t even bother to try on Big Sur). I did dig out my 2008 MacBook Air running El Capitan; surely this would do it!

    No, it didn’t. El Cap did not want to run it. I finally found BristleConeIT’s launcher utility for 5.6, and was able to get it to run on El Cap. Unfortunately, the straightforward “extend the network” (“join the network” was oddly not there) wasn’t available. I gave up and tried configuring it with no network, figuring I’d try later to fix it.

    This was the key to success: AirPort Utility diagnosed the settings as bad, and then led me through fixing them — and the fix process allowed me to join whatever network I wanted! I pointed it to my (non-Apple) Xfinity router, and said go. It restarted, and when I went to “Network” in the Finder, there it was!

    I launched the current AirPort Utility, which allowed me to access it and erase the disk. I chose to zero it out, and I’m waiting for that to finish, but so far, it seems like it worked.

  • “I just wanted to play Portal…”

    Prologue

    A friend on Facebook mentioned that he wanted to play some games on his Mac to help with an inner ear problem (practicing with virtual motion apparently helps with vertigo from real motion) — I had suggested Portal, as that’s a very changing-viewpoint-intensive game. Unfortunately, neither of us knew that Portal and Portal 2 are both 32-bit apps, and so they don’t run under more modern Mac OS X’s — anything past Mojave dropped 32-bit support. I said, “I’m sure there’s a way I could make this work.”

    Hubris.

    They don’t call it Boot Camp for nothing

    My initial thought was, well, of course most games run best under Windows; why don’t I set up Boot Camp on this machine? I’ve always wanted to see if it would work.

    Well, it might. But the machine I have to play around with — a 2011 MacBook Pro, the last one to have user-upgradable memory and disk — does not play well with modern versions of Boot Camp. See, modern versions of Boot Camp assume that you’ll be able to build a Windows installer USB stick and boot off that to install Windows. Boot Camp does build the installer USB stick; it’s just that my 2011 MBP can’t boot anything except OS X from USB. It could install from DVD, but a) I had no DVD blanks on hand and b) newer Boot Camp does not believe in DVD drives. There’s no option to tell it “please burn this to DVD”.

    I started exploring other options, trying to find one I wouldn’t feel like an utter heel trying to convince a not-so-technical friend to use, and there just wasn’t one. The closest I got was building a Windows VM, but that started getting messy and I decided if this was going to work, it needed to work with the tools that a typical Mac user would have, and shouldn’t require the installer to understand how to mount ISOs on virtual machines, and worse.

    Dual-wielding Mac OS installs

    My MPB can run 32-bit OSes, so I decided that the simplest possible option was create a second partition on the internal HD and install Mojave (the last 32-bit OS X) on it. This was a less complex option by far; the worst it required was a little work in Disk Utility to create the target partition, and issuing one command in Terminal.app to create the installer USB (which yes, my MBP would boot, since it was OS X).

    This article was really helpful in getting it done; I won’t repeat the whole thing here, but just mention the highlights:

    • Modern Mac OSes use APFS, and creating an extra APFS volume in free space on the internal drive only took a couple minutes.
    • Links to older version of OS X are available through this Apple support page; because Apple does get rid of older OSes, I recommend getting the installer you want and backing it up in case you ever want it again. Currently (as of May 2021), you can get Catalina, Mojave (the last 32-bit OS X), and High Sierra as installer apps from the App Store, and Sierra, El Capitan, and Yosemite as .dmg files, which install the installer. Older versions are probably available out there on the Internet, but they won’t be official Apple source.
    • Creating the installer is the one more-sophisticated step, in that it requires you to enter a command in Terminal.app to create the USB stick. That’s documented in this Apple support document; it’s only one command, so it’s not too scary.
    • Once you have a usable USB stick, it’s relatively straightforward. Boot the machine while holding down the Option key, and you’ll get a menu of disks to boot from. Pick the installer USB. You go through a couple screens to get to the install disk; pick the APFS partition you added.

    The result

    That’s pretty much it; wait for the installer to do its thing. One it’s finished, you’ll be up in Mojave. If your Catalina or Big Sur install is on an encrypted disk, you’ll get a prompt to enter your userID password from the other install; note that there are two partitions it will have to unlock. The first will use a bizarre dashed-hexidecimal username; if you’ve got more than one user, you’ll have to try combinations of different weird usernames and your login password until it unlocks. The second will use your regular username. (You can have Mojave remember these so you won’t have to enter them again.)

    And now you’re up on Mojave! Note that since your Catalina/Big Sur install is readable, you can run applications that are installed on that system in this one without reinstalling them. In this case we want to run Steam, which runs just fine and allows you to install Portal to the Mojave partition and run it there.

    This still isn’t as simple as having an OS that supports both 32 and 64 bit apps, but it will work. If you’ve got 32-bit apps you really need to keep, then this is a way to have the best of both: the newest OS and one that still runs all the things you need.

  • Praise and a warning about using Gemini II and CleanMyMac X to clean up old merged backups

    Time to clean up!

    Earlier this year, my company, in its push to get things squared away for an IPO at some point (note to the SEC: I know nothing about IPO plans, I am not suggesting anyone invest in anything, I’m just this guy, you know?), installed a remote management tool for MacOS. Initially, I was concerned that we might end up being monitored as to what was on our machines, and non-work use might be frowned upon – plus I learned the hard way at WhiteHat that if you’re going to get laid off or fired, no one’s going to give you a day or two to back up anything personal on your machine. (I lost, and later managed to partially recover, all the patches for my Radio Free Krakatau album.)

    IT and upper management, after a couple of days of general consternation and concern about keylogging, etc., formally told us, “no, we don’t care what you do on your laptop, just don’t do anything illegal,” but by that point I’d scoured off the personal files and data and moved them to iCloud, Dropbox, or a spare 2012 MacBook Pro I had.

    The 2012 MBP was the last one that allowed upgrading by the end user. It could accept up to 16GB of memory, had a lot of ports (including a DisplayPort, native Ethernet, and FireWire), and had an internal disk that could be swapped to an SSD.

    I picked up a 2TB Crucial SSD, pulled the old disk, installed the new one, and used Carbon Copy Cloner to copy the old internal disk back on to the SSD. I also pulled in several older backup spinny disks into a folder called “Backups to Clean Up”. This was a superfund site of duplicates, junk, and accumulated files. I took a first cut at cleaning it up right away — deleting old stuff I knew I didn’t care about anymore, like partial iPhoto/Aperture/Photos libraries and old iTunes folders — but I was left with a considerable stash of data that I knew contained duplicates. At the time I was busy and decided I’d work out the rest later. I had removed my Adobe apps and music apps and data from my work laptop, and at the time I just didn’t have any time to work on those.

    Diving in with Gemini II

    Last weekend, I decided it was time to do the cleanup. I had bought Gemini II a couple years ago in a MacHeist bundle, and had tried it a little, but found it too slow on a spinny disk to to be useful. I decided that the job was big enough that I really needed to have some help, so I tried it again. I fired it up on Wednesday afternoon, and pointed it at my home directory on the MBP, and said go get ’em.

    Friday morning (I neglected to exclude Dropbox from the duplicate check, resulting in a lot of “download the file, check it” for the 200 or so GB or data in there, slowing things down considerably), I had a complete comparison. I spent the better part of Friday evening and Saturday and a chunk of Sunday looking at the recommendations and clearing duplicates. In general Gemini had made good choices as to which files to keep and which were duplicates, and this got rid of almost 200GB of duplicates. I did a couple rescans and found another hundred or so that I could clean up.

    Gemini recommended I try CleanMyMac X to help with getting rid of extra junk on the disk, and being in a cleaning mood, I decided to try it. I signed up for a month, and only after I’d done that did I see a “30% off if you own one of our other products”, despite being signed in. MacPaw was very kind and extended my CleanMyMac X subscription for three months to compensate.

    On the initial run, CleanMyMac X was very useful. It cleared a bunch of old caches, got rid of unused languages, etc., and helped me cleanly delete some old apps that were cluttering up ~/Library. It installed a very attractive cleanup and virus checking monitor, and I thought nothing of it at the time.

    Problems surface

    I continued working with Gemini II, and the monitor was solicitously clearing the trash when it got full, and so on. I then tried to use Gemini to just dedup my Music folder, and here’s where the fun started.

    It ran for an hour or so and then I got a “You are out of memory” warning; Gemini II apparently had 69GB of memory allocated. I shut some stuff down, but I ran out of memory again. And again. And again. Quit Gemini. Tried to run Ableton Live; the cursor was sluggish, sound was breaking up, and trying to select a patch in plugins was causing outright crashes. And the laptop was so hot I couldn’t leave it on my legs.

    This was not going to do at all. I wanted to use this machine for music, and it wasn’t able to handle it anymore. Was I going to need a new laptop? It was late. I went to bed.

    The solution

    In the morning, after some time spent with Activity Monitor, I twigged to the problem: CleanMyMac X had installed a lot of startup items. Like four. And Gemini had installed some too. This was not going to get any better with those hanging around. I decided that I was going to have to remove them, and the easiest way was to have CleanMyMac X do it. All credit to MacPaw: it simply warned me that it would shut down all the monitoring if I removed CleanMyMac X, did I want to do that? I did.

    And now the machine is running fine. I’m able to keep a couple of instances of Arturia’s 2600 emulator open and running with Live actively generating sound, and I can tweak the settings without significant effort or the sound breaking up. I ended up using Song Sergeant to do the Music Library cleanup; I can recommend it as doing a good job of finding duplicates, even in different formats.

    Conclusions

    The machine is slimmed down by about 250GB total and running fine; if I decide to do a similar cleanup again, I will probably use both Gemini II and CleanMyMac X to get the cleanup work done, but without being able to easily say no to the monitoring they install, I’ll probably delete them again as soon as I finish. MacPaw, if you’re reading this: make it optional to install the startup items, and give us an easy way to turn them off. If I had those I’d leave the two apps installed, but I just can’t and get any work done.

  • iTunes Ringtone UI Surprise

    You cannot drag and drop .m3r files into the Tones tab in iTunes. They must be pasted.

    Find your .m3r files in the Finder, select them all, File > Copy, click on the Tones tab in the iTunes sidebar, and File > Paste.

    No, it does not make any sense that drag and drop does not work. But it absolutely does not.

  • High Sierra Wifi Poor Performance Fix for 2010 MacBook Pro

    I’ve been working remotely at an AirBNB this week and was having a really frustrating time of it. The 2010-vintage MacBook Pro I have would connect to the Wifi, go for awhile — sometimes a half-hour, sometimes not more than a minute, — and then drop the connection. Shutting off wireless and reinstating it would restart the connection, but it would be unstable and drop again. The length of time it would stay connected was completely unpredictable, and whether or not it would reconnect, and how long it would take was also completely random.

    I was getting speed test results of 0.15 MB/s up and 0.18 down. This was unusable, and I fell back on my hotspot for any sustained connection. Weirdly, I could connect fine with the Amazon Dot I’d brought along – flawlessly, in fact. What was going on?

    Late Friday evening, after a particularly frustrating session attempting to get Netflix to work (I really wanted to see Disenchantment — great show, by the way!), I started doing some research and came across an article that recommended reducing the MTU for the wireless device to 1453 (from the default somewhere in the 1500’s). Really? Okay…

    Magic. It has now been solid for several hours, including streaming video. If you’re having any trouble at all, I’d recommend at least trying it. The article shows you how to set up a separate “location” with the different MTU, so it’s simple to switch it on or off as you choose.

    Update: 12 hours later, I’m getting terrible performance again. A little more searching turned up a tutorial on readjusting the MTU to optimum with ping. Reset your MTU size to default, then starting at your 1500, try the following commad (replacing mtusize with the actual number!):

    ping -D -s mtusize -c 2 google.com

    If you get “message too long” in the ping output, drop the MTU size a bit a try again. If you have no idea what MTU size is good, start at 1500, which will be too big, and go down by 100s until you start seeing “xxxx bytes from google.com:…” messages, which let you know your ping is getting through. You can then go up by tens until you get “message too long” again, then back down by 1’s until you find the maximum MTU size that doesn’t get “message too long”.

    I had to reduce my MTU size further to 1425, and I’m near 10 megabits/second again.