Miguel,
Primarily the NT4 version of the driver installed on 2000 is a stop-gap, to
simply provide a driver for the hardware until the 2000 driver has been
completed. This driver does work, and works within specs, on other 2000
platforms, it is not working on the Compact PCI with a PMC bus mastering
card on a Compact PCI carrier. My gut feeling is that you are right – a
PnP driver that properly dances with the PnP manager will most likely be
alright. But it sure would be nice to feel warm and fuzzy that this is
indeed the case before I go committing such to the customer.
The question, restated, is “Are there any known problems using bus
mastering, PMC boards in CPCI carriers on CPCI systems running Windows 2000,
SP1?”.
Gary
-----Original Message-----
From: Miguel Monteiro
[mailto:xxxxx@criticalsoftware.com]
Sent: Tuesday, January 23, 2001 3:27 AM
To: NT Developers Interest List
Subject: [ntdev] Re: [NTDEV] Legacy drivers, 2000,
and a Compact PCI
Is this something that will go away once I have a PnP
compliant suite of
>drivers in place?
I might be guessing, but you may have to make your driver
PnP compliant:
you probably will have to implement (if you haven’t yet)
routines for
AddDevice/DispatchPnp/DispatchPower in order to get it to
work under
Win2K.
Please note I’m not sure about this (I’m novice to driver
development),
but I’ve been having some NT/Win2K compatibility problems
that make
me “suspect” of such thing. Hope this could be useful… 
Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com
?Humour and love are God’s answers
to Human weaknesses?
----- Original Message -----
>From: “Gary Little”
>To: “NT Developers Interest List”
>Sent: Tuesday, January 23, 2001 12:53 AM
>Subject: [ntdev] [NTDEV] Legacy drivers, 2000, and a
Compact PCI
>
>The hardware is Compact PCI. The system has a 5360
controller board and
>several IO boards. Our fibre channel PMC board is installed
in Compact PCI
>carrier, and our drivers loaded in the operating system …
NT4 or Windows
>2000.
>
>Under NT4 there is no problem. Our drivers initialize our
FC card, based on
>the Isp2200, the application acquires a handle, and data
transfers can be
>performed.
>
>Under 2000, here is what I know. I have established an
install INF that
>installs the latest NT4 version of the driver on 2K. This
works on other
>hardware platforms. The driver will load and then use
HalGet/SetBusData to
>fetch and store PCI data and finally uses
HalAssignSlotResources to finalize
>the resources that is provided by the PCI bus. DriverEntry
has log writing
>and assert message at key points that tell me that the IRQ
is hooked, an
>interrupt object is generated, and proper port IO addresses
are acquired.
>However, when IO is done using the base address supplied by
HASR, things do
>not work. For instance, a simple request to get the world
wide name for the
>card returns FFFFFFFF FFFFFFFF. So, IO does not appear to
be working, which
>means that nothing will ever happen to trigger an
interrupt.
>
>I feel certain that all of this will be resolved with the
completion of the
>2000 version of the driver, but right now I am trying to
get the customer
>working, so I can complete the 2000 driver.
>
>Has anyone used a PMC card on a Compact PCI carrier, in
Windows 2000? If so
>did you have problems? What were they and how did you
resolve them?
>
>Is this something that will go away once I have a PnP
compliant suite of
>drivers in place?
—
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com