RE: Serial port direct access

RE: Serial port direct access

[Stas Sergeev]

Hello.

Miguel A. Rasero wrote:
> Well i forget to tell the list that i have updated the
> version to dosemu 1.1.5.0
Then you may not need a direct access
to serial port. Try the emulated access
again and in case it still fails, produce
a -D9+s log to see what's going wrong.
Attach your dosemu.conf with a log.

RE: Serial port direct access

[Miguel A. Rasero]

>Hello.

>Miguel A. Rasero wrote:
>> Well i forget to tell the list that i have updated the
>> version to dosemu 1.1.5.0
>Then you may not need a direct access
>to serial port. Try the emulated access
>again and in case it still fails, produce
>a -D9+s log to see what's going wrong.
>Attach your dosemu.conf with a log.

Hello.
I will get the printer tomorrow and i will send the log but i have tried
with this dosemu version too with the same result, because of this i
tried to get a direct access to com1, but i need the com1 dev name
because the program that i am trying to print uses this dev name. Do i
have any other way to get this direct acess with the dev name? Thanks.

RE: Serial port direct access

[Stas Sergeev]

Hello.

Miguel A. Rasero wrote:
> Here i have the logs, i have created two logs, one from a normal 
> printed report, more short, and other that fails to print
Hmm, your app uses an int14 for data
writes with no IRQ handling. This
shouldn't make any problems.
This may be a problem with something
else I think. If you are using a
freedos under dosemu, try the MS-DOS
instead. Try to bypass your config.sys
and autoexec.bat to see if probably some
external program causes troubles, etc.
I don't see any problems in the log,
and since it doesn't work for you also
under win4lin, I think the problem is
elsewhere.

RE: Serial port direct access

[Miguel A. Rasero]

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hi Stas,
Here i have the logs, i have created two logs, one from a normal printed
report, more short, and other that fails to print i would be very
pleased if you can see it and reply me with your recommendation.

-----Mensaje original-----
De: Stas Sergeev [mailto:stsp@aknet.ru] 
Enviado el: miércoles, 10 de septiembre de 2003 19:44
Para: Miguel A. Rasero
Asunto: Re: Serial port direct access


Hello.

Miguel A. Rasero wrote:
> Now i have the logs and a bunch of more tests done, it doesn´t really
Your log is very incomplete, there is nothing
about an actual data transfer. You must run
dosemu with the -D9+s (as you did), start printing,
wait until it fails, and only then stop the dosemu.
Then you'll get a complete log.

> seems a dosemu problem, i don´t know if it is an application problem
or
> other but i have tested from other emu like win4lin that provides
direct
> access to serial port (without kernel module loading) and i have the
Does the win4lin provides a direct access to the
serial port, or the emulated access like dosemu
does?

> understand it.I would be very thankful if you could help me. I could
> think that it´s a linux kernel problem but if i test from a bash
command
> line "cat largereport > /dev/ttyS0" it works fine.
Well, the emulated access to the serial port is
a tricky thing. The main problem is that dosemu
is not able to handle the interrupts from the
serial port, so it maintains a virtual interrupt
status. "cat xxx >/dev/ttyS0" doesn't have any
limitations like that apparently.


[-- Attachment #2: printfail.zip --]
[-- Type: application/octet-stream, Size: 8830 bytes --]

RV: Serial port direct access

[Stas Sergeev]

Hello.

Miguel A. Rasero wrote:
> Anyone can help me please?
Probably not.
In one of your messages you wrote:
> Hi, i have installed dosemu dosemu-1.0.2.1
Is this still true?

> I have a big trouble with this misconfiguration, i have
> to fix now or my boss will kill me.
Well, then using such an outdated dosemu version
will mean a death for you, so be prepared... or
update your dosemu? :)
It is just that most people are ignoring the
help requests when people are using an outdated
versions.

RE: Serial port direct access

[Miguel A. Rasero]

Well i forget to tell the list that i have updated the version to dosemu
1.1.5.0 and it fix one of my problems with keyboard mapping but not my
worst problem that is direct access to com1. thanks.

-----Mensaje original-----
De: linux-msdos-owner@vger.kernel.org
[mailto:linux-msdos-owner@vger.kernel.org] En nombre de Stas Sergeev
Enviado el: jueves, 17 de julio de 2003 20:48
Para: linux-msdos@vger.kernel.org
Asunto: RV: Serial port direct access


Hello.

Miguel A. Rasero wrote:
> Anyone can help me please?
Probably not.
In one of your messages you wrote:
> Hi, i have installed dosemu dosemu-1.0.2.1
Is this still true?

> I have a big trouble with this misconfiguration, i have
> to fix now or my boss will kill me.
Well, then using such an outdated dosemu version
will mean a death for you, so be prepared... or
update your dosemu? :)
It is just that most people are ignoring the
help requests when people are using an outdated
versions.

-
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

Serial port direct access

[Miguel A. Rasero]

Hi i am having trouble with a serial printer, i have tested anything
from the mailing list to do it work correctly but i haven´t obtained
positive results so i want to make a direct access to com1, i have
tested many ways to do this but i can´t use the COM1 name, ms-dos says
me that com1 isn´t a valid device name if i use direct access.i have
tested with and without serial support in linux kernel.

$_com1 = ""      
or
#$_com1 = ""     

$_ports = "fast range 0x3f8,0x3ff" 
or
$_ports = "device /dev/ttyS0 fast range 0x3f8,0x3ff"          
or
$_ports = "0x3f8"

$_irqpassing = "4"

Anyone can say me if this is normal? Or if i am doing anything
incorrect, i don´t know if direct access would give me the com1 dev name
in ms-dos or not, thank you by the help.

-
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