Who produces our computer cables?

male-it-worker-buried-in-computer-cable_450

That’s the kind of question that doesn’t come up unless you get have all these problems with your firewire drives, and Mac’s Console reports things like “bad node” and you think it’s either the drive or the computer and finally you figure out it’s the BLOODY CABLE.

So then you go looking on the intertubez to try to find out who makes the best Firewire cable (even though Mac phased all that stuff out ages ago and instead of being able to daisy chain FW drives you now have to buy things like THIS to handle all the USB connectors.) And then you come across discussion threads like this one, where people seem quite knowledgeable or at least you hope.

FYI: There are three wire mills that make the vast majority of FireWire IEEE 1394a and 1394b cables.

The actual cabling, #28 AWG signal wires (four data wires, stranded, double duplex, packet switching peer to peer communications) and #20, #22 or #24 AWG power, ground & shield wires, used for almost all FW 1394a cables are virtually the same.

The rub is in the assembly and termination parts, the connectors. Dr. Sam Liu, an upstanding IEEE engineer and owner of Newnex.com Technology Company, is the head of the standards committee at the 1394ta.org and has been since 1999. If there is a FireWire “triad” symbol on the cable terminations or connectors, then its a good one and Dr. Sam probably helped design it and/or certify it.

And suddenly you look at Firewire cables a little bit differently, because–and maybe this is why I find it comforting–there’s an actual person behind it, and there’s even a seal of approval to look for.

Also learned: you can test a cable if you have the right oscilloscope equipment and a good cable will produce an aesthetically pleasing pattern like this.

firewirepattern

So to sum up: Cables! More fascinating than you think.

Battling inactive memory on Macs pre 10.9

activity_monitor

If you have a Mac running Lion, Mountain Lion…pretty much anything before Yosemite, memory issues are rampant. (Firefox you suck! Handbrake you are made by the devil!!)
But it’s all good, you know. By watching Activity Monitor and Console, I’ve got to learn a little more about the inner workings of my Mac and diagnose some problems.
When my computer slowed to a crawl I noticed that “Inactive memory” was a huge chunk of my memory pie. There’s four kinds: Free, Wired, Active, and Inactive. (Here’s a good tutorial on what it all means.)
Trouble is, Macs before Yosemite have sucky memory management and that Inactive Memory can take over and never become free, which is what should happen, but doesn’t.
That sent me on a Google search and I came across this wonderful post on 55 Minutes, which recommends downloading a Python script (no, not this kind of Python script), putting it in a hidden folder and dropping a launchd script into Library/LaunchAgents that runs the memory purging script whenever Inactive memory gets too big.
Works like a charm, and all I really did was Google search and use a bit of logic to figure out the directions. No l33t haxx0r me!!

Writing on the Arts, Santa Barbara, and Beyond!