Skip to main content

How To: Quick Way to Clear Up a Jammed Print Job

For one reason or another, a print job may get hung up and stop responding. You may be unable to print or even to cancel the job. One way to possibly clear up this problem is to use the Windows command line to stop and restart the printer spooler after flushing it. The services command “sc” or the “net” command can be used. Here are the steps using the services command:
  1. Open the command prompt. For Vista or 7, you will need administrator privileges.
  2. In the command prompt, type and enter   “sc stop spooler” (without quotes).
  3. Next type and enter the line below:
           del /q /f /s "%SystemRoot%\system32\spool\printers\*.*"
  4. Then type and enter “sc start spooler” (without quotes).
This procedure will clear out the Spooler and should allow you to continue with your printing. Note that this will not clear paper jams or mechanical problems.

Credit: Techsupportalert.com

Comments

Popular posts from this blog

Using ESPEasy with Home Assistant via MQTT

Preface: I've just started playing around with Home Assistant on a Raspberry Pi and exploring the world of MQTT to control devices on the network. Learning curve is a bit steep but worth the effort as MQTT is very fast. The hardware and software tools I'm using are as follows: 2 x Sonoff relay units 2 x NodeMCU Boards ESPEasy firmware (must be version 121 or above as that contains the MQTT 'retain' flag option. Home Assistant software on Raspberry Pi2 MQTT Test Software: PC: MQTT.fx Android: MQTT Dashboard

My Notepad++ tricks when editing YAML files in Home Assistant

To comment out a whole section in one go: Highlight the text you want to comment out and use CTRL + Q. If you do this at the start of a line, it will only comment that line. CTRL + Q is toggle mode (comment on/off). CTRL + K will allow you to add multiple comments one after the other.

How to check what entities are filling up your Home Assistant database

If you use the Home Assistant MariaDB add-on, this tip will show you how to query the database so see what Home Assistant entity states are triggering the most, filling up your database. What were going to do: Install the phMyAdmin add-on for MariaDB. Query the MariaDB database. See what entity state changes have the most action. Paste the code below into the SQL query box:  select entity_id,count( * ) from states group by entity_id order by count ( * ) desc; And if you're using the internal home-assistant_v2.db instead, you can use the SQLite Web add-on to achieve the same thing.