RE: Serial printer problem

["Miguel A. Rasero" <tecnico@bareacomunicaciones.com>]

Ryan,

Yes i am root but it seems that i do direct access the ms-dos doesn´t
gives the com1 name to hardware, if i try set mode with this setup dos
says me that no com1 dev name exists.

-----Mensaje original-----
De: linux-msdos-owner@vger.kernel.org
[mailto:linux-msdos-owner@vger.kernel.org] En nombre de Ryan Underwood
Enviado el: lunes, 14 de julio de 2003 19:07
Para: linux-msdos@vger.kernel.org
Asunto: Re: Serial printer problem



Miguel,

Are you root when you run dosemu (or using sudo)?  Direct port access
needs root.

Ryan

On Mon, Jul 14, 2003 at 04:03:25PM +0200, Miguel A. Rasero wrote:
> 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
> 

-- 
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