(Thanks to all who have responded. Folks, sorry if this thread is consuming too much of your bandwidth. I never intended this to be quite so long. I think I have my answer: things in the DDK relative to ISA PnP on WinNT 4 haven’t changed, and nobody has an alternative tool like DriverWorks to recommend. With that said, I’ll respond to anyone who asks for further info, but not originate any more on the subject.)
They are listed, the issue seems to be “activating” the card. It seems that NT finds the card allocates the resources, puts that in the registry but doesn’t actually do the last step of “activating” the card (the term used in the ISA PnP spec.)
It appears that the driver is responsible for informing the OS of the usage of the resources and then activating the card assuming it gets them (it succeeds in allocating them). We have some home grown (and ugly) activation code buried in the existing driver. Alternatively we have it buried somewhere in the DriverWorks version of the driver which is unfinished and I inherited.
The situation, (without being long winded), is that I need to enhance a driver written several years ago for improved functionality on already deployed (years ago) Win NT 4 systems.
The question I was originally trying to answer was:
- Are there any alternatives to the old DDK? (in other words, are things in the new DDK the same? It appears they are.)
- Or is there some other toolchain, etc. anyone would recommend for what I’m tackling?
I’m basically lazy (did I say that?) I mean I’d rather use somebody’s proven and debugged activation code as opposed to inventing my own for this project. The issue with DriverWorks as I understand it from the guy who was working on this is that the DriverWorks code base needs to be significantly patched (he worked with the DriverWorks people on this) to make it work. This gives me the queasies, I’m looking for something cleaner that a patched set of code that may or may not be supported, etc.
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Monday, January 27, 2003 10:41 AM
To: NT Developers Interest List
Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega DriverWorks o r
Jungo WinDriver?)
BTW - am I wrong that, with proper BIOS setup, ISAPnP resources will
be listed in HKLM\HARDWARE even on NT4, and thus will be available via
IoQueryDeviceDescription?
Max
----- Original Message -----
From: “Christiaan Ghijselinck”
To: “NT Developers Interest List”
Sent: Saturday, January 25, 2003 1:37 AM
Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega DriverWorks o r
Jungo WinDriver?)
>
> Well John, this is exactly the same what NT40 does with the “well
know”
> devices such as parallel port, serial ports at startup and without
help of
> the
> “pnpisa.sys”. Nothing has been changed all the time. The
“serial.sys” from
> the DDK ( and the official version ) for example is a pure legacy
driver
> that
> enumerates the resources that were found during startup. I cannot
think
> about
> the fact that DriverWorks builds on top of the requirement that
resources
> are
> provided in the HARDWARE hive within the HKLM registry.
>
> Nothing has been added last years to support PnP on NT40, not even
in the
> DDK.
>
>
> ----- Original Message -----
> From: “Miramonti, John”
> To: “NT Developers Interest List”
> Sent: Friday, January 24, 2003 10:59 PM
> Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega DriverWorks o
r Jungo
> WinDriver?)
>
>
> > I’m quite familiar with pnpisa.inf , etc.
> >
> > It’s not generally known, but that thing will come up and
configure the
> resources. It even fills out the registry. Your driver then comes
up and
> looks in the registtry for it’s card and makes calls to allocate the
> resources. Some of this is documented, some isn’t, some you can
figure out
> by reading the sound blaster sources, etc. This is what DriverWorks
builds
> on top of and what our homegrown driver did too. This has all been
there
> since day 1 of NT4. I haven’t looked at this for a couple years and
I was
> just wondering if things had improved/gotten documented.
> >
> > John
> >
> > -----Original Message-----
> > From: Moreira, Alberto [mailto:xxxxx@compuware.com]
> > Sent: Friday, January 24, 2003 3:44 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega DriverWorks
o r
> > Jungo WinDriver?)
> >
> >
> > Do a Google Search on “NT4 PnP”. You’ll be surprised. There’s a
file in
> the
> > NT4 CD, at \DRVLIB\PNPISA\X86\PNPISA.INF, right click, click
“install”,
> > reboot, enjoy. It has to do with sound cards.
> >
> > Alberto.
> >
> >
> > -----Original Message-----
> > From: Christiaan Ghijselinck [mailto:xxxxx@CompaqNet.be]
> > Sent: Friday, January 24, 2003 3:25 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega DriverWorks
or
> > Jungo WinDriver?)
> >
> >
> >
> > Let’s summarize :
> >
> > - there is NO newer NT40 DDK
> > - there is NO support for PnP ISA or WDM on NT40 ( unless you
“read” the
> > PnPPorts sample which is just a CPL applet )
> > Just give me the name of a “DriverWorks” sample for NT40 that
supports
> PnP
> > .
> > - Oney’s wizard supports at least theWDM
> >
> >
> > ----- Original Message -----
> > From: “Miramonti, John”
> > To: “NT Developers Interest List”
> > Sent: Friday, January 24, 2003 8:50 PM
> > Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega DriverWorks
or
> Jungo
> > WinDriver?)
> >
> >
> > > Lot’s here…hmmm. Again, we’re not concerned with W2K/XP, I
know we
> can
> > do it there.
> > >
> > > - Is WDM supported with the newer DDK on WinNT 4?
> > > - does it support PnP ISA?
> > >
> > > - Does Oney’s wizard support PnP ISA on WinNT 4? (Where do I get
it to
> > see?)
> > > - DriverWorks advertises that they do, and they sort of do, but
pieces
> are
> > broken, hence the patches we put in (with the DriverWorks people’s
help).
> > >
> > > - Since no one else has responded, my guess is that nothing has
changed,
> > and it’s the same choice, (in other words I’ll continue with the
patched
> > DriverWorks or the cobbled PnP code I’ve already got).
> > >
> > > - I am interested in building drivers inside the 'Studio, but
I’ll
> tackle
> > that after I answer this question. Thanks.
> > >
> > > John
> > >
> > >
> > > -----Original Message-----
> > > From: Christiaan Ghijselinck [mailto:xxxxx@Compaqnet.be]
> > > Sent: Friday, January 24, 2003 2:44 PM
> > > To: NT Developers Interest List
> > > Subject: [ntdev] Re: How do I do ISA PnP? (NOT! Numega
DriverWorks or
> > > Jungo WinDriver?)
> > >
> > >
> > >
> > > NT40 does not support PnP in the sense it is used today on W2K
and XP.
> > > Drivers that supported devices that were automatically detected
on
> > > NT40, are still legacy drivers ( serial , mouse , ). These kind
of
> > > drivers must be WDM compliant on XP/W2K. Although legacy drivers
are
> > > still supported for non PnP, Microsoft does recommend to use the
WDM.
> > >
> > > Most people here recommend the use of the DDK only, perhaps with
a
> little
> > > help from a wizard ( Walter Oney provides one ) and/or batch
files that
> > > wrap build.exe of the DDK’s ( see resources - download at the
OSR web
> site
> > > ) that allows comfortable programming in i.e. Visual Studio
6/NET. Third
> > > party librairies are always wrappers of existing, documented
driver
> > > functions. They will speed up coding, but slow down the overall
> > > development
> > > time when problems occur ( support requests , work arounds, and
probably
> a
> > > fall back to the native DDK functions… )
> > >
> > > You may E-mail me personally, if you would try out my own way of
> building
> > > drivers within Visual Studio environments.
> > >
> > > —
> > > You are currently subscribed to ntdev as:
xxxxx@livco.com
> > > To unsubscribe send a blank email to
xxxxx@lists.osr.com
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
xxxxx@compaqnet.be
> > > To unsubscribe send a blank email to
xxxxx@lists.osr.com
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
xxxxx@compuware.com
> > To unsubscribe send a blank email to
xxxxx@lists.osr.com
> >
> >
> >
> > The contents of this e-mail are intended for the named addressee
only. It
> > contains information that may be confidential. Unless you are the
named
> > addressee or an authorized designee, you may not copy or use it,
or
> disclose
> > it to anyone else. If you received it in error please notify us
> immediately
> > and then destroy it.
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@livco.com
> > To unsubscribe send a blank email to
xxxxx@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as:
xxxxx@compaqnet.be
> > To unsubscribe send a blank email to
xxxxx@lists.osr.com
> >
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
—
You are currently subscribed to ntdev as: xxxxx@livco.com
To unsubscribe send a blank email to xxxxx@lists.osr.com