Fixing the Camera Printer

image
Ancient technology from the long long ago. The printer is the thing on top of the computer tower. The camera is the giant cabinet looking thing to the right of the monitor.

We have something called a “gel doc printer” at my work. It’s purpose is self-evident. It prints documents of our gel pictures.

Gel doc printers are used infrequently and often labs share them. Ours is shared between… probably five different labs? Maybe more.

Taking pictures of gels is important in science. Gels are how we visualize DNA and proteins.

A digital copy is good enough for your own records, but you need a printed copy in case someone claims your digital copy is edited. The gel doc printer provides that physical copy.

Our printer is shared and an issue comes up that when the printer breaks we don’t know whose responsibility it is to fix it.

Usually the breaks are fixed easily. A reboot of the printer or the computer will suffice. Not this time!

This time the printer has refused to print any and all images despite the computer recognizing it as a printer that is plugged in and printing test pages.

Awful looking test pages, but test pages none the less.
Awful looking test pages, but test pages none the less.

I delved into it and realized the printer’s driver’s were outdated. Normally this would be an easy problem to fix. Not so!

You see, the computer the printer is attached to runs Windows XP which is no longer supported by Microsoft.

An unsupported operating system can easily be hacked which means this computer can no longer be connected to the internet. If it was, hackers would have an easy access point to UC Davis’s systems.

What that means is I couldn’t just download an update to the drivers like usual. I had to download the update on my laptop and then move it over to the printer computer with my USB drive.

So I downloaded the drivers and moved them over to the computer. “But wait! You need the driver install program.”

Okay. I get that and move it over. “But wait! You need .Net Framework 4 to use the driver install program!”

Okay… I get that and move it over. “BUT WAIT! You need Windows Service Pack 3 to install .Net Framework 4!”

Okaayyyy… Move that on over. And that one finally installs!

Moving backwards, the .Net Framework 4 installed as well. Along with the patch I got for that.

Then the driver install program laughed at me and said it needed access to the internet after all. I tried installing the drivers on my own, but no luck there.

I researched more on the problem. The printer is able to print out the very first part of all the images. Then it disconnects from the computer, reconnects, and decides the print job is complete.

I found absolutely nothing on how to fix that problem. There were some suggestions that it was a problem with the connection to the computer, but switching the USB port used by the printer changed nothing.

Maybe a new USB cable would do the trick, but I’m unsure if those are available for printers this old or whether it would fix the problem.

For now, all the images are put on USB sticks and printed on different computers.

-GoCorral

Advertisements

The Death Knell of my iPod

Here lies a dying breed, the iPod classic.
Here lies a dying breed, the iPod classic.

Alack and alas oh readers of my blog! For my iPod is slowly dying!

I got this iPod about six years ago back and it has served me well in its lifetime.

But now… Now it refuses to connect to my computer!

I can still charge it using the cable, but iTunes no longer registers that the iPod is connected.

I looked the issue up and found a post on Apple’s support pages from 2012 which listed a number of solutions to my problem, none of which worked.

I probably reinstalled iTunes a dozen different ways in an attempt to fix this issue, but it still refuses to interface with my iPod.

And I’m sure its not the iPod. My computer still sees the device. I could remove and add things to the iPod manually, but the music is coded and difficult to rearrange. Plus, that process is a whole lot harder to deal with than using iTunes like I have in the past.

My reading on the issue makes me think something got messed up in my computer’s registry when I updated iTunes from version 11 to version 12. The registry of my computer is some internal programming section that I can’t normally access to fix and if I did go through the steps to access it I might irreparably damage my computer for ever and eternity.

I could go to the Apple Store for help, but since the problem is with a Windows PC I don’t think they’d be able to help.

Likewise, because the problem is with my computer, getting a new iPod might not necessarily work either. Plus, they don’t even make the iPod classic that I have anymore! It’s all iTouch, iNano, and iShuffle now. None of them have the same storage capacity as my six year old iPod which is frankly a little shocking. My collection is sitting at 45GB right now and the largest iTouch is 64GB, so I wouldn’t have to make any hard choices. I’d still be missing the assurance that a new device would even work with my computer though.

The most frustrating part of this whole experience has been how long Apple has known about this error in iTunes code. The support page I found indicates they’ve been aware of this issue or a similar issue for the last two years and haven’t fixed it. Peter Jackson’s finished two movies faster than that!

The core of it is that Apple won’t fix an error when the error only occurs on their competitors machines. Its turned me off so much to their company that I’m now looking into getting a different MP3 player.

So… Any suggestions?

-Mister Ed