From: Frank Cox <theatre@sasktel.net>
To: Jakub Klawiter <jklawiter@gmail.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: lag while printing and serial redirect
Date: Tue, 13 Dec 2016 11:04:36 -0600 [thread overview]
Message-ID: <20161213110436.0efde9b82773a8dc3875db59@sasktel.net> (raw)
In-Reply-To: <CAOpyoqZVPJSdZSeTh4fF+my63_pHfa7xnNvS=FpXiNFZWK-0ZA@mail.gmail.com>
On Tue, 13 Dec 2016 14:26:34 +0100
Jakub Klawiter wrote:
> $ echo test | lpr -l
> the printer starts to print immediately.
>
> But from dosemu if i'll try:
>
> C:>echo test > lpt1:
>
> it's working but there is 3-4 seconds lag before it starts to print.
> Where can i look to fix it?
That's the way that lpr works under dosemu. It's my understanding that the objective is to print a whole page at a time because that's how modern printers work. Since most dos programs don't send a page end/page break, dosemu just waits for a few seconds to see if anything more is coming; if not the page is assumed complete and send it to the printer.
--
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
next prev parent reply other threads:[~2016-12-13 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 13:26 lag while printing and serial redirect Jakub Klawiter
2016-12-13 17:04 ` Frank Cox [this message]
2016-12-13 21:13 ` Stas Sergeev
2016-12-14 14:32 ` Jakub Klawiter
2016-12-14 20:00 ` Stas Sergeev
2016-12-15 16:18 ` Jakub Klawiter
2016-12-15 21:57 ` Stas Sergeev
2016-12-15 22:10 ` Jakub Klawiter
2016-12-15 22:18 ` Stas Sergeev
2016-12-19 13:34 ` Jakub Klawiter
2016-12-19 13:53 ` Jakub Klawiter
2016-12-20 0:19 ` Stas Sergeev
2016-12-20 20:37 ` Jakub Klawiter
2016-12-21 21:22 ` Stas Sergeev
2016-12-25 14:03 ` Jakub Klawiter
2016-12-25 16:58 ` Stas Sergeev
2016-12-27 22:44 ` Jakub Klawiter
2016-12-28 20:04 ` Stas Sergeev
2016-12-20 0:17 ` Stas Sergeev
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=20161213110436.0efde9b82773a8dc3875db59@sasktel.net \
--to=theatre@sasktel.net \
--cc=jklawiter@gmail.com \
--cc=linux-msdos@vger.kernel.org \
/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