This is an old problem to some people, but it just happened to me.
My printer won't print, although it will throw out a test page, so I know that the printer is not the problem.
My printer icons have all disappeared.
I tried to reinstall a printer, and the computer told me that the print spooler was gone.
I used my "System Mechanic" to set up another print spooler. That didn't hurt, but it didn't help, either.
I found a button to push, to start the spooler, and it told me that either I or the computer had committed error 1075, and that a component was missing.
I looked at the discussion threads in "daniweb" under "printer subsystem unavailable". It seems that I'm a little late. Everyone else had this problem between 2003 and 2005, and from the look of the postings, people had "aha!" moments, and fixed the problem.
I tried the fixes, from the discussion threads. The fixes included going into the c: prompt and initializing the print spooler. No luck. I wound up with error 1075 again.
I have looked through the Microsoft Windows website, and there is just too much information to sift through. But the "printer subsytem unavailable" information box said that the problem occurs when a user tries to configure Windows Fax, which I haven't tried to do.
I tend to over-correct, and so what I'm presently considering is backing up all of my data, and re-installing W 2000, or buying more RAM, and installing XP Pro. But there has to be something a little less pervasive.
Hey there whytheheck I do telephone tech support for a computer manufacturer in the US and have found this article to be quite helpful with the problem you explained here:
Hey there whytheheck I do telephone tech support for a computer manufacturer in the US and have found this article to be quite helpful with the problem you explained here:
Cool. And it's in English. And it points out another possibility I hadn't thought of, which is that the printer, although it works, may be the source of the problem. It's a Lexmark. I didn't think that it could have been the problem (or that the driver could be the problem), because it worked for a year and a half without problems.
Not enough time to do it tonight, but I'm going to set aside the time, and push through the instructions when I have an hour.
No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.
Previous Thread in Windows NT / 2000 / XP Forum Timeline:another boot loop