I do volunteer work for a historical association. The association received from the municipality new second hand hardware.
Dell Optiplex 3010. Processor Intel core i3-3220 CPU 3.30 Ghz, 4 GB Ram, Windows 10 Pro version 1703, build 15063.674

The installation of Calamus 2015 went fine but ...

It takes ages to load winprint.cdt. Today for instance winprint.cdt was after 5 minutes still not loaded. Then I lost my patience and minimized the window which seems to provoke Calamus to load winprint and the rest of the drivers.

The printer is a Ricoh MP C3004 used in a network.

gdiprn.log
<URL:[www.dropbox.com];


Any idea what can be done to load Calamus faster?

Please check which Windows printer driver is the default one when you launch Calamus. Maybe you might want to switch the default driver and check if Calamus behaves in a different way. I usually use any physical printer's driver as the default one and Calamus SL 2015 loads fine without any delay.

Grüße / Greetings / Groetjes / Salutations,
Ulf Dunkel

Calamus starts very fast with for instance 180dpi.cdt but if I change it back to winprint.cdt inside Calamus it takes ages before winprint.cdt get loaded.

For test purpose I installed quite some time ago an old version (2006) of Calamus on another windows 10 pc. No problem with winprint at all untill today.
As said Calamus was installed for test purpose so it isn't used often. I really can't tell at which point the problem started to occur.
But right now winprint.cdt takes ages to load. BTW: the test pc only has only one printer, a brother whatever

I wonder if this has something to do with windows updates. The test pc runs windows 10 home, version 1703, build 15063.726. That update dates from 14/11.



Edited 1 time(s). Last edit was 6 years ago by tos4ever. (view changes)

The issue is situated somewhere between WinPrint.CDT and the Windows printer driver which doesn't seem to reply to WinPrint's requests in an appropriate time
Maybe you can find some more detailed information about this issue in C:\Calamus\gdiprn.log - or in the same file situated somewhere else on your drive C.

Grüße / Greetings / Groetjes / Salutations,
Ulf Dunkel

I've found the solution. It turned out to be a windows 10 setting:
"Let Windows manage default printer" was set on. Switch off that option solved the problem.

Martin

That's a really annoying "feature" of Windows 10. I always want to keep control over the used printer drivers myself. I'm glad you found out yourself.

Grüße / Greetings / Groetjes / Salutations,
Ulf Dunkel