Category Archives: OS X

Mindfulness about what you’re doing with OneTab

I use OneTab (see: previously) to manage the tabs on my Chrome browser. It does a great job of sweeping a bunch of current state for open tabs onto a page, so that you can get a fresh start when a new project comes up and then restore the state of the old one. It also means that I have a lot more working memory on my old MacBook. All in all a big win.

Every once in a while the projects pile up, and I forget what I was doing but still don’t know what to focus on. The mindfulness project then is to go methodically through each of the tabs, dealing with whatever is on that page and then closing the tab instead of saving it. This has been a good way to feel like I don’t have an infinite set of half-done efforts.

Advertisements

I should have bought more memory for my Macbook sooner

Ever since upgrading my Mac to 10.6.8 I've been running into memory problems, especially when I have a lot of Chrome windows open. I solved this problem – or I seem to have – by upgrading from 2G to 4G of memory, with memory from Crucial. Less than $100 spent, and the computer no longer starts to thrash when I have more than a few windows open.

Now of course it's time to keep a lot more apps open to see what the new system limits are.

Technology upgrades are a tedious but necessary task

Technology upgrades are a tedious but necessary task.

I'm going through this now, with an upgrade from Mac OS 10.5.8 to Mac OS 10.6.8 on my black MacBook. The world decided in its infinite wisdom that 10.5 was too old to keep supporting, and so quite a bit of software was starting to break. The promise is that 10.6.x will last a bit longer and keep my old 2008 vintage system running for a while longer.

Upgrades are always fraught with peril. In this case, it involved sticking a DVD in the drive, clicking a few times, and then waiting 45 minutes for the system to emerge in newly upgraded status. When you do something like that there's a lot of faith you have to have that the people who put together the shiny DVD got every last thing right, that they didn't forget to check some bit somewhere which in your case would turn your computer into a puddle of slag. I know that at some level it's an irrational fear, yet I've bricked my share of hardware in my time and I've known the process of operating system upgrades to involve long late-night patching sessions to get everything to work.

There was no puddle of slag at the end of my upgrade, just a computer that looked about the same as it did before with no huge obvious changes, just a few cosmetic bits and the promise of future compatibility.

I'm told that the typical Android phone that's sold never gets an operating system upgrade from the vendor, and that the usual upgrade path is either to install a completely unsupported hacked up new software load or to scrap the phone and start afresh with new hardware. I haven't lived in that world yet so I don't have the experience of others to go through, just the general sense that unless you're willing to delve into the details of Cyanogenmod that you should be prepared to get a new phone every time your contract runs out.

Compared to operating system upgrades, application upgrades are relatively easy and low worry. With most consumer software that's going through a rev cycle, these days you select "upgrade" from within the app and it magically replaces itself with a slightly newer version. This time I needed to update Chrome, and I had to descend to the operating system and delete one file to make the automated process work just fine.

The other task in my grand system upgrade effort has been to try to get BlueStacks running. This is an app that runs Android apps on Mac OS X. It's in beta, so I have some reason to understand when things don't go instantly right, but I tried it out anyway and the install failed to come up with a working system within the amount of time I was willing to throw at it.

Just because I have part of a 10.6 upgrade done doesn't mean that the whole thing is ready. The CD ships with 10.6.3, and you have to download a gigabyte-plus combo update to get to 10.6.8. The first time I did this the download was corrupted (?) so I tried again with success. I don't understand why, just enough to hit the "yes" button, and to type the error message exactly into Google when the error happens in the hopes that someone else has seen exactly the same problem.

What did we do before error messages could be looked up with such precision? Well, for one thing, there was usually some source code lying around so that you could read just what the context was for the error. If there was no source code to be had, then Usenet was sure to have someone who had seen the same failure mode. Google searching for failures just distributes out the task to a broader audience than ever, but there's still the basic issue that when something goes wrong you have to rely on the goodness of people who are willing to air their systems difficulties in public in the hopes of righting them again.

Keeping a system running with current software is an ongoing job. I ended up only being able to do it after digging through a rats-nest tangle of cables in my basement, emerging victorious with a Firewire cable that allowed me to back up the Mac to the point where I was confident enough that I could insert the DVD, click "Yes", and hope that someone in Cupertino tested every combination of equipment that one single updater was supposed to work on.

 

Related articles

I recently upgraded to lion 10.7 and now I can't open itunes or do any software upgrades. Not even 10.7.1! Help
my mac had it's original software re-installed by Apple. since they did this, my airbook pro will not recognize my iphone in Itunes, and I cannot update the latest version of itunes, because it says I'm not running the latest version mac software????
My bid for tech liberty: how have I done so far?
Sprint has now canceled its early upgrade program

spotty wifi

The problem with unreliable networks is that you have to engineer extra hard to be able to make use of them, and you still can't rely on them even when you do.

Consider the network connection that's randomly working and not working. If the network were actually down, you could work with that, knowing that eventually it would be a time and place that you could reconnect. Until then you stay offline in airplane mode and just chill and enjoy it.

The maddening part of the network that doesn't work is that instead of working with the network you end up working to repair the network, and its unreliablity neither gives you access nor downtime. In other words, spotty wifi is bad, worse than no wifi at all.

(Posted on the occasion of the repair of my MacBook's wifi card, which had been flaky for months.)

Freedom, to go offline

Through some random chance encounter on the net – that is to say,
I don’t remember why I found it – I’m offline right now.

The tool of choice for going offline is a little Mac application
called Freedom, which disables your Internet access for a specified
period of time so that you can get things done. Written by Fred
Stutzman at UNC.

Freedom enforces freedom; a reboot is the only circumvention of the Freedom time limit you specify. The hassle of rebooting means you’re less likely to cheat, and you’ll be more productive. Not rebooting is why we bought Apple computers in the first place. When first getting used to Freedom, I suggest using the software for short periods of time.

It’s a great idea, especially for the times when you find yourself
overwhelmed by the 1000000000s of possible things to do when you
are on line, and when reducing the number of options is key to actually
accomplishing any one task.

(Obviously I’m back online to post this!)