The NT4 DDK has an example for a Control Panel applet for configuring a PnP
serial port. It’s under src\setup\pnp\PNPPORTS. We used that as a base for
our configuration applet. The issue that I had deal with was that using
SetupDixx calls you could change the configuration of the PnP card but the
resource setting values would be written automatically to a special location
in the registry for the ISAPnP driver to read and configure our device with
at boot time. Our driver for the device still needed to know the the
resources settings (true Pnp was not there yet) so the applet would also
write those values to the registry key for the driver, to be read when the
driver loaded.
Jim
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Joe McCloskey
Sent: Tuesday, July 10, 2001 8:50 AM
To: NT Developers Interest List
Subject: [ntdev] RE: pci device support on nt4 (sp6)
Hi Jim,
Did you explore how to do the configurations? I am currently trying to
force
configuration on a legacy device and I have had no luck at this point.
Running
bounds checker on the source code, I found that no CM_ functions are being
called
by the device manager. Were you writing configurations directly to the
registry?
Joe McCloskey
Gamry Instruments, Inc.
xxxxx@gamry.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jim Young
Sent: Monday, July 09, 2001 9:00 PM
To: NT Developers Interest List
Subject: [ntdev] RE: pci device support on nt4 (sp6)
I successfully wrote a ISAPNP driver for NT4, but it was not a task that I
would want to perform again. To get around the problem that NT4 did not
natively support ISAPNP we had our customers install an ISAPNP driver that
MS provided to support the ISAPNP Sound Blaster cards. After that was
installed then our card, a high speed serial port, would install in somewhat
the same fashion as it would with Win9x. One of the big problems we had was
that NT4 did not have the equivalent of Device Manager. I had to write a
custom Control Panel DLL that allowed the customer to change the resources
and device name of the port - I had to emulate the functionality of Device
Manager for our device. This involved digging into some rather unexplored
areas of the origins of the SetupDixxx calls for NT.
Jim
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Gary Little
Sent: Monday, July 09, 2001 10:05 AM
To: NT Developers Interest List
Subject: [ntdev] RE: pci device support on nt4 (sp6)
Under NT 4 forget ISAPNP. NT 4 does not support PnP natively. For multiple
devices on the PCI bus you call HalGetBusData until you have found all of
your devices. You also call HalAssignSlotResources for each device you find.
I would suggest you get INF-Tools to build your INF files. It makes life in
the wonderful world of drivers much easier. Costs $40 and is faster,
cheaper, and has less bulk than InstallShield.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: Ta H. [mailto:xxxxx@hotmail.com]
Sent: Saturday, July 07, 2001 10:27 PM
To: NT Developers Interest List
Subject: [ntdev] pci device support on nt4 (sp6)
1). How NT4 supports multiple PCI instances? Anything the driver needs to
do so that can be done? I was told there’s ISAPNP for the limited PnP
support. Is it helpful for my case? I know for WDM drivers, you can put
PCI\VEN_XXXX&DEV_YYYY in their inf. Is it supported in NT4?
2). Now I manually edit the registry to install the driver. I’d appreciate
if someone can show me a sample oemsetup.inf for a PCI device. My device is
a multimedia device (not audio though).
Thanks
Get your FREE download of MSN Explorer at http://explorer.msn.com
You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@youngendeavors.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@gamry.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@youngendeavors.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