X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Can't print because .lnk makes printer name invalid Date: Mon, 24 Apr 2006 08:41:36 -0500 Message-ID: From: "Rockefeller, Harry" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k3ODfXaG020426 Jay Abel wrote: >I would love to know how to get lpr to just print directly to the printer's >IP address, but the above isn't as bad as it seems, since it keeps windows >and cygwin print jobs in sequence, and visible in the queue. > >I'm sure there is a better way, but the above worked for me. With help I received from this list I found that the Windows (DOS?) lpr command *does* work. So, my latest workaround is to create a couple of aliases which call the Win lpr command instead of the Cygwin one. From my ~/.bash_login and ~/.bashrc files: alias lprbw='/cygdrive/c/WINNT/system32/lpr -S ntserver1 -P sw-txt1 ' alias lprcl='/cygdrive/c/WINNT/system32/lpr -S ntserver1 -P hpcj1 ' Maybe something like this will also work for you? -- 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/