Unfortunately, it doesn't. I am using the 20051117 snapshot from the cygwin1.dll, but I still get the same error.
It's not critical, but printing using enscript is easier than pointing and clicking in the explorer. Btw. I compiled enscript 1.6.3-9 and the uid error is gone. Regards, Jurgen Corinna Vinschen <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 2005-11-23 01:39 PM Please respond to cygwin@cygwin.com To cygwin@cygwin.com cc Subject Re: lpr error (Was :Re: Enscript error with passwd uid field (enscript-1.6.3-3)) Classification On Nov 23 12:49, Jurgen Defurne wrote: > I do have a real problem, but not with enscript, but with accessing > the printers. > > In the past, I could set PRINTER to //server/printershare, and use > enscript and lpr to print out my jobs. > > If I try to print now, I get the following message from lpr : > lpr: printer error: can't open '\\beqbrgbrg1ms0p1\psbe31.lnk' for > writing: The printer name is invalid. > > Upon further investigation, it seems that I cannot contact any > printers anymore from cygwin upon our print server, but I > can see those printers from my explorer. > > Ie. If I do 'ls //server' I should probably see the printer shares, > like any other share on the same server. No, the shares under //server are only of type disk, not type printer. Contacting the printer using the above $PRINTER variable should work in the snapshots. Please try the latest one from http://cygwin.com/snapshots/ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
