I’ve just disabled the Auto config option on the printers, centrally on the server (which I presume the client picks up and honors), and it solved the problem. If the Office programs is triggering this repeatedly and then waits for answer, that could be the answer why everything comes to a grinding halt. The core of the problem here maybe that every time the printer is activated from the client it tries some kind of auto config, asking the printer of it capabilities, this takes a couple of seconds. Affected more than Office 2010, also 20 was suffering.
#Printing labels in word for mac 2011 drivers#
In my case it was KONICA MINOLTA Universal PCL drivers and printers. Documents with just a few pages they were able to use, but it was painfully slow. Yes! This solved a problem where machines on a slow link was unable to use the Office programs because of totally taxed down by their default printer. If a network printer is set as the default and it can’t find it, then why don’t we get a message to tell us to change to another printer driver so we can work in a fully responsive document? Most of us have many ‘printers’ listed these days - many of which aren’t even printers, but instead are printer drivers.
And guess what? The document responded beautifully! No more achingly long Not responding messages in the Word 2010 title bar no more watching the ‘spinning wheel of death’ (as I like to call it) while waiting and waiting for the Word document to respond because it was trying to talk to my network printer.īut I have to question WHY Microsoft still ties things like Word documents so closely to the default printer.
#Printing labels in word for mac 2011 pdf#
In my case, the default printer is not only a networked printer, but when I opened this 300+ page document, the printer was turned off (it was a Sunday and I don’t use the printer all the time, especially on weekends).Īfter following the advice of people in this forum thread, I changed my default printer on the Vista laptop to Adobe PDF (Microsoft EPS works well too, I believe). If the default printer is a networked printer, then there can be response issues. And there is! And it’s not related to Vista at all, but to how a Word document interacts with the default printer. So off to Google to see if there was an answer to this problem. I’ve been blaming Vista…īut when I started to edit a 300+ page Word 2010 document on my Vista laptop, the unresponsiveness was going to be a huge productivity drain. Word 2007 - and now Word 2010 - on my Vista laptop has often been very slow to load a document and to respond to a document command (like Save).
0 kommentar(er)
