(First Question in the bottom)... Hope yopu can help me!

Hi!!!

I checked and it seems ok. So I will tell you what
happens in my debugging: I created a simple driver(withot
any I/O, memory or IRQ), which I can install to a non-
existent hardware. The run goes like:

PCIETH - Version 1.00.000 Dec 8 2003 15:17:25
PCIETH - Entering AddDevice: DriverObject 85DEDA70, pdo
857EA690
PCIETH - PNP Request (IRP_MN_FILTER_RESOURCE_REQUIREMENTS)
PCIETH - PNP Request (IRP_MN_START_DEVICE)
PCIETH - To WORKING from STOPPED
PCIETH - PNP Request (IRP_MN_QUERY_CAPABILITIES)
PCIETH - PNP Request (IRP_MN_QUERY_PNP_DEVICE_STATE)
PCIETH - PNP Request (IRP_MN_QUERY_DEVICE_RELATIONS)

And the it's ok, I can communicate with this driver, but
when I install the same one to my chip it stops after the
PNP minor function resource requirements (supposedly
managed by the PCI bus):

PCIETH - Version 1.00.000 Dec 8 2003 15:17:25
PCIETH - Entering AddDevice: DriverObject 85DEDA70, pdo
857EA690
PCIETH - PNP Request (IRP_MN_FILTER_RESOURCE_REQUIREMENTS)
PCIETH - PNP Request (IRP_MN_QUERY_STOP_DEVICE)
PCIETH - PNP Request (IRP_MN_QUERY_STOP_DEVICE)
PCIETH - PNP Request (IRP_MN_CANCEL_STOP_DEVICE)

So obviosly as you say it will never work...

So I re-start the computer as asked by windows and the it
marks this resource overlaping in the I/O area with an
intel pentium ii xeon processor to agp controller, but the
device manager gives me this info:

Intel I/O area: 03B0-03BB and 03CO-03DF
My chip: F000-FFFF

Now, do you now how can I fix this?

Thanx

"Rober Zimbra" <rozigs00@fht-esslingen.de> wrote in message news:fda101c3be31$bb6c2e90$a601280a@phx.gbl...
Assuming this is actual resource requirements of your device -
a standard PC system most probably does not have I/O window this big, due to so called "aliases".
On NT5, device manager doesn't show the aliases but win9x does.
Try to restrict your i/o window to 32.. 48 bytes or use memory based i/o.

- PA