Prev: vista checked HAL/NT files download ?
Next: winddi.h
From: chris.aseltine on 8 May 2008 13:58
On May 8, 12:10 pm, Brianhub <Brian...(a)discussions.microsoft.com>
wrote:

> The drivers are for a USB communication adapter for an industrial
> network. Because it is a custom driver class it canÂ’t be tested
> by MicrosoftÂ’ hardware lab.

Not true at all, there is an "Unclassified" suite in DTM that will
allow you to get a WHQL signature for a custom device class.

> systems). Also, the setupapi.log file gives many warnings indicating that the
> driver isnÂ’t signed when all files and the catalog file are correctly signed.
> Is this a bug that will be fixed or is the fact that the file is signed not
> detected for some reason?

XP x86 doesn't care about Authenticode signatures at all. For built-
in device classes it will behave as if your driver is totally
unsigned. For custom device classes, I think you might skip a warning
box or two, but you will still see such errors in setupapi.log.
From: Brianhub on 8 May 2008 15:37
Chris,

Thanks for the quick response. I didn't realize the custom driver could get
a WHQL signature. We may look into that.

Is there any way to prevent the searching of removeable media like the DVD
for INF files when the system is trying to determine the best driver?
--
Brian


"chris.aseltine(a)gmail.com" wrote:

> On May 8, 12:10 pm, Brianhub <Brian...(a)discussions.microsoft.com>
> wrote:
>
> > The drivers are for a USB communication adapter for an industrial
> > network. Because it is a custom driver class it can't be tested
> > by Microsoft' hardware lab.
>
> Not true at all, there is an "Unclassified" suite in DTM that will
> allow you to get a WHQL signature for a custom device class.
>
> > systems). Also, the setupapi.log file gives many warnings indicating that the
> > driver isn't signed when all files and the catalog file are correctly signed.
> > Is this a bug that will be fixed or is the fact that the file is signed not
> > detected for some reason?
>
> XP x86 doesn't care about Authenticode signatures at all. For built-
> in device classes it will behave as if your driver is totally
> unsigned. For custom device classes, I think you might skip a warning
> box or two, but you will still see such errors in setupapi.log.
>
From: mirage2k2 on 8 May 2008 21:59
my experience with driver install is that windows likes to look everywhere
else first before looking at the infs you provide (I'm assuming that you have
inf for your driver and that it is part of your install package).

Windows usually first looks in infcache file, in windows\inf, and sometimes
entries in this file can lead to your driver not being installed correctly.
When I come across a certain system that has trouble installing my driver,
the first thing I do is delete the infcache (usually named INFCACHE.1). This
normally fixes my problem! On one system I tried everything and my driver
would not install, finally I ran a registry fixup/cleanup tool and this fixed
it - this may also be the answer for the system you mention that always looks
on DVD.

Another common problem you may encounter is when a system contains older
versions of your inf file. In this case windows usually installs your driver
using the existing older versions instead of the current one provided in your
install package.

mirage

"Brianhub" wrote:

> Chris,
>
> Thanks for the quick response. I didn't realize the custom driver could get
> a WHQL signature. We may look into that.
>
> Is there any way to prevent the searching of removeable media like the DVD
> for INF files when the system is trying to determine the best driver?
> --
> Brian
>
>
> "chris.aseltine(a)gmail.com" wrote:
>
> > On May 8, 12:10 pm, Brianhub <Brian...(a)discussions.microsoft.com>
> > wrote:
> >
> > > The drivers are for a USB communication adapter for an industrial
> > > network. Because it is a custom driver class it can't be tested
> > > by Microsoft' hardware lab.
> >
> > Not true at all, there is an "Unclassified" suite in DTM that will
> > allow you to get a WHQL signature for a custom device class.
> >
> > > systems). Also, the setupapi.log file gives many warnings indicating that the
> > > driver isn't signed when all files and the catalog file are correctly signed.
> > > Is this a bug that will be fixed or is the fact that the file is signed not
> > > detected for some reason?
> >
> > XP x86 doesn't care about Authenticode signatures at all. For built-
> > in device classes it will behave as if your driver is totally
> > unsigned. For custom device classes, I think you might skip a warning
> > box or two, but you will still see such errors in setupapi.log.
> >
 | 
Pages: 1
Prev: vista checked HAL/NT files download ?
Next: winddi.h