Re: Can anything in W2K use a port range, which already used by (assigned to) kernel-mode drive

NTDEV
1

> I see, but you recommendation is wrong. My driver does not use a COMx

ports, it uses the processor IO ports range 0x120-0x127. The system
reports that there is no conflict on that ports. But the device gets
the
illegal input/output, and as it seems to me not via my driver.

Citation:
>you now
> need to do things the right way — attach to the PDO/FDO stack and
filter
> the IO of the port your now trying to control directly

Yes I have developed the new style pseudo-PnP W2k driver. Guess what I
get
… oh…, the same result.

pseudo-Pnp driver? You should be writing an ISA-bus function driver for your device, and your
inf file ought to be specifying IO port 0x120 with a range of 8 bytes. Anything else is
doomed. In your start device routine you will then obtain the IO resources you specified, or
your device will fail to install.

What you cannot do is to bypass the resource allocation mechanism and just decide that IO
port 0x120 is yours for the use as you see fit.

===========================
Mark Roddy
Consultant, Microsoft DDK MVP
Hollis Technology Solutions
xxxxx@hollistech.com
www.hollistech.com
603-321-1032

2

> ===========================

Mark Roddy

pseudo-Pnp driver? You should be writing an ISA-bus function driver for your device, and your inf file ought to be specifying IO port 0x120 with a range of 8 bytes.

Yes, I did just this thing. I got the example from W2K DDK - “portIO”. I
rewrite
“portIO” and “portIO.inf” to fit my requrements.

Anything else is doomed. In your start device routine you will then obtain the IO resources you specified, or your device will fail to install.
What you cannot do is to bypass the resource allocation mechanism and just decide that IO port 0x120 is yours for the use as you see fit.

Yes, The driver obtained the requred resources on it’s start.
Yes, The device manager shows the requested resources, and the device
manager shows no conflict.

The driver mostly works, but when I press keyboard button “Enter”, in any
window applications (just anywhere) the device get the illegal
input/output.