All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Can't access I/O ports with dosemu 1.0.2
Date: Fri, 27 Dec 2002 19:20:53 +0300	[thread overview]
Message-ID: <3E0C7DE5.6060902@yahoo.com> (raw)

Hello.

Brad Rodriguez wrote:
> I tried changing the ownership of the executable, and giving it setuid
> status, but that didn't work.  I tried running it as the root user; but 
> that wasn't allowed (I got a message saying I have to run as normal 
> user). 
Upgrade your dosemu.

> $_ports = "range 0x2f8,0x2ff range 0x320,0x327 range 0x378,0x37f range
> 0x3f8,0x3ff"
If any of that range is listed in
/proc/ioports, then dosemu will not
allow its usage to avoid the conflicts.
So you have to disable the in-kernel
support for that devices.

> The software I'm using requires direct hardware access to the LPT1
Yes, LPT is a weak part of dosemu unless
you do a simple printing.

> COM1, and COM2 ports
Why would the one require a direct
access to the COM ports? The support
for those is fairly complete under
dosemu.

> Are there some simple diagnostics that I can 
> perform to tell me if DOSEMU is configured properly?
-D9+Tci log would do.


             reply	other threads:[~2002-12-27 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 16:20 Stas Sergeev [this message]
2002-12-27 21:08 ` Can't access I/O ports with dosemu 1.0.2 Brad Rodriguez
2002-12-27 21:23   ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2002-12-27 22:14 Stas Sergeev
2002-12-27 15:52 Brad Rodriguez

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=3E0C7DE5.6060902@yahoo.com \
    --to=stssppnn@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.