From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: Can't access I/O ports with dosemu 1.0.2 Date: Fri, 27 Dec 2002 19:20:53 +0300 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <3E0C7DE5.6060902@yahoo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org 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.