From: "Jaime Herazo B." <jherazo@linuxfreemail.com>
To: linux-msdos@vger.kernel.org
Subject: Two printing problems
Date: Thu, 11 Jul 2002 11:06:29 -0500 [thread overview]
Message-ID: <20020711160629.GC1769@jherazob.myip.org> (raw)
Hi. I've been using dosemu to run an accounting package on a place i
assist from time to time. I has worked well (apart from the fact that in
the console the ascii borders and decorations look weird, but it's no
big deal), but this week two new machines were added there, one that had
been used to write letters and stuff like that in staroffice (it has
Mandrake 7.2 and dosemu 1.0.1-6), named Darwin, and another one, a brand
new machine with Mandrake 8.2 (dosemu 1.0.1-8) called Server (it doubles
as a file server for the rest now, and i know, it's a dumb name, but it
was necessary, long story :) ). Both use lpr because i've had problems
with cups and Epson dot-matrix printers, so it's very standard stuff.
The problems are: In Darwin, printing doesn't work from dosemu. The
config files are correct, it's pointing to the right printer in the
printcap (the only one in there anyway), and the user can print directly
("lpr sometextfile.txt" works just fine). Just to be sure i added
"c_printer" to that user in the dosemu.users file, but it didn't worked
anyway. I used logging as stated in the HOWTO, and i found that the
temporary file it creates when ordered to print something is indeed
created, but it doesn't print anyway. Thinking it was some permissions
issue, i ran it as root and tried to print, with the same results. Not
even "type somefile.txt > prn" works. The configfiles are in general the
ones that came with the dosemu RPM, and had worked well in the other
computers.
In server, everything works, but printing has a problem, and is that
when printing from dosemu, the printer makes a pause after each text
line, making it annoyingly slow. I haven't thoroughly checked this one,
as i was dedicated to fixing Darwin, so you can suggest even the obvious.
I'm out of ideas, so i'd appreciate suggestions on these problems.
---------------------------------------
Microsoft: Writing viruses has never been easier!
Microsoft: The company that made email dangerous
Microsoft: Having a false sense of security was never so expensive
-----
Jaime Herazo Barrios /"\
jherazo at linuxfreemail dot com \ / ASCII Ribbon Campaign
ICQ number: 14721935 X Against HTML Mail,
Yahoo! id: jherazo_1999 / \ and News Too
next reply other threads:[~2002-07-11 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 16:06 Jaime Herazo B. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-11 17:00 Two printing problems Greg LaBossiere
2002-07-11 18:38 ` Jaime Herazo B.
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=20020711160629.GC1769@jherazob.myip.org \
--to=jherazo@linuxfreemail.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