X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4AA473858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1687205376;
	bh=qbO4UPCY9AXcKA56K8sXes0YCZ+B1EPnITbUFJF3eyA=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=ujJRyzYbiTegd/XTOpSC3kAFE6qwsRvTHyyWiLQ3iTSA1rcK5vAxgAjEFp+68yT7Q
	 eMUZ5ndmFm6bC7+7rJTojT+cl8oQf0xDQJOU5UL11TKZX5D74B2tUzvCLdoZX81Vor
	 zL83wJWzCKZcIV1271PpXE3xziSmTwo7QcUi7ymE=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 4BB483858D1E
Message-ID: <7ee6a27e-22b0-8409-12be-224dc7a1fd93@t-online.de>
Date: Mon, 19 Jun 2023 22:09:06 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.12.0
Subject: Re: Use Real LPT port with Cygwin?
Content-Language: en-US
To: cygwin AT cygwin DOT com
References: <!&!AAAAAAAAAAAuAAAAAAAAAEIv7Z/V4xxNu3wc77DZsnUBAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAChMbcbP5T3QbCwSNhB2sAqAQAAAAA=@twcny.rr.com>
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAEIv7Z/V4xxNu3wc77DZsnUBAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAChMbcbP5T3QbCwSNhB2sAqAQAAAAA=@twcny.rr.com>
X-TOI-EXPURGATEID: 150726::1687205358-097C5714-EABF3AB2/0/0 CLEAN NORMAL
X-TOI-MSGID: 0be7fed0-c50e-4ed1-80c5-c80e54ff6b8d
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00, FREEMAIL_FROM,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: =?utf-8?q?Hans-Bernhard_Br=C3=B6ker_via_Cygwin?= <cygwin AT cygwin DOT com>
Reply-To: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= <HBBroeker AT t-online DOT de>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Am 18.06.2023 um 21:35 schrieb tlake--- via Cygwin:
> I can use an emulated LPT port to a shared network printer from Cygwin but
> I'd like to print to a local LPT port also.

> The local printer has no IP address. Is it possible to print to a physical
> LPT port?>   
> 
> If I do this:

> 	ls > LPT1:

> a file called LPT1: is created on the hard drive rather than sending the
> data to the printer on LPT1:

The fact that works at all is a remarkably ancient quirk that made it 
into MS-DOS by way of it trying to emulate even older quirks from CP/M. 
We're talking 1970s computing, there.  Because the dogma of backwards 
compatibility is so strong in Seattle, this quirk is still available in 
Windows to this very day.

But as it's a massive DOS-ism that really does not fit into he POSIX 
world at all, it's not entirely surprising that it doesn't reproduce in 
a Cygwin shall, just like that --- Linux doesn't do that, either.

What you do get instead is a Unix-style /dev tree of device 
pseudo-files.  I might be cool if that gave you a /dev/lpt1 on Cygwin, 
but alas, I don't think it does.

What you do get is a /proc/sys/DosDevices/Global tree.  A printer, if 
existing as a Windows device "LPT1", should show up there as a character 
device.

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