res ipsa loquitur

Human error may have led to outbreak | Special reports | Guardian Unlimited
Government officials believe human error at the private pharmaceutical firm Merial Animal Health is the most likely source for the return of foot and mouth disease, it emerged last night.

I’ll be your terrorist for the evening…

I’m at YYZ, and despite the Canadian passport, I’m still Mr Designated Searched Guy. Thought that the passport might’ve changed things, but no. Sigh…

It does mean I no longer have to do those dumb visa waiver things, yay!

And it didn’t help that part of one of the lighting panels started to fall off inside the cabin before takeoff, so we had to taxi back, get it fixed, and head back out an hour later. Gotta love Air Canada.

Free the Laserjet 4!

I love the HP LaserJet 4+. Built like a tank, good print quality, and now available used/refurb for pennies. Sure, they weight about as much as a Sherman, and suck power like there was no tomorrow, but one of my 4+s has nearly a million on the page count, yet prints crisp and clean.

Last weekend I scored a 4+ with built in duplexer from eBay for very little. It didn’t want to print at first (giving a cryptic 13 PAPER JAM error), but removing the rather beat-up full-ream paper tray fixed that. It may need a new cartridge (at almost twice what I paid for the printer), but I’m happy.

Wonder if I can direct-connect one of them to the ethernet port on Catherine’s eMac? I know my router won’t talk AppleTalk, so we can’t network just one printer.

A helpful error message

IBM
DB2
just gave me this far from helpful error
message:

DB21034E  The command was processed as an SQL statement because it was not a
valid Command Line Processor command.  During SQL processing it returned:
SQL0010N  The string constant beginning with "'" does not have an ending
string delimiter.  SQLSTATE=42603

As a human, or a close facsimile of one, I don’t need to
know the internal server codes DB21034E and
SQL0010N. I don’t need to know that the command was
processed as an SQL statement, because that’s what I was
hoping it would be all along. And I definitely don’t want
to know that SQLSTATE is 42603, for I’m not sure if it
would be very much better or worse if it were 42604. Or 2.
Or, for that matter, 999999999996.

And all this for mismatched quotes around a string.