G
George Hardy
if your vista print spooler will not start, this may help....
If you are on vista, and your spooler service does not work, you might have
attached a network printer that is shared through a server.
i have a toshiba e-studio65 printer (tcp printer), but also have it shared
off of the server. This caused the print spooler service in vista to lock
up, not to be recovered. I could not even delete the printer anymore.
Next, i un-shared that network printer of the server, because vista could
re-discover the printer, and i'm back to square one.
After restoring Vista to the ORIGINAL install point, i connected that
printer through a local TCP/IP port, and installed the drivers for the
manually (XP drivers by the way, because there were none for Vista).
From what i have read out there, this only happens to some printers. So, if
you have a networked printer (connected directly to a network plug), do not
go through another computer to get to it. Connect as a local port, and you
will be fine. I think this might be a bug in Windows2003 Server printer
sharing or the Vista print sub-system.
george hardy
If you are on vista, and your spooler service does not work, you might have
attached a network printer that is shared through a server.
i have a toshiba e-studio65 printer (tcp printer), but also have it shared
off of the server. This caused the print spooler service in vista to lock
up, not to be recovered. I could not even delete the printer anymore.
Next, i un-shared that network printer of the server, because vista could
re-discover the printer, and i'm back to square one.
After restoring Vista to the ORIGINAL install point, i connected that
printer through a local TCP/IP port, and installed the drivers for the
manually (XP drivers by the way, because there were none for Vista).
From what i have read out there, this only happens to some printers. So, if
you have a networked printer (connected directly to a network plug), do not
go through another computer to get to it. Connect as a local port, and you
will be fine. I think this might be a bug in Windows2003 Server printer
sharing or the Vista print sub-system.
george hardy