From: "Miguel A. Rasero" <tecnico@bareacomunicaciones.com>
To: linux-msdos@vger.kernel.org
Subject: RE: Serial printer problem
Date: Mon, 14 Jul 2003 16:03:25 +0200 [thread overview]
Message-ID: <000001c34a10$b2da02b0$0500a8c0@skuda> (raw)
In-Reply-To: <20030714015039.GE1031@dbz.icequake.net>
Hi Ryan,
When i try to do direct access like you say, ms-dos gives me an error
that com1 isn´t a valid name device.
Hi Miguel,
On Mon, Jul 14, 2003 at 02:12:32AM +0200, Miguel A. Rasero wrote:
> Hi ryan
> I have saw the charset options in the new technical readme in the
> development versions but i have not tested yet because i am having
very
> trouble with the printer that it?s more important to me, well i take
to
> 5 hours proving options with setserial and stty, i realized wich when
i
> tried a "cat largefile > /dev/ttyS0" in linux i had the same result,
and
> the end of the printed page character disorder and not the whole file
> printed, i had tested the closing_wait "infinite" like i saw in the
> printing howto but it didn?t worked, i found in a old newsgroup a
> message that recommends this.
> stty -F /dev/ttyS0 opost onlcr tab3 crtscts
> setserial /dev/ttyS0 uart 16450
Hmm, what kind of motherboard/serial card do you have (does it really
only
have a 16450 on it?) and what kind of printer is this?
> in doc but i don?t understand very well, i need that the dos knows
which
> is com1, it doesn?t works if i add to the ports list 0x3f8 without say
> it that it?s com1.
Yeah, you need to add 0x3f8 to $_ports, and probably 4 to $_irqpassing
assuming it is on the standard COM1 port. That should accomplish the
direct access to com1. Remember to remove anything from "$_com1" that
you put in there.
--
Ryan Underwood, <nemesis at icequake.net>, icq=10317253
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-07-14 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 0:12 RV: Serial printer problem Miguel A. Rasero
2003-07-14 1:50 ` Ryan Underwood
2003-07-14 14:03 ` Miguel A. Rasero [this message]
2003-07-14 17:06 ` Ryan Underwood
2003-07-14 20:54 ` Miguel A. Rasero
-- strict thread matches above, loose matches on Subject: below --
2003-07-13 1:13 Miguel A. Rasero
2003-07-14 2:56 ` Mike Keithley
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='000001c34a10$b2da02b0$0500a8c0@skuda' \
--to=tecnico@bareacomunicaciones.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