Re: InstallHinfSection



Hello, Thanks for the responses. Sounds like I am being severely
chastised - maybe I am asking the wrong question.

The ShellExec... is probably no longer needed. That was a suggestion
for preloading the USB drivers so XP would immediately see them.
Preloading did not help much.

The bottom line is that when our USB hardware is plugged in, the
Windows "Found New Hardware" dialog pops open. I need the easiest,
simplest path to get our drivers loaded once this dialog pops up.

WHQL is out because the drivers do something that will not pass in
Win98. Since we are XP only, it's not a problem. But according to the
manufacturer, prevents WHQL.

Is there a way to tell Windows during our app installation "When you
see this Vid and Pid just go here and don't bother my customer".

Thanks again,
Barry.

.



Relevant Pages

  • Re: NDIS IM driver signing
    ... I've heard of WHQL and Verisign. ... For large lab, DTM is fine, and not only for Windows drivers - its advantages ... you install the new version from Windows Update and - voila! ...
    (microsoft.public.development.device.drivers)
  • Re: InstallHinfSection
    ... WHQL differ for W2K/XP and 9x, so your OEM can path only first ... > The bottom line is that when our USB hardware is plugged in, ... > Windows "Found New Hardware" dialog pops open. ... > simplest path to get our drivers loaded once this dialog pops up. ...
    (microsoft.public.development.device.drivers)
  • Re: ATI driver install
    ... Windows Hardware Quality ... >Labs) Drivers. ... > saying that the driver is not WHQL approved just ignore ... For example the ATI install. ...
    (microsoft.public.windowsxp.hardware)
  • Re: IRQ Conflict
    ... Thank you Richard for your advice, according to nVidia the software is WHQL ... drivers i should try and that have been WHQL certified? ... > NVIDIA cards do NOT need a separate IRQ in Windows XP. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: InstallHinfSection
    ... > for preloading the USB drivers so XP would immediately see them. ... > Windows "Found New Hardware" dialog pops open. ... > simplest path to get our drivers loaded once this dialog pops up. ... > manufacturer, prevents WHQL. ...
    (microsoft.public.development.device.drivers)