Evening all. Perhaps my posting of 28 06 2010 (copy below) became randomly corrupted or something. I am grateful for advice offered, I’m more than a bit puzzled by the responses, as the appear on my screen.
Have a look at this: I wrote - “However, even as it merrily wasted ink, the O/S reported that there was no current print job - and thus the 'job' could not be removed from the spool queue in the usual way.” I should have been explicit that the list was unpopulated? Puzzlingly, Malcolm's retort was - “….It is usually a case of killing the print job in the printer queue….” and Derek’s, in a similar vein - “……, you can delete jobs from the printer queue on the machine that is the print server.” Further confirmed by Malcolm in - “Derek is right, for a home PC network the printer queue will be on the computer that you set up as the master machine, with the printer(s) attached to it.” I exercised Malcolm's “administrative privileges, to be able to kill off those corrupted print jobs or the malicious ones” on the "master machine". That, of course, is how I tried to … “[remove] from the spool queue in the usual way.” But with an unpopulated queue ......? Anyone anything to add please?. Cheers, John in Wales ================================================== Hello everyone, Had a real teaser last evening. I was networking (LAN) a document to be printed on a 'remote' (not QPC approved) printer attached to a peer in the network. In other words it was all in (this) house! When the printer had initiated, it attempted to print stuff from its local machine, stuff which originated from that W/Xp's machine's copy of QPC-2! It had been (accidentally) spooled to the HD from ARCHIVE , some days ago, after the printer was last on-line. Incidentally, some was plain text, some was gobbledegook and many were new-page codes! The only way to stop it, I found ,was to force an error by denying paper to the muncher. Then I would reboot the local (to the printer) machine and the printer. It was still there. :( O.K. I (think) I understand all that behaviour. However, even as it merrily wasted ink, the O/S reported that there was no current print job - and thus the 'job' could not be removed from the spool queue in the usual way. Again, I (think) I understand. There now follows an appeal for help on behalf of the "Save my Sanity, Ink and Paper" party. Is there a 'magic' way of removing, what has, in effect, become a 'rouge' job, from QPC-2, on the O/S spooler, please, anyone? Be good all. Its not raining here. John in Wales. PS: QPC-2 in innocent! ======================================================= _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
