From: easlab@absamail.co.za
To: linux-msdos@vger.kernel.org
Cc: easlab@absamail.co.za
Subject: Is this project under control, or just 'suck it and see' ?
Date: Thu, 22 Jan 2004 12:12:11 -0500 [thread overview]
Message-ID: <S266308AbUAVRML/20040122171211Z+35803@vger.kernel.org> (raw)
> > Both users want to print to their
> > printers, and the printers are defined thru .dosemurc files in their
> > home directories. Once I run both users under the same login name, they
> > both use the same .dosemurc settings file and thus BOTH PRINT ON THE
> > SAME NETWORK PRINTER! Running one of DOSEMU session from other home
> > directory dosen't help either, because DOSEMU takes .dosemurc strictly
> > from user's home directory and this way the printing is directed to only
> > one printer.
>
Bartos-Elekes Zsolt wrote:-
> See the -f parameter for dosemu.bin to use a different .dosemurc, and start
> each dosemu client with a different .dosemurc, which contains only a line like
> $_printer = "rlp_1"
But where/how do I "See the -f parameter for dosemu.bin" ?
Is there applicable documentation with the binary-only package ?
Someone wrote:-
> > you seem to have multiple versions of dosemu lying around. Better
> > do some clean-up.
Yes I too have multiple installations/versions.
Still trying to drive par-port hex378 with a DOS-application.
Is the method of 'cleaning up' sytematically documented anywhere ?
How old is this project ?
Isn't it time that someone explained to the 'contributors' that
in scientific english "everywhere" is critically different from
"anywhere" ?
"... the dosemu binaries can reside everywhere in the system.
..you can call dosemu from everywhere." !!
Does any[not every]body KNOW how to drive port hex378 under
pre- ver. 1.1.99.1, or do you all just 'suck it and see' eg. "this works
for me" ?
== Chris Glur.
next reply other threads:[~2004-01-22 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 17:12 easlab [this message]
2004-01-23 22:17 ` Is this project under control, or just 'suck it and see' ? Bart Oldeman
2004-01-27 7:51 ` Bartos-Elekes Zsolt
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=S266308AbUAVRML/20040122171211Z+35803@vger.kernel.org \
--to=easlab@absamail.co.za \
--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