public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Salter-Duke <b_duke@octa4.net.au>
To: David Means <dmeans@the-means.net>
Cc: cygwin@cygwin.com
Subject: Re: Printing locally.
Date: Sun, 03 Mar 2002 00:27:00 -0000	[thread overview]
Message-ID: <20020303175530.A316@BSALTERDUKE1> (raw)
In-Reply-To: <1015130447.12379.1.camel@milo>; from dmeans@the-means.net on Sat, Mar 02, 2002 at 11:40:47PM -0500

On Sat, Mar 02, 2002 at 11:40:47PM -0500, David Means wrote:
> I don't have my cygwin machine handy, so I've got to ask:
> 
> how about this:
> 
> cat a.txt > /cygdrive/c/WINNT/lpt1
> 
> that's probably not the ultimate solution, but does it work?

No. It reports nothing and does nothing. There is nothing in any printer
queue.

PRINT a.txt

reports that <full path>/a.txt is currently being printed, but again
nothing happens and there is nothing in the queues.

Thanks for the suggestion. I remain very puzzled.

Brian.
 
> David
> 
> 
> 
> On Sat, 2002-03-02 at 21:52, Brian Salter-Duke wrote:
> > On Sat, Mar 02, 2002 at 02:45:57AM -0500, Paul McFerrin wrote:
> > > Brian:
> > > 
> > > I used to be able to print from cygwin by refering to /dev/lpt1
> > > 
> > > -paul mcferrin
> > 
> > There is no /dev directory! "which lpt1" gives "/cygdrive/c/WINNT/lpt1",
> > but typing "lpt1 file" gives permission denied and looking in WINNT with
> > Windows Explorer I do not find it. I'm even more puzzled.
> > 
> > Cheers, Brian.
> > 
> > [my original query about how to print to a local printer deleted.]
> >  
> > -- 
> >            Brian Salter-Duke (Brian Duke) b_duke@octa4.net.au  
> > Honorary Fellow in Chemistry, NT University, Darwin, NT 0909, Australia.
> >  Phone 08-89881600.    Fax 08-89881302.    http://lacebark.ntu.edu.au/
> > 
> > --
> > Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> > Bug reporting:         http://cygwin.com/bugs.html
> > Documentation:         http://cygwin.com/docs.html
> > FAQ:                   http://cygwin.com/faq/
> -- 
> 
> No trees were killed in the sending of this message. However,
> a large number of electrons were terribly inconvenienced.



-- 
           Brian Salter-Duke (Brian Duke) b_duke@octa4.net.au  
Honorary Fellow in Chemistry, NT University, Darwin, NT 0909, Australia.
 Phone 08-89881600.    Fax 08-89881302.    http://lacebark.ntu.edu.au/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2002-03-03  8:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 23:23 Brian Salter-Duke
2002-03-01 23:44 ` Paul McFerrin
2002-03-02 18:54   ` Brian Salter-Duke
2002-03-02 20:40     ` David Means
2002-03-03  0:27       ` Brian Salter-Duke [this message]
2002-03-03  2:50 fergus at bonhard dot uklinux dot net
2002-03-03 16:25 ` Brian Salter-Duke
2002-03-04  8:26   ` Larry Hall (RFK Partners, Inc)
2002-03-05  1:24     ` Brian Salter-Duke
2002-03-05  8:17       ` Rick Rankin
2002-03-05 13:07       ` Larry Hall (RFK Partners, Inc)
2002-03-05 15:39 Karl M
2002-03-06 15:03 Heribert Dahms

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020303175530.A316@BSALTERDUKE1 \
    --to=b_duke@octa4.net.au \
    --cc=cygwin@cygwin.com \
    --cc=dmeans@the-means.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).