Just one more time...
Apr. 4th, 2007 10:56 pmNow, in the real world, repeating the same actions over and over to get the same failed result is a pretty good definition of insanity. However, if you play with technology enough - and especially if you do any programming - you'll soon find that sometimes trying it just One More Time™ does the trick.
You see, the server has a "reset" button that didn't seem to do anything the previous 17.5 times I depressed it, but for some reason (or for some combination of arcane circumstances) actually reset the unit this last time I pressed it. From there onward, setting up the server was a piece of cake.
Not only that, but I learned how to clear out a print job that doesn't seem to want to go away using "conventional" methods (the way the gnomes of Redmond intended). Summarized without fluff:
1. NET STOP SPOOLER (entered from command prompt)
2. Delete the SPL and SHD files associated with the jammed job from %WinRoot%\System32\Spool\Printers (need to rely on file time stamps for this)
3. NET START SPOOLER (again, from command prompt)
Telecon tomorrow! Early start! (Good thing I napped this afternoon!)
Cheers...
You see, the server has a "reset" button that didn't seem to do anything the previous 17.5 times I depressed it, but for some reason (or for some combination of arcane circumstances) actually reset the unit this last time I pressed it. From there onward, setting up the server was a piece of cake.
Not only that, but I learned how to clear out a print job that doesn't seem to want to go away using "conventional" methods (the way the gnomes of Redmond intended). Summarized without fluff:
1. NET STOP SPOOLER (entered from command prompt)
2. Delete the SPL and SHD files associated with the jammed job from %WinRoot%\System32\Spool\Printers (need to rely on file time stamps for this)
3. NET START SPOOLER (again, from command prompt)
Telecon tomorrow! Early start! (Good thing I napped this afternoon!)
Cheers...