X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=M+Xwx0rEmFnkZF3E
	UlYqD2WPLkl0nkivu2wPPm1u9RDKbI7/PILvr3unDlI/js8W9WFftojSTXUqEv9v
	8GCBobqB1FRCYluvKqtZ3DMp8h8hI4K/t75hZFLLoOzVAk6kRXTs6le03Q1l/IYK
	uDjxqOfHEvfhk4KD2h2CtTESPkw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=pLQ7q2OQ5aGDHQOOHsmH9l
	E/lFI=; b=DFa7IqfJO/uxMxdSnxLqF6DZNt54j77Kc8sOEf3yhvQGQwXv3XQPzO
	tcHWIQb6zW/xgS4JNpkSrpJSXTuZHaXAppIdA0HrISzUoyT70C2wN+4BK35BfMSl
	xzLD8wmQJQJBpNFVrYpInpGMUcN9q+W37duzluvR83dMRNSyeVfNY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtpback.ht-systems.ru
Date: Thu, 27 Mar 2014 13:49:32 +0400
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <258119112.20140327134932@yandex.ru>
To: David Masterson <dsmasterson AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: LPR problem ?
In-Reply-To: <86d2h83z8y.fsf@gmail.com>
References: <86lhw4yzzh DOT fsf AT gmail DOT com> <681723866 DOT 20140326234117 AT yandex DOT ru> <8661n0r8xg DOT fsf AT gmail DOT com> <1803838655 DOT 20140327014037 AT yandex DOT ru> <86d2h83z8y DOT fsf AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, David Masterson!

>>> Windows has an 'lpr' command?!?
>>
>> Since the moment it gained TCP/IP support. Part of standard protocol
>> stack.  Along with ftp, telnet and other stuff.  And not to disappoint
>> anyone, but I've found that windows LPR works better in certain cases.

> Hmmmm.  Where (on Windows 8.1) is this 'lpr' command (or where is it
> supposed to be)?

Supposed to be in %SystemRoot%/System32/lpr.exe
Not using that Vista clone myself.

> What exactly is it used for?  How is it used?

Same as Cygwin's lpr... Sending jobs to LPD-enabled printer.
lpr /?

> I think I found it in a hidden temp directory, but I don't have any
> clues on how it is used.

Shouldn't be "in a temp directory"...

>>> It seems to be a Dell dialog box possibly produced by the printer
>>> driver.  I get it for anything that I try to print out to the printer
>>> under Windows.  It pops up in the lower right of the screen and tells
>>> you how far the printout has progressed as well as whether the ink
>>> cartridge is running out.  This, at least, gives me the clue that the
>>> 'lpr' command is "kicking" the printer if not quite kicking it
>>> properly.

>> No, but I can quite imagine this kind of annoying boxes. Epson do that
>> alot, so does HP last six or so years.  This just confirms that you
>> probably printing to localhost.  The answer could be that the
>> resulting job missing something critical, and is refused either by
>> printer driver or the printer itself.  If you print something from
>> Windows right after this failure of an experiemnt, don't your LPR'd
>> job gets out as well?  Another thought is that LPR works with printer
>> on a low level.  Which means... the document you are sending to print
>> must be preformatted in a language the printer understand. I.e. it
>> must be a plain text, PS, PCL or something of that kind.

> I had thoughts along this line too (missing formfeed at end of file?),
> but haven't devised a test yet.  Thought I might try the Windows 'lpr'
> you spoke of to see if it worked better.  The 'print' command seems to
> work, but I'm not sure if it has conversion problems (CRLF -> LF or vice
> versa) and, so, causes strange wraps in the output.  If it had more
> output controls, I'd probably just settle for that.

cat | lpr
^L^D^D
Should spit the sheet out of the printer at the very least.
That assuming this is a hardware printer that understand basic English.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 27.03.2014, <13:19>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple