Imagine my surprise when I try to print a document, and nothing comes out of the printer. The printer isn’t claiming it’s processing the document – and in one instance, while waiting for my document, I saw the printer fire up and spit out someone else’s document. On these occasions, if I go back to my desk and flip back to the Office application that was trying to print, only then does the document print. In fact, I can see Word finally display the status message “Printing page 1 of …” at the bottom of the window.
My own worst nightmare story with Windows: This was Windows 95, IIRC. The printer driver did two things: 1: It converted a document (or received a document so converted from some other Microsoft app) such that all byte values were being interpreted as control codes (a sort of frame shift, in DNA language). This happens now and then in Windows. This is when the printer spits out several pieces of paper and most of them have one symbol …. like a happy face or a club (as in the card suit) or five or six random sensless blobs … on each page.
The other thing the printer driver did was to become unattached to the system, but still live. So, it could not be reached, even on the command line. The printer driver survived reboots as well. It could not be killed.
And the document sent to it was a 200 page manuscript.
Solution: Reinstall Windows.
Reason why this is bad: I was printing out a document that needed to be produced some time within the next couple of hours.
Actual solution: Find a different computer, print the document out there, return to original computer, and install Linux on it.