From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Underwood Subject: Re: RV: Serial printer problem Date: Sun, 13 Jul 2003 20:50:39 -0500 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <20030714015039.GE1031@dbz.icequake.net> References: <000101c3499c$9ff427d0$0500a8c0@skuda> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <000101c3499c$9ff427d0$0500a8c0@skuda> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-msdos@vger.kernel.org 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, , icq=10317253