Journal Qzukk's Journal: Joys of Windows #1245 3
Print document, spooler crashes. Document cannot be removed from queue because spooler is not running.
Reboot computer. Document in queue immediately tries to print, spooler crashes.
Solution: Turn off printer, reboot computer. Delete document from queue. Turn on printer.
You'd think that critical infrastructure like the print spooler would be a bit more robust. Or at least be able to detect that it is repeatedly crashing on a single document and ask the user if they'd like to cancel the offending print job. Or make cancelling print jobs not dependent on the spooler service. Also, apparently user permission to manage print queues does not extend to restarting the print service itself.
Aside: You know how when you say a word over and over it starts to sound funny? Apparently Chrome gets the same way too... it didn't start highlighting "spooler" as a misspelled word until I wrote it about 5 times.
In the 1990's (Score:1)
I worked at a place that used Banyan Vines as the network OS.
You could logon to any computer on the network, it delivered your environment with all software & privileges as if you were at your desk and allowed you to manage your print jobs intelligently - eg delayed print to set a print run off after you left for the night or cancel a job from another computer (eg one closer to the printer) AND YOU COULD MOVE THE PRINT JOB TO ANOTHER FUCKING PRINTER IF IT WAS THE SAME TYPE OF PRINTER EG PS. WTF can thi
Re: (Score:2)
If it was in the 90's, they probably patented it and demand 5% of the gross revenue.
Come to think of it, maybe that's why Windows's roaming profiles had so many problems back then.
Re: (Score:2)
Window's roaming profiles still has a ton of problems, but mostly they are attributable to 3rd party vendors. Damn you Sun Java.