From: "Edenyard" <mail@edenyard.co.uk>
To: linux-msdos@vger.kernel.org
Subject: DOSemu serial port problem
Date: Fri, 31 Oct 2003 09:36:39 [thread overview]
Message-ID: <200310310937.AMB57095@msgdirector1.onetel.net.uk> (raw)
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"
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?) and it's running
in an Xterm window. I've an idea that I need to tell Linux to ignore
COM1 (ttyS0) so that the DOS programme can have it, but I don't know
whether this idea is sensible and, if so, how to do this. Is there
a parameter to give to a module or the kernel at boot time, or
something like that?
I've tried DOSemu V1.0.2 and get the same problem, so I'm sure it's
something I'm doing that's messing it up, rather than a DOSemu bug.
Hope this isn't a dumb question I'm asking. Thanks for any help
on this!
Gerald.
next reply other threads:[~2003-10-31 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 9:36 Edenyard [this message]
2003-10-31 12:09 ` DOSemu serial port problem Dr. Claudia Neumann
-- 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=200310310937.AMB57095@msgdirector1.onetel.net.uk \
--to=mail@edenyard.co.uk \
--cc=linux-msdos@vger.kernel.org \
/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