Vendor and Product info from a PCI device

Hi -

I am trying to get vendor and product information from installed pci devices
on Win9x up to WinXP.

I am successful using the SetupAPI functions on XP and 2000, however, I am
kind of stumped on how to go about doing this for Win9x. My first thoughts
where to find some type of IOCTL_ command using DeviceIoControl, but not
sure which IOCTL_ command or which device paramater handle to pass in to
DeviceIoControl..

Can anyone point me in the right direction?

Any help is appreciated.
Thanks,
Bert

Ray
Fri Oct 17 13:37:10 CDT 2003

I believe that SetupAPI started being supported in Win98SE on the 9x
side. If you need 98/95 support, SetupX is probably your best bet, as it
contains more or less parallel functionality and exists through ME. It's
pretty undocumented, though...

Bert Grantges wrote:

> Hi -
>
> I am trying to get vendor and product information from installed pci devices
> on Win9x up to WinXP.
>
> I am successful using the SetupAPI functions on XP and 2000, however, I am
> kind of stumped on how to go about doing this for Win9x. My first thoughts
> where to find some type of IOCTL_ command using DeviceIoControl, but not
> sure which IOCTL_ command or which device paramater handle to pass in to
> DeviceIoControl..
>
> Can anyone point me in the right direction?
>
> Any help is appreciated.
> Thanks,
> Bert
>
>

--
../ray\..

Bert
Mon Oct 20 12:09:25 CDT 2003

A little confused on what you wrote regarding SetupX. Are you referring to
the SetupAPI again? or is it something different?

- Thanks for the help -
Bert


"Ray Trent" <rat@synaptics.com.spamblock> wrote in message
news:eSqJu2NlDHA.2776@tk2msftngp13.phx.gbl...
> I believe that SetupAPI started being supported in Win98SE on the 9x
> side. If you need 98/95 support, SetupX is probably your best bet, as it
> contains more or less parallel functionality and exists through ME. It's
> pretty undocumented, though...
>
> Bert Grantges wrote:
>
> > Hi -
> >
> > I am trying to get vendor and product information from installed pci
devices
> > on Win9x up to WinXP.
> >
> > I am successful using the SetupAPI functions on XP and 2000, however, I
am
> > kind of stumped on how to go about doing this for Win9x. My first
thoughts
> > where to find some type of IOCTL_ command using DeviceIoControl, but not
> > sure which IOCTL_ command or which device paramater handle to pass in to
> > DeviceIoControl..
> >
> > Can anyone point me in the right direction?
> >
> > Any help is appreciated.
> > Thanks,
> > Bert
> >
> >
>
> --
> ../ray\..
>

Ray
Tue Oct 21 12:59:03 CDT 2003

No, there's a separate 16-bit DLL that was in 95 (and all other 9x
flavors that I know of). It's called SetupX.dll, and it's a bit of a
mess to use. Don't know of another alternative for 95, though...

Bert Grantges wrote:

> A little confused on what you wrote regarding SetupX. Are you referring to
> the SetupAPI again? or is it something different?
>
> - Thanks for the help -
> Bert
>
>
> "Ray Trent" <rat@synaptics.com.spamblock> wrote in message
> news:eSqJu2NlDHA.2776@tk2msftngp13.phx.gbl...
>
>>I believe that SetupAPI started being supported in Win98SE on the 9x
>>side. If you need 98/95 support, SetupX is probably your best bet, as it
>>contains more or less parallel functionality and exists through ME. It's
>>pretty undocumented, though...
>>
>>Bert Grantges wrote:
>>
>>
>>>Hi -
>>>
>>>I am trying to get vendor and product information from installed pci
>
> devices
>
>>>on Win9x up to WinXP.
>>>
>>>I am successful using the SetupAPI functions on XP and 2000, however, I
>
> am
>
>>>kind of stumped on how to go about doing this for Win9x. My first
>
> thoughts
>
>>>where to find some type of IOCTL_ command using DeviceIoControl, but not
>>>sure which IOCTL_ command or which device paramater handle to pass in to
>>>DeviceIoControl..
>>>
>>>Can anyone point me in the right direction?
>>>
>>>Any help is appreciated.
>>>Thanks,
>>>Bert
>>>
>>>
>>
>>--
>>../ray\..
>>
>
>
>

