windows port access

[Chris Gonnerman]

----- Original Message -----
From: "Peter Hansen" <peter at engcorp.com>


> Chris Gonnerman wrote:
> >
> > Unfortunately what Bryan is asking is not what you are answering.  He
wants
> > to access the I/O port 0x280, which he states is assigned to a "custom
ISA
> > card" which (I assume) is not using the standard parallel port
interface,
> > nor serial, etc. and for which he evidently has no driver.
>
> I admit I didn't actually look at the winioport stuff proposed in the
> "parallel port?!?" thread, but given that it was called winioport
> and not winparallelport, I assumed it was a way of providing generic
> access to IO ports under Windows.  If I was wrong, then you are right
> to correct me!  (Do you know winioport would not work or were you just
> tricked by the name of the thread?)

Whups.  Evidently the low-level package in use by winioport DOES support
generic
access.  My mistake... I was going by the commentary on the main winioport
page,
where he says "I am now able do printer port IO."  I assumed that was the
entire
scope of the package, but evidently not.

> Of course, it's probably moot given Jon Nicoll's response which suggests
> a perfectly viable alternative.

Indeed... to wit:

----- Original Message -----
From: "Jon Nicoll" <jkn at nicorp.f9.co.uk>

> This is exactly what my code can be used for - you can set it up to
> get access to arbitary IO ports (via the ioperm mechanism in Linux),
> and then read or write etc. as you like. Admittedly, it doesn't
> currently cater for interrupts.

Which could be vitally significant or totally unimportant.

> I originally started writing this to drive an ISA 8255/8253 card, and
> although this project-ette is currently in limbo, the basics are all
> there and working, if Bryan wants to do eg. polled access to an A/D
> card etc.
>
> You don't need a VxD (for W95 at least), although it's probably the
> 'better' way of doing things. My code is in C and turns into a little
> '.PYD' (= .DLL) file. In NT, you need a kernel mode driver, which I
> haven't yet got around to looking at.

Here the winioport module (and the underlying DriverLYNX package) might
be better for Bryan.

> I've just resurrected my code and am looking at using distutils to get
> it in a form more easily distributed. Email me if would be of use to
> you in the meantime.

Bryan hasn't responded since he initially requested this information...
are you out there, Bryan?