Vista - Print Spooler Crashes at Startup - Network Printer Won't Install

Hi All,
I have been trying to get a Minolta magicolor 2300DL network
printer to work with Beta 2 for several days. It should work. I can ping the
printer and see the printers HTTP web configuration page. All my other
computers use it. The install new printer wizzard cannot find the network
printer so I configure the IP address manually. Everything looks good but I
cannot print test page. I have tried the 2300DL XP drivers and the Windows
Vista Update 2430DL drivers. It is just a RAW write to port 9100. To kill
print documents or delete printer useally hangs requiring re-boot. After
many tries I now get print spooler crash error message at startup and cannot
do anything with Control Panel>Printers as the service is not running. Any
ideas on how to clear the print spool and delete printer so I can try more
stuff?

TIA,
Kent

Some Minolta drivers have issues with stack corruption on XP. If the driver
was designed for XP it may have the same failure.

here's info to clean the drivers.

http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Kent_Diego" <None@no.way> wrote in message
news:edWgWbPkGHA.4304@TK2MSFTNGP03.phx.gbl...
> Hi All,
> I have been trying to get a Minolta magicolor 2300DL network
> printer to work with Beta 2 for several days. It should work. I can ping
> the printer and see the printers HTTP web configuration page. All my other
> computers use it. The install new printer wizzard cannot find the network
> printer so I configure the IP address manually. Everything looks good but
> I cannot print test page. I have tried the 2300DL XP drivers and the
> Windows Vista Update 2430DL drivers. It is just a RAW write to port 9100.
> To kill print documents or delete printer useally hangs requiring re-boot.
> After many tries I now get print spooler crash error message at startup
> and cannot do anything with Control Panel>Printers as the service is not
> running. Any ideas on how to clear the print spool and delete printer so I
> can try more stuff?
>
> TIA,
> Kent
>

In order to install the printer use the setup.exe file that comes with the driver and don't use the add printer wizard. You get the same print spooler crash in XP if you use the add printer wizard but if you use the setup file it installs fine in both XP and Vista Beta 2.

Make sure and delete the printer before you begin and if you are using the ethernet interface and not sharing it off of another computer, during setup choose to install it as a local printer and pick any of the port choices it gives (lpt or file) and once it completes the install go back into the properties and change the port to the IP port.

Dez

>
> In order to install the printer use the setup.exe file that comes with
> the driver and don't use the add printer wizard. You get the same
> print spooler crash in XP if you use the add printer wizard but if you
> use the setup file it installs fine in both XP and Vista Beta 2.
>
> Make sure and delete the printer before you begin and if you are using
> the ethernet interface and not sharing it off of another computer,
> during setup choose to install it as a local printer and pick any of
> the port choices it gives (lpt or file) and once it completes the
> install go back into the properties and change the port to the IP
> port.
>
The setup.exe will not run correctly. Something about a .JAR file crashing.
I think there is some bug/incompatibility with the networking or security
features and the network printer installation wizard/drivers. The wizard
cannot find the printer even thought I can reliably ping the printer's IP
address. There seems to be intermittant unreliable communication to the
printer. The driver seems to know the printer has paper and will report "Job
sent to printer" and sometimes change icon to having the image of two people
upon it. I suspect firewall or networking bug.