Archive for the ‘Jettison’ Category
Thursday, October 25th, 2018
Jettison 1.7.2 is now available, and contains a single fix to correct an intermittent licensing problem that a few users have experienced. On some machines, Jettison would accept and confirm a serial number, but would subsequently fail to save it in its preference file. This resulted in a very frustrating cycle for new users: You’d buy a license for Jettison, enter your serial number, then later get pestered to buy Jettison again.
If you haven’t been bitten by this bug, there’s no hurry to install this update – it’s functionally identical to version 1.7.1 except for the licensing fix.
Tuesday, October 16th, 2018
Jettison 1.7.1 is available, bringing fixes for a couple of simple problems and one complicated one.
The previous release of Jettison didn’t correctly show that it was licensed when you looked in the About box after importing a Mac App Store license. This was understandably very confusing to those of you that followed the instructions for upgrading in the FAQ. It now correctly shows “Licensed to: Mac App Store User” (since Apple doesn’t provide a way for us to get your name or Apple ID from your license) and removes the “License” item from its menu.
Also, there were occasions when all of the items in Jettison’s menu would become grayed out. This turned out to be caused by its error window getting stuck behind an application that was in Full Screen mode. It was patiently waiting for you to respond to an error message you couldn’t see – definitely not very helpful. That’s been fixed now.
Messy issues with Power Nap and Wake for Network Access:
When Power Nap or Wake for Network Access are turned on in your Energy Saver prefs, macOS may wake from sleep in ‘dark mode’ – which means it wakes from sleep, but never turns on the display. When this happens, it doesn’t let most applications – including Jettison – know when it wakes up or goes back to sleep. That means that Jettison can’t mount or eject your disks as it’s supposed to.
This would all be well and good if this temporary wakeful state mounted your disks, did its thing (like a Time Machine backup), ejected the disks and then went back to sleep. Unfortunately, while it seems to (mostly) work with Time Machine disks, if other drives get mounted during dark wake, you’ll often see a “Disk not ejected properly” error for them when you return. macOS can’t always manage the mounting and ejecting of disks correctly, even when it’s all by itself in a dark room.
Jettison 1.7.1 solves this problem by refusing to let macOS mount any non-Time Machine drives during a dark wake. This should take care of the disk errors (and associated possibility of data corruption) while still allowing you to use Power Nap and Wake for Network.
On the outside chance that you’re actually getting error messages for your Time Machine drive too, you can launch Terminal and run this command:
defaults write com.stclairsoft.Jettison disableTimeMachinePowerNap 1
That will tell Jettison to prevent your Time Machine drive from being mounted during dark wakes – with the obvious consequence that Time Machine can’t run Power Nap backups while your machine is sleeping. It’s a compromise, but at least it’ll ensure that your backups don’t get corrupted.
You can see the full change history and download Jettison 1.7.1 from the Jettison release page.
Monday, September 24th, 2018
App Tamer and Jettison have both been updated with support for Dark Mode in Mojave.
Jettison 1.7 also includes a number of features and fixes for all versions of macOS (well, from 10.8 to 10.14, anyway — that’s what Jettison supports). These include the addition of a menu command to mount all unmounted disks, options to not automatically remount specific drives after they’ve been ejected, and the fix for a bug that could cause some Macs to repeatedly cycle between sleep and wake. There are also a number of under-the-hood improvements and fixes.
Details and download links are available on the Jettison Release Page and the App Tamer Release Page — or you can just hop over to the Products Page and download them both!
Friday, March 16th, 2018
Before starting a reorganization and rewrite of Jettison’s internals, I figured I’d better officially release the myriad little changes that I’ve been trickling out to various folks as they’ve contacted me with issues.
Version 1.6 brings Jettison up-to-date with APFS (the new file system format released in High Sierra) as well as making its drive mounting / remounting procedure more robust. There are also a bunch of bug fixes and improvements in error checking and error reporting, and new AppleScript commands for ejecting, remounting and sleeping.
You can grab the update from the Jettison Release Page, as well as seeing a more complete list of changes there.
There are still a few issues with Jettison on High Sierra, primarily due to some flakiness on High Sierra’s part that I haven’t been able to pin down. If Jettison can’t eject a drive and tells you “try ejecting it in the Finder,” that means that macOS refused to eject the drive, won’t tell Jettison why, and there aren’t any files open on the volume that should logically keep it from being ejected. In that case, Jettison just throws up its hands and says “I give up!”
If you ask the bus driver to stop the bus and he just keeps on driving, what can you do? (Well, you could open the window and jump out of the speeding bus, but I doubt you want me to do that with your external drives…)
So I’m continuing to chase down that issue, as well as a rare one where the machine continually cycles between sleep and wake states every few seconds, resulting in hundreds of “External disks ejected” notifications from Jettison while the machine was supposed to be sleeping. This situation is rare and I’ve been unable to reproduce it here, making it a tough one to figure out. If it’s happening to you, please let me know at firstname.lastname@example.org.
Thursday, March 2nd, 2017
While Jettison and HistoryHound are still supported and sold on the St. Clair Software website, I’ve pulled them from the Mac App Store. The versions that were in the Mac App Store were older revisions, and it just didn’t make business sense to rearchitect the apps to meet Apple’s current requirements for approval so they could be kept up-to-date.
For both applications, complying with Apple’s sandboxing and feature constraints to get them approved for sale would have required significant rewrites. And in Jettison’s case, it would also require that buyers download a separate helper app to enable its full functionality. I realize that some people will be put off or inconvenienced by the fact that these apps are no longer in the Mac App Store – my apologies if you’re one of those folks, but it just doesn’t make sense for Jettison and HistoryHound.
Without going into a full-on rant about the Mac App Store (I could ramble on for days), let’s just say that while the Mac App Store is convenient for consumers, it doesn’t really serve the needs of some developers. Much has been written about it already (here, here, here, here and here, for example) so I won’t rehash it all – and despite years of “constructive criticism” from developers, Apple hasn’t fixed some major problems.
I hope you’ll continue to purchase our applications, as well as those from other independent developers selling outside the Mac App Store. While it’s a little less convenient than the Mac App Store, it allows us to bring you the best software we can, and also gives us the opportunity to foster a two-way relationship with you – both of which really matter to us.
Sunday, November 13th, 2016
Version 1.5.3 of Jettison is now available, correcting a couple of bugs that could cause Jettison to crash. The folks that reported the bug simply noticed that Jettison’s icon would disappear from their menubar sometime during the day. The new version should eliminate that problem.
You can update your copy by downloading version 1.5.3 from the Jettison Release Page or by selecting “Check for Updates” from Jettison’s menu in your menubar.
Wednesday, November 2nd, 2016
HistoryHound 1.9.12 and Jettison 1.5.2 both deliver stability improvements and bug fixes to make sure they run without issue on El Capitan and Sierra.
HistoryHound also includes better error handling and its indexing is more intelligent when it encounters web pages that redirect you to a new page. You can now click on status messages in the main window to show you the status of indexing and the contents of your search index, and HistoryHound 1.9.12 supports the Vivaldi browser as well as Safari, Chrome, Firefox, OmniWeb, iCab, Opera, NetNewsWire and URL Manager Pro.
Full lists of changes and download links are available on the HistoryHound release page and the Jettison release page.
Wednesday, August 31st, 2016
Yes, I’ve been busy over here! There are Sierra-compatible updates for both App Tamer and Jettison today, with both offering additional fixes and enhancements as well as support for macOS 10.12.
App Tamer 2.2: While I’ll be the first to admit that App Tamer is a bit of a niche product (you’ve got to be a little geeky to like the details of what it does), I’m excited by the improvements in this release. It’s more intelligent about identifying which processes are “helpers” for others, and can therefore do a much better job at throttling all those Safari Web Content processes when it limits Safari’s CPU usage, for example, while still letting the Mail Web Content helpers run at full tilt for Mail (if that’s what you want).
App Tamer’s basic process management is also more efficient now, so it all adds up to it doing its job better. If you’ve got apps that are sucking down CPU (and battery!) while they’re sitting in the background, App Tamer can help you out. More details and download links are on the App Tamer What’s New page.
Jettison 1.5.1: The Jettison update addresses issues with Sierra, and also gives you the option to unmount rather than eject drives when your Mac sleeps. “Why do I care?” you say? Well, I’m glad you asked (and you might be too)! Some SD cards and Flash drives won’t remount properly after being ejected, even when Jettison reloads their device drivers. That can result in you having to do a really inconvenient little dance of unplugging them and plugging them back in to get them to show up. Turning on this new option in your Jettison prefs avoids that.
There are also bug fixes for Jettison’s handling of network drives, removal of some logic that checked whether the display was going to sleep before ejecting disks (long story – it did solve a problem, but created even more in the end), and tweaks to better handle OS X’s propensity to report errors when there are none. Go visit the Jettison What’s New page for a list of changes and download links.
Now here’s hoping that Apple doesn’t make any major changes to Sierra before it comes out of beta that require me to update these Sierra-compatible updates 🙂
Wednesday, February 10th, 2016
A security vulnerability has been found in Sparkle, the framework used by many Mac applications to check for and download software updates automatically. Full details are at:
While some of our applications (like HistoryHound) are using older versions of the Sparkle framework at the moment, they all use encrypted HTTPS connections to check for and download updates, so there’s no chance of a man-in-the-middle attack, as described in the report.
So you can safely leave automatic update checking turned on in all of our products – it’s being done safely.
Thursday, November 12th, 2015
So I started getting emails yesterday complaining that Jettison was suddenly telling users their trial period was over – even though they’d already purchased a license. When I got the first few, I thought they’d just deleted their preference files and needed to re-activate their licenses, but then the trickle became a deluge – what the heck?
So I dropped everything and looked into it – I needed an answer ASAP or I was gonna spend the next couple of days doing nothing but answering email. It turns out everyone who was affected had bought Jettison through the Mac App Store and then upgraded to the direct-from-the-website version (because it’s better, of course – instructions here if you’re interested). When you do this, Jettison copies your Mac App Store receipt to a safe place so that it can verify that you’ve actually bought a license, even if you delete the App Store copy of Jettison.
Lucky for me, I’d bought a copy of Jettison myself when testing this mechanism, so I had my own receipt still sitting in ~/Library/Application Support/ so I could look at it. Printing the certificates in the receipt showed this little tidbit:
Signature Algorithm: sha1WithRSAEncryption
Issuer: C=US, O=Apple Inc., OU=Apple Worldwide Developer Relations [...]
Not Before: Nov 11 21:58:01 2010 GMT
Not After : Nov 11 21:58:01 2015 GMT
Subject: CN=Mac App Store Receipt Signing, OU=Apple Worldwide Deve [...]
See that “Not After:” entry in the Validity section? “Nov 11 21:58:01 2015 GMT” – yeah, that’d be yesterday. When the emails started. Apple signed the receipt with a certificate that expired yesterday, so if you have one of these receipts, Jettison no longer thinks you’re legit. Sorry about that – I hadn’t considered that eventuality. And reading the news this morning, it appears that Apple hadn’t either.
So what to do? I’ve wrapped up Jettison 1.5 and posted it. You’re going to have to do a little dance again to get Jettison to update your receipt, but this version will do the right thing once you follow these instructions:
- Put every copy of Jettison on your Mac in the Trash and empty the Trash.
- Open the App Store application and click on the Purchases tab.
- Re-download the copy of Jettison you purchased. It will include a new, non-expired receipt.
- Download the latest version of Jettison (http://www.stclairsoft.com/download/Jettison-1.5.1d2.zip)
- Double-click the .dmg file to open it, then double-click on Jettison before copying it to your Applications folder.
- After Jettison tells you that it has found your App Store license, you can copy it to your Applications folder.
Sorry for the hassle. But hey, at least it forced me to get the version 1.5 update out the door, so there’s some benefit there, eh? And thanks Apple – I didn’t need to sleep last night anyway.
P.S. I’m seeing a bunch of people buying non-App Store licenses directly from the St. Clair Software store today instead of jumping through these hoops to deal with the App Store. I have to say I’m all for that 🙂
A bit more info that’s interesting and could use some corroboration: I think this problem only affects apps that were downloaded before September 24 (either via purchase or update). When I download a new copy of Jettison from the App Store, the receipt is signed with a cert valid within these dates:
Not Before: Sep 24 19:09:31 2015 GMT
Not After : Oct 23 19:09:31 2017 GMT
So in my sample size of 1, copies of Jettison purchased or updated today will work until Oct 23, 2017, and could have worked with this receipt only as far back as September 24. If Apple has been using the same certificate to sign all App Store receipts (which seems reasonable), then anything that has been downloaded from the App Store after September 24 won’t expire until 2017. And apps downloaded prior to that have some other expiration in their receipts. If I had more time, I’d dig through all of my App Store apps to find out when each cert expires, but alas, I’ve got work to do and have killed enough time on this already…