Serial printer problem

Serial printer problem

[Miguel A. Rasero]

Hi, i have installed dosemu dosemu-1.0.2.1 and 
configure dosemu.conf to get direct access to 
/dev/ttyS0, then i configure in dosemu the com1 port 
with the "mode com1:9600,n,8,1,p" when i print it 
works fine but when i print anything large, i am using 
a pos printer, when i print a simple ticket works fine 
and cut the paper too, but when i print the whole day 
sales resume, the printer begins to print the lines 
upon others and doesn´t cut the paper, do you know what 
can be the problem? the printer and the program that i 
am using for pos has been tested in a normal ms-dos 
Computer.

I have other problem, i can´t use the (Ntilde) (Ñ) from 
dosemu, do you know any way to do this?

Thanks by the help and sorry for my poor english 

-
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

RE: RV: Serial printer problem

[Miguel A. Rasero]

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 1:21
Para: linux-msdos@vger.kernel.org
Asunto: Re: RV: Serial printer problem



Hi Miguel,

On Sun, Jul 13, 2003 at 10:13:29PM +0200, Miguel A. Rasero wrote:
> I have tested this:
> 
> 	stty -F /dev/ttyS0 crtscts
> 	
> 	setserial /dev/ttyS0 uart 16450
> 
> And in ms-dos: mode com1:96,n,8,1,p
> 
> But i have the same problem yet, all works fine if the report it?s
short
> but when it has more lines (>25) it stops the printing, i have tested
> from the linux directly with cat /etc/hosts > /dev/ttyS0 in a large
> hosts file but it works good, anyone can help me please?
>
*snip*
>
> Hi, i have installed dosemu dosemu-1.0.2.1 and 
> configure dosemu.conf to get direct access to 
> /dev/ttyS0, then i configure in dosemu the com1 port 
> with the "mode com1:9600,n,8,1,p" when i print it 
> works fine but when i print anything large, i am using 
> a pos printer, when i print a simple ticket works fine 
> and cut the paper too, but when i print the whole day 
> sales resume, the printer begins to print the lines 
> upon others and doesn?t cut the paper, do you know what 
> can be the problem? the printer and the program that i 
> am using for pos has been tested in a normal ms-dos 
> Computer.

When you say the printer "stops printer" do you mean it stops printing
altogether, or that it stops feeding the paper and keeps printing over
and over the same line?

> I have other problem, i can?t use the (Ntilde) (Ñ) from 
> dosemu, do you know any way to do this?

Perhaps you need to change the character set options in dosemu.conf?
There are term_char_set for 1.0.2, and for the development versions
internal_char_set and external_char_set.

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


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
Later than this i can print large files with cat so i was very happy and
i went to probe in dosemu trusted but in dosemu the printer do the same
thing!!!, and it´s exactly the same that linux "cat largefile >
/dev/ttyS0" did before i applied the commands showed above. Do you know
any way to resolve that o how i can give a direct access to dos, i saw
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.

-
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

Re: RV: Serial printer problem

[Ryan Underwood]

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

Re: Serial printer problem

[Mike Keithley]

Perhaps a formfeed isn't being passed?



On Sun, 13 Jul 2003, Miguel A. Rasero wrote:

-Hi, i have installed dosemu dosemu-1.0.2.1 and
-configure dosemu.conf to get direct access to
-/dev/ttyS0, then i configure in dosemu the com1 port
-with the "mode com1:9600,n,8,1,p" when i print it
-works fine but when i print anything large, i am using
-a pos printer, when i print a simple ticket works fine
-and cut the paper too, but when i print the whole day
-sales resume, the printer begins to print the lines
-upon others and doesn´t cut the paper, do you know what
-can be the problem? the printer and the program that i
-am using for pos has been tested in a normal ms-dos
-Computer.
-
-I have other problem, i can´t use the (Ntilde) (Ñ) from
-dosemu, do you know any way to do this?
-
-Thanks by the help and sorry for my poor english
-
--
-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

RE: Serial printer problem

[Miguel A. Rasero]

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

Re: Serial printer problem

[Ryan Underwood]

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

RE: Serial printer problem

[Miguel A. Rasero]

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