public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 31 Oct 2003 13:09:53 +0100	[thread overview]
Message-ID: <200310311309.53315.dr.claudia.neumann@gmx.de> (raw)
In-Reply-To: <200310310937.AMB57095@msgdirector1.onetel.net.uk>

Hi!

Am Freitag, 31. Oktober 2003 10:36 schrieb Edenyard:
>    I'd very much appreciate help with this serial port problem:
>
>    I've installed DOSemu V1.1.99 from source an an Athlon and have
> got it running quite well on Slackware 9.1 (2.4.22 kernel). It
> recognises the DOS partition on the HDD, boots from the IBM DOS there
> and will run programmes like Xtree and Wordstar without any problems.
>
>    However, I have a programme written in Turbo Basic that accesses the
> DOS COM1 serial port hardware (UART registers, etc.) directly and I'm
> having trouble getting it to talk to the port properly under DOSemu.
> The port is a standard 16550A UART on the motherboard and works
> correctly under Linux.
>
>    This is the error message I get as DOSemu is coming up:
>
>       ERROR: PORT: conflicting devices: COM1 & std port io
>
>    The programme appears to be able to send out of the port but cannot
> get any data coming back in. I've set /etc/dosemu/dosemu.conf to deal
> with the COM1 port like this:
>
>       $_com1 = "/dev/ttyS0 irq 4"
>       $_ports = " device /dev/ttyS0 fast range 0x3f8,0x3ff"
>       $_irqpassing = "4"

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"
>
>    but I can't stop the 'conflict' message or get any data from the
> port into my programme. The remainder of the programme appears to work
> properly, even printing to what it thinks is LPT1.

>    I'm running DOSemu as root (which I believe I have to do in order to
> gget access to the UART at /dev/ttyS0 - is this true?) 
Don't run DOSemu as root. You don't have to. Give your user access to 
/dev/ttyS0 for example
crw-rw-rw-    1 root     dialout    4,  64 2003-10-31 12:42 /dev/ttyS0
and asign the user to the group dialout.

If it doesn't work, look for some programm, which blocks the /dev/ttyS0. I 
experienced the same problem, because XWindows wanted to asign a serial mouse 
to the COM port. After I commented out the lines in XF86Config-4, I could 
work with the COM port.

Regards

Claudia

  reply	other threads:[~2003-10-31 12:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31  9:36 DOSemu serial port problem Edenyard
2003-10-31 12:09 ` Dr. Claudia Neumann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-31 16:22 Edenyard
2003-11-02 13:30 ` Dr. Claudia Neumann
2003-11-02 16:39   ` Ged Haywood
2003-11-02 18:54     ` Robert Komar
2003-11-02 19:07     ` Stas Sergeev
2003-11-03 11:37 Edenyard
2008-06-28 10:03 Dosemu " Horváth András
2008-06-28 14:18 ` James Courtier-Dutton

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=200310311309.53315.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