Scrabble Game – 5.28.08

Inanis wins again. Pfft.

Points This Game

Inanis: 636 | Gac: 584

Games Won

Inanis: 16 Gac: 12

Play of the Game

I played ZA and ARE on triple word on the very last play, clinching the win. To add insult to injury, the Q didnt get pulled until the very last pull of the game. Gac got that. Ugh.

Windows Printer Reset – Fix 99.9% of Windows XP Printer Issues

Far be it from me to steal someone else’s fix, but this is just too good to pass up. It’s known as the Windows Printer Reset trick, from this guy. He is so smart!

If you are having weird odd funky problems with printing, this may fix your problem. Read his article first, otherwise, here’s the run down…

1. Startup your computer in safe mode. This is done by repeatedly tapping the F8-key when you first turn on the computer until you see the Windows menu. Select “Safe Mode” and wait until the computer is finished booting up.

2. Delete all files and folders out of these two locations.

  • C:\Windows\System32\Spool\Printers
  • C:\Windows\System32\Spool\Drivers\w32×86

3. Open the registry editor. To do this, click Start, click Run, type “regedit” in the Open box, and then press OK.

4. Locate and expand the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86

There should only be the following two subkeys (delete the rest):

  • Drivers
  • Print Processors

5. Expand the Version-x subkeys, and then delete all the printer driver entries.

6. Locate and then expand the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors

There may be a bunch of different subkeys in this place. These are the only ones that should be there, delete the rest:

  • BJ Language Monitor
  • Local Port
  • PJL Language Monitor
  • Standard TCP/IP Port
  • USB Monitor

You can also delete any extra ports that were created but are no longer needed at this location in the registry if you wish.

7. Check to see if the Print Spooler service is running. To do this, follow these steps:

  • Click Start, right-click My Computer, and then click Manage.
  • Expand Services and Applications, and then click Services.
  • In the details pane, right-click the Print Spooler service, and then click Start (if it is stopped).
  • Exit Computer Management.

If this service doesn’t start, you may have other issues. Head to the link at the end of this article. That that KB page, there is a link to work out printer spooler problems.

8. After all these steps are done, go ahead and restart the computer and try and add a printer. It worked great for me. Hopefully this will help out anyone with that annoying, “Operation can not complete” error.

These steps are a tech’s abridgment of this Microsoft KB article (324757)

Late night

Almost done at work at 11:42 pm. The work queue got backed up and someone had to do it. It’s still not great, but it’s better. Let’s see if the techies are relieved tomorrow.

HP LaserJet 1020 Spooler Service Restart

UPDATE: The following procedure did not work for very long. See the new procedure.

If you are sharing an HP LaserJet 1020 USB printer over a network, and you have problems printing to it without restarting the print spooler service on the “server” machine (like people here, here and here are having), I found a solution that works for me. Maybe it will work for you too.

Quick Fix

Put the user who is printing to said printer over the network into the “Print Operators” group. If that doesn’t work (or you aren’t on an Active Directory domain – i.e. most users), try setting the security on the printer so that “Everyone” has “Print”, “Manage Printers”, and “Manage Documents” allowed. (Open up Printers/Faxes, Right click the printer, hit properties, hit the Security tab, select “Everyone”, put checkmarks in all the “Allow” boxes, hit OK.)

It may not be the most secure policy, but it sure beats buying another printer and then waiting around for the printer to get there. I find it makes a good “crutch” solution in a pinch.

Reason

The print driver on the 1020 is HOST based, not PCL based. The problem I was having was that anyone who was not an Administrator would trigger the issue. I surmise that the HOST based driver requires a certain level of permissions from the user in order to fire off the job properly. Weird, but now solved.