XP SP2 introduces 90 second delay

[John]

After I installed SP2 I have a 90-second delay between
when I select File - Print and when the printout
management dialog box pops up. Tis happens in third-party
apps, such as Adobe Acrobat 6, but not in MS apps, like
Office and IE. It is quite consistent, and the delay goes
away when I remove SP2. It doesn't matter which printer I
select, be it a Brother, Lexmark, or HP, and it doesn;'t
matter if it's connected locally or via the network.

Any Ideas?

 

[chris]

Mine seems to take about 2:30. I haven't determined
whether it was SP2 or the .NET framework which has affected
my printing. You are correct, though..... Printing from
any Microsoft product seems to work fine. Hmmmm....

Anyone?

 

[chris]

Actually, I just went in and got rid of all my other
networked printers but left the default and it seems to
have fixed the problem. I haven't nailed down what SP2 has
changed to affect this but I am cured over here.... for now.

 

[John]

The scary question is, "Does Microsoft even know if it's a
problem," or worse yet, "Does Microsoft consider this a
good feature and want to keep it that way?"

 

[Alan Morris\(MSFT\)]

Yes, you will get a little bit of performance back by enabling the sharing
ports in the Firewall exceptions and stopping, then restarting the Print
Spooler server. When making your default printer a local printer, the
application does not have to enumerate the remote server when displaying a
print dialog.

--
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.

 

[Guest]

I suppose by "local printer" you mean one connected via LPT(n)? I have my
default printer set to be PDFCreator, which is a local program that creates
its own port. I've also tried the Microsoft Office Document Image Writer
(again uses its own port). Neither prevents the enumeration. Unfortunately,
I don't have a "local printer" because this is a laptop used for constant
travelling. All of my printers are remote.

BTW, the Firewall is turned off completely on this laptop. I've even tried
disabling it on all network adapters as well. If it is the Firewall that is
still causing the delay, perhaps you could file this as a bug report?

# m a r t y

Yes, you will get a little bit of performance back by enabling the sharing
ports in the Firewall exceptions and stopping, then restarting the Print
Spooler server. When making your default printer a local printer, the
application does not have to enumerate the remote server when displaying a
print dialog.

--
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.

The scary question is, "Does Microsoft even know if it's a
problem," or worse yet, "Does Microsoft consider this a
good feature and want to keep it that way?"