search for: construct_nt_devicemod

...t the print jobs in any way. Gerald Carter wrote: >| This messages are side-effects of setting the printername >| To "\\servername\drivername", when assigning drivers to >| printers. >| AFAIK the message is caused by the safe_strcpy call in >| printing/nt_printing.c : construct_nt_devicemode () >| or get_a_printer2 (). >| >| The MAXDEVICENAME macro is set to 32 whereas printername plus >| servername is usually longer than that. > > This is the size defined by MS. (see MSDN and one the > wire traces). Hello Jerry, After the upgrade from 3.0.4 to 3.0.6 I also...

I updated one of my file servers to 3.0.6, and while file serving is improved (no M$-Office file already open messages), every time I access a printer my logs flood with messages like to those below. It seems I can set printer properites, etc... but when I print the jobs seem to go to never-never land (still researching where the jobs go). [2004/08/20 08:46:27, 0]