X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=BAYES_05 X-Spam-Check-By: sourceware.org References: Date: Tue, 16 Dec 2008 08:12:36 -0800 (PST) From: Rick Rankin Subject: Re: Printing to network printers To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <189950.11753.qm@web65613.mail.ac4.yahoo.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > From: Steve Rainbird > > How can I print to a network printer? > > I know if its attached to a server I can say > > lpr -d //server/printer file > > > But what do I do if the printer isn't attached to a server and is just a printer > on the network? You should be able to add the printer through control panel, which will give it a local name. You can then use that name as the argument to -d. It's usually simpler if the name doesn't contain any spaces, but that's not a requirement. Many network printers also provide a UNC-style name (//server/printer), even though they're not directly connected a server, per se. If you can browse to the printer when you're adding it, you should be able to use that name directly. It all depends on how the provides its networking capability. I assume you know that lpr is quite stupid, i.e., it just spools the file, assuming that it is already correctly formatted for the target printer. It was originally written to spool a postscript file to a postscript printer. It didn't need to do any formatting. --Rick -- 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/