--
../ray\..

Bert
Tue Oct 21 14:31:49 CDT 2003

Thanks Ray - I will look into that then.. You don't have any resources for
that .dll by chance?



"Ray Trent" <rat@synaptics.com.spamblock> wrote in message
news:uu0RE0$lDHA.1800@TK2MSFTNGP10.phx.gbl...
> No, there's a separate 16-bit DLL that was in 95 (and all other 9x
> flavors that I know of). It's called SetupX.dll, and it's a bit of a
> mess to use. Don't know of another alternative for 95, though...
>
> Bert Grantges wrote:
>
> > A little confused on what you wrote regarding SetupX. Are you referring
to
> > the SetupAPI again? or is it something different?
> >
> > - Thanks for the help -
> > Bert
> >
> >
> > "Ray Trent" <rat@synaptics.com.spamblock> wrote in message
> > news:eSqJu2NlDHA.2776@tk2msftngp13.phx.gbl...
> >
> >>I believe that SetupAPI started being supported in Win98SE on the 9x
> >>side. If you need 98/95 support, SetupX is probably your best bet, as it
> >>contains more or less parallel functionality and exists through ME. It's
> >>pretty undocumented, though...
> >>
> >>Bert Grantges wrote:
> >>
> >>
> >>>Hi -
> >>>
> >>>I am trying to get vendor and product information from installed pci
> >
> > devices
> >
> >>>on Win9x up to WinXP.
> >>>
> >>>I am successful using the SetupAPI functions on XP and 2000, however, I
> >
> > am
> >
> >>>kind of stumped on how to go about doing this for Win9x. My first
> >
> > thoughts
> >
> >>>where to find some type of IOCTL_ command using DeviceIoControl, but
not
> >>>sure which IOCTL_ command or which device paramater handle to pass in
to
> >>>DeviceIoControl..
> >>>
> >>>Can anyone point me in the right direction?
> >>>
> >>>Any help is appreciated.
> >>>Thanks,
> >>>Bert
> >>>
> >>>
> >>
> >>--
> >>../ray\..
> >>
> >
> >
> >
>
> --
> ../ray\..
>

Ray
Tue Oct 21 16:50:39 CDT 2003

Not really, I'm afraid. It's been a long time since I played with SetupX
at all. Back when we wrote our 95 installer (in '95 :-), there was no
documentation at all, so we had to reverse engineer it all by dumping
the exports from SetupX.dll and installing a shim DLL to figure out what
it was doing for our device class.

Since then, I think MS may have documented some of it (though I don't
have the 98DDK installed on my machine, so I can't check). Basically, my
recollection was that it involved enumerating the devices with
DiGetClassDevs, enumerating the compatible drivers with
DiBuildCompatDrvList, selecting that in the LPDI structure, and then
calling DiInstallDevice to install the selected driver onto the device.

Bert Grantges wrote:

> Thanks Ray - I will look into that then.. You don't have any resources for
> that .dll by chance?
>
>
>
> "Ray Trent" <rat@synaptics.com.spamblock> wrote in message
> news:uu0RE0$lDHA.1800@TK2MSFTNGP10.phx.gbl...
>
>>No, there's a separate 16-bit DLL that was in 95 (and all other 9x
>>flavors that I know of). It's called SetupX.dll, and it's a bit of a
>>mess to use. Don't know of another alternative for 95, though...
>>
>>Bert Grantges wrote:
>>
>>
>>>A little confused on what you wrote regarding SetupX. Are you referring
>
> to
>
>>>the SetupAPI again? or is it something different?
>>>
>>> - Thanks for the help -
>>>Bert
>>>
>>>
>>>"Ray Trent" <rat@synaptics.com.spamblock> wrote in message
>>>news:eSqJu2NlDHA.2776@tk2msftngp13.phx.gbl...
>>>
>>>
>>>>I believe that SetupAPI started being supported in Win98SE on the 9x
>>>>side. If you need 98/95 support, SetupX is probably your best bet, as it
>>>>contains more or less parallel functionality and exists through ME. It's
>>>>pretty undocumented, though...
>>>>
>>>>Bert Grantges wrote:
>>>>
>>>>
>>>>
>>>>>Hi -
>>>>>
>>>>>I am trying to get vendor and product information from installed pci
>>>
>>>devices
>>>
>>>
>>>>>on Win9x up to WinXP.
>>>>>
>>>>>I am successful using the SetupAPI functions on XP and 2000, however, I
>>>
>>>am
>>>
>>>
>>>>>kind of stumped on how to go about doing this for Win9x. My first
>>>
>>>thoughts
>>>
>>>
>>>>>where to find some type of IOCTL_ command using DeviceIoControl, but
>
> not
>
>>>>>sure which IOCTL_ command or which device paramater handle to pass in
>
> to
>
>>>>>DeviceIoControl..
>>>>>
>>>>>Can anyone point me in the right direction?
>>>>>
>>>>>Any help is appreciated.
>>>>>Thanks,
>>>>>Bert
>>>>>
>>>>>
>>>>
>>>>--
>>>>../ray\..
>>>>
>>>
>>>
>>>
>>--
>>../ray\..
>>
>
>
>

--
../ray\..

Walter
Tue Oct 21 20:09:56 CDT 2003

Ray Trent wrote:
> Not really, I'm afraid. It's been a long time since I played with SetupX
> at all. Back when we wrote our 95 installer (in '95 :-), there was no
> documentation at all, so we had to reverse engineer it all by dumping
> the exports from SetupX.dll and installing a shim DLL to figure out what
> it was doing for our device class.
>
> Since then, I think MS may have documented some of it (though I don't
> have the 98DDK installed on my machine, so I can't check). Basically, my
> recollection was that it involved enumerating the devices with
> DiGetClassDevs, enumerating the compatible drivers with
> DiBuildCompatDrvList, selecting that in the LPDI structure, and then
> calling DiInstallDevice to install the selected driver onto the device.

You could try looking at the 16-bit version of FASTINST in my book. I
did the same sort of trial and error to figure that out. IIRC, the
16-bit APIs are documented in MSDN. Or else they were sufficiently
similar to the 32-bit APIs that I was able to figure out what to do with
them by trying to imagine how they evolved to their 32-bit counterparts.
Plus I got lucky with some guesses.

Oh, the heck with it. Let's just abandon 98/Me, why don't we?

--
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Check out our schedule at http://www.oneysoft.com

Bert
Mon Oct 27 09:53:28 CST 2003

Would love to abandon it (and in my mind I have) unfortunately my employer
thinks otherwise :)

Bert

"Walter Oney" <waltoney@oneysoft.com> wrote in message
news:3F95D8E4.AD4F856A@oneysoft.com...
> Ray Trent wrote:
> > Not really, I'm afraid. It's been a long time since I played with SetupX
> > at all. Back when we wrote our 95 installer (in '95 :-), there was no
> > documentation at all, so we had to reverse engineer it all by dumping
> > the exports from SetupX.dll and installing a shim DLL to figure out what
> > it was doing for our device class.
> >
> > Since then, I think MS may have documented some of it (though I don't
> > have the 98DDK installed on my machine, so I can't check). Basically, my
> > recollection was that it involved enumerating the devices with
> > DiGetClassDevs, enumerating the compatible drivers with
> > DiBuildCompatDrvList, selecting that in the LPDI structure, and then
> > calling DiInstallDevice to install the selected driver onto the device.
>
> You could try looking at the 16-bit version of FASTINST in my book. I
> did the same sort of trial and error to figure that out. IIRC, the
> 16-bit APIs are documented in MSDN. Or else they were sufficiently
> similar to the 32-bit APIs that I was able to figure out what to do with
> them by trying to imagine how they evolved to their 32-bit counterparts.
> Plus I got lucky with some guesses.
>
> Oh, the heck with it. Let's just abandon 98/Me, why don't we?
>
> --
> Walter Oney, Consulting and Training
> Basic and Advanced Driver Programming Seminars
> Check out our schedule at http://www.oneysoft.com