From: "Dr. Claudia Neumann" <dr.claudia.neumann@gmx.de>
To: Edenyard <mail@edenyard.co.uk>
Cc: DOSemu Mailingliste <linux-msdos@vger.kernel.org>
Subject: Re: DOSemu serial port problem
Date: Sun, 2 Nov 2003 14:30:46 +0100 [thread overview]
Message-ID: <200311021430.46548.dr.claudia.neumann@gmx.de> (raw)
In-Reply-To: <200310311622.AMC47673@msgdirector1.onetel.net.uk>
Hi Edenyard,
Am Freitag, 31. Oktober 2003 17:22 schrieben Sie:
> Many thanks for your help, Claudia!
>
> You suggested:
> > try:
> > $_com1 = "/dev/ttyS0"
> > no entries in $_ports and $irqpassing.
> > make sure you have right access to /var/lock or make a directory
> > /home/user/dosemu/lock and say in .dosemurc
> > $_ttylocks = "/home/user/dosemu/lock"
>
> I tried that and I find that I can send data from my DOS programme
> out of the port and also receive data to my programme from the port,
> when I remove the $_ports and $irqpassing entries. I also no longer
> get any error messages. But...
>
> Unfortunately, all is still not well: the programme has to drive
> the port's RTS line to control an RS232 to RS485 convertor (the
> equipment at the other end is RS485). The RTS line has to be made high
> whilst the PC is transmitting and then set low immediately after
> transmision so that the remote equipment can send its response.
>
> Now I find with the settings that you suggest that, although the
> transmit and receive data is getting through, something other than my
> programme is controlling the RTS line. The result of this is that my
> programme cannot now transmit along the RS485 cable, because something
> is resetting RTS low after my programme has set it high but just
> before my programme's transmission starts.
>
> I have checked and Xwindows is not trying to use the port (as far as
> I can tell) for a mouse. My mouse is on /dev/psaux. There is a modem on
> /dev/ttyS1 but, as far as Linux is concerned, /dev/ttys0 is unused.
>
> Please could you suggest something that I can do to stop this.
> I don't understand why the system would let me transmit and receive
> using the port but at the same time interfere with just the RTS line....
> Do I need something to actually block the rest of the system from taking
> an interest in /dev/ttyS0, perhaps? What might be trying to use just the
> RTS line?
I am lost here. I don't know what a RTS line is.
The only suggestion I can make is:
make a
find /etc -type f -exec grep -l /dev/ttyS0 { } \;
and you get a list of files which have an entry of /dev/ttyS0. Look at every
file and find out if some other program uses /dev/ttyS0.
Or make the same with /var/log.
Hope that helps
cu
Claudia
next prev parent reply other threads:[~2003-11-02 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 16:22 DOSemu serial port problem Edenyard
2003-11-02 13:30 ` Dr. Claudia Neumann [this message]
2003-11-02 16:39 ` Ged Haywood
2003-11-02 18:54 ` Robert Komar
2003-11-02 19:07 ` Stas Sergeev
-- strict thread matches above, loose matches on Subject: below --
2008-06-28 10:03 Dosemu " Horváth András
2008-06-28 14:18 ` James Courtier-Dutton
2003-11-03 11:37 DOSemu " Edenyard
2003-10-31 9:36 Edenyard
2003-10-31 12:09 ` Dr. Claudia Neumann
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=200311021430.46548.dr.claudia.neumann@gmx.de \
--to=dr.claudia.neumann@gmx.de \
--cc=linux-msdos@vger.kernel.org \
--cc=mail@edenyard.co.uk \
/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