Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Thu, 18 Nov 1999 10:35:01 -0600 (CST) From: "M. R. Brown" To: Philippe PUJAS cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: IO PORT ACCESS UNDER NT In-Reply-To: <3.0.1.32.19991117173745.00971920@194.199.229.198> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII NT by its nature doesn't allow direct hardware access to _ANY_ user program, only device drivers are allowed to get low-level with your hardware, and writing one is not a walk in the park :) You can search the net for a generic NT device driver that allows arbitrary I/O port access using IOCTLs, or you can roll your own. Even the practice of writing directly to I/O ports is depreciated under Windows 9x, as 9x "attempts" to do some hardware management. To my knowledge, cygwin doesn't support any functions regarding ioport access (think about it, does VC++ have any methods of rw I/O ports?). Marcus On Wed, 17 Nov 1999, Philippe PUJAS wrote: > I want to manage directly ioport from inp/outp (inb,outb) commands under > > Cygwin20.1/NT4. > > 1st These instructions don't exist on Cygwin20.1 > > 2nd I try the assembler routines from the FAQ and I get the following > > message : handle_exceptions: Exception STATUS_PRIVILEGED_INSTRUCTION > > > > Thank you for your help. > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com