Device Code

I am wondering how I match up a PCI Base Class code with a INF file
class.
I have a device that has an Base Class 07 and Subclass 80, a Simple
Communications Controller, other communications device. I wrote a
driver that works with it, but I get a new device detected message every
time Windows boots up. What entry do I need in my INF file to tell
Windows this is the driver for that device? I am using Windows 2000.

Thanks,
Clint

Don
Tue Oct 21 15:02:53 CDT 2003

You do not match on Class Codes, only Vendor ID/Device ID and potentially
Subsystem ID/Subsystem Vendor ID. Class codes are not used since the PCI
specs do not define what a class looks like, if you match all simple
communications controllers you would find your driver needing to support a
bewildering set of devices.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

"Clint Stott" <cs@cs.cs> wrote in message news:3F958CFF.87DC2ECE@cs.cs...
> I am wondering how I match up a PCI Base Class code with a INF file
> class.
> I have a device that has an Base Class 07 and Subclass 80, a Simple
> Communications Controller, other communications device. I wrote a
> driver that works with it, but I get a new device detected message every
> time Windows boots up. What entry do I need in my INF file to tell
> Windows this is the driver for that device? I am using Windows 2000.
>
> Thanks,
> Clint
>

Clint
Tue Oct 21 19:36:55 CDT 2003

Ok, how do I put the Vendor ID/Device ID and potentially Subsystem
ID/Subsystem Vendor ID in the INF file? The driver itself matches the
Vendor ID and Device ID and works fine. It's a matter of telling
windows to look at that driver when looking to satisfy the device at bootup.



Don Burn wrote:
> You do not match on Class Codes, only Vendor ID/Device ID and potentially
> Subsystem ID/Subsystem Vendor ID. Class codes are not used since the PCI
> specs do not define what a class looks like, if you match all simple
> communications controllers you would find your driver needing to support a
> bewildering set of devices.
>
>

Don
Wed Oct 22 06:01:08 CDT 2003

Look at any of the INF files in the DDK, this is very basic. Or use
the GenInf tool in the DDK, it will prompt you for data and create
the INF for you.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting

"Clint" <cs@cs.cs> wrote in message news:3F95D127.1010004@cs.cs...
> Ok, how do I put the Vendor ID/Device ID and potentially Subsystem
> ID/Subsystem Vendor ID in the INF file? The driver itself matches the
> Vendor ID and Device ID and works fine. It's a matter of telling
> windows to look at that driver when looking to satisfy the device at
bootup.
>
>
>
> Don Burn wrote:
> > You do not match on Class Codes, only Vendor ID/Device ID and
potentially
> > Subsystem ID/Subsystem Vendor ID. Class codes are not used since the
PCI
> > specs do not define what a class looks like, if you match all simple
> > communications controllers you would find your driver needing to support
a
> > bewildering set of devices.
> >
> >
>

Clint
Fri Oct 31 10:35:50 CST 2003

Thanks Don.
I got all of the informatin in the INF file, and finaly figured out Windows made
a copy of it during install so it was using the old copy even after installing
the new copy. Once I got rid of the old copys, it started working.
Thanks for your assistance.
Clint


Don Burn wrote:

> Look at any of the INF files in the DDK, this is very basic. Or use
> the GenInf tool in the DDK, it will prompt you for data and create
> the INF for you.
>
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>
> "Clint" <cs@cs.cs> wrote in message news:3F95D127.1010004@cs.cs...
> > Ok, how do I put the Vendor ID/Device ID and potentially Subsystem
> > ID/Subsystem Vendor ID in the INF file? The driver itself matches the
> > Vendor ID and Device ID and works fine. It's a matter of telling
> > windows to look at that driver when looking to satisfy the device at
> bootup.
> >
> >
> >
> > Don Burn wrote:
> > > You do not match on Class Codes, only Vendor ID/Device ID and
> potentially
> > > Subsystem ID/Subsystem Vendor ID. Class codes are not used since the
> PCI
> > > specs do not define what a class looks like, if you match all simple
> > > communications controllers you would find your driver needing to support
> a
> > > bewildering set of devices.
> > >
> > >
> >