public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Crawford <psc@sat.dundee.ac.uk>
To: Vedran Vucic <vedran.vucic@gmail.com>
Cc: Ivan Baldo <ibaldo@adinet.com.uy>,
	linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: printing
Date: Mon, 22 Nov 2010 11:17:31 +0000	[thread overview]
Message-ID: <4CEA514B.3090704@sat.dundee.ac.uk> (raw)
In-Reply-To: <AANLkTi=r+dACw46_bfugcJ=AUBF0MGprjj3gnscw3BBc@mail.gmail.com>

On 20/11/10 20:38, Vedran Vucic wrote:
> Hello,
>
> The first option based on lpr -P Laserprinter command did not work
> The second option based on cat command did not produce any files in tmp.
>
> Any suggestions?
>
> Thanks,
>
> Vedran

Are you sure it is printing to 'lpt' and not doing something suspect 
going directly to I/O address 0x378 (where the printer port is located)?

Do you know anything about how the software normally prints?

Regards,
Paul

  reply	other threads:[~2010-11-22 11:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 23:18 printing Vedran Vucic
2010-11-18 23:52 ` printing Ivan Baldo
2010-11-19  0:02   ` printing Vedran Vucic
2010-11-19  0:14     ` printing Ivan Baldo
     [not found]       ` <AANLkTin8-qGJ12--1RdfPT-sFB9=dS6Qx11SayLUda+a@mail.gmail.com>
2010-11-20 12:49         ` printing Ivan Baldo
2010-11-20 20:38           ` printing Vedran Vucic
2010-11-22 11:17             ` Paul Crawford [this message]
     [not found]           ` <AANLkTimV3u_wcGxv+p=aBRqEtkfgyXpkgiTS8H3srAWC@mail.gmail.com>
2010-11-22 23:32             ` printing Ivan Baldo
2010-11-22 23:54               ` printing Mike McCarty
2010-11-23  7:30               ` printing Vedran Vucic
2010-11-23  8:54                 ` printing Andrew Joakimsen
2010-11-23 18:36                   ` printing Vedran Vucic
2010-11-23 19:58                     ` printing Mike McCarty
2010-11-23 22:48                       ` printing Vedran Vucic
2010-11-26  1:15                         ` printing Andrew Joakimsen
2010-11-26  7:56                           ` printing Vedran Vucic
2010-11-26 10:31                             ` printing Frantisek Hanzlik
2010-11-27  7:42                               ` printing Vedran Vucic
2010-11-27 15:44                                 ` printing Frantisek Hanzlik
2010-11-27 16:10                                 ` printing Frantisek Hanzlik
2010-11-27 16:37                                   ` printing Vedran Vucic
2010-11-27 17:44                                     ` printing Frantisek Hanzlik
2010-11-27 18:53                                       ` printing Vedran Vucic
2010-11-27 20:08                                         ` printing Frantisek Hanzlik
2010-11-27 21:12                                           ` printing Vedran Vucic
2010-11-28  2:20                                             ` printing Frantisek Hanzlik
2010-11-29  6:10                                               ` printing Vedran Vucic
2010-11-29  7:09                                                 ` printing Frantisek Hanzlik
2010-11-19  7:11 ` printing Andrew Joakimsen
2010-11-19 11:35   ` printing Vedran Vucic
2010-11-29 18:39 ` printing Ken Heard

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=4CEA514B.3090704@sat.dundee.ac.uk \
    --to=psc@sat.dundee.ac.uk \
    --cc=ibaldo@adinet.com.uy \
    --cc=linux-msdos@vger.kernel.org \
    --cc=vedran.vucic@gmail.com \
    /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