From: dracipmot on
without (or at least in the interim prior to) re-spinning silicon.

for instance, say ven id - 0001, dev id = 0001, class code = (this is a lie)
ehci compatible
how do i modify registry so ms usb driver wont even start to load

for reasons easy to imagine i cannot wait till driver fails to load and then
disable in device manager

--
Tom Picard
From: Tim Roberts on
dracipmot <dracipmot(a)discussions.microsoft.com> wrote:
>
>without (or at least in the interim prior to) re-spinning silicon.
>
>for instance, say ven id - 0001, dev id = 0001, class code = (this is a lie)
>ehci compatible
>how do i modify registry so ms usb driver wont even start to load
>
>for reasons easy to imagine i cannot wait till driver fails to load and then
>disable in device manager

If you pre-install your INF file, it should be matched first. If you don't
have a driver ready, you can pre-install an INF file with a null driver.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Mike [MSFT] on
What's the scenario? Are you plugging a new device into the system and
trying to prevent PnP from installing the Inbox USB driver? If so then
preloading a better ranked driver is the best option. Which operating
system you are targeting would help as well.

-Mike

"Tim Roberts" <timr(a)probo.com> wrote in message
news:pl5co5hbnqggev5r8hfimduvcigk0t834a(a)4ax.com...
> dracipmot <dracipmot(a)discussions.microsoft.com> wrote:
>>
>>without (or at least in the interim prior to) re-spinning silicon.
>>
>>for instance, say ven id - 0001, dev id = 0001, class code = (this is a
>>lie)
>>ehci compatible
>>how do i modify registry so ms usb driver wont even start to load
>>
>>for reasons easy to imagine i cannot wait till driver fails to load and
>>then
>>disable in device manager
>
> If you pre-install your INF file, it should be matched first. If you
> don't
> have a driver ready, you can pre-install an INF file with a null driver.
> --
> Tim Roberts, timr(a)probo.com
> Providenza & Boekelheide, Inc.

From: dracipmot on
Mike Tim thanks

what do you mean by "preloading a better ranked driver" or "pre-install your
INF file"?
Is that just copying the inf to Windows\Inf directory?
Or maybe using devcon with the inf?

Anyway i managed to accomplish what i needed by
after os crash, remove multifucntion pci card from slot , reboot, change
"Service"="usbehci"
to
"Service"="Null"
at
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_0001&DEV_0001&SUBSYS_00000001&REV_00\6&6d66820&0&000000E0],
plug in card in same slot, restart
the above key must have been written prior to os crash

device manager shows a mismatch of info, but otherwise ok
I can install another driver, as long as I don't let Windows install
automatically (recommended) rather point to exact inf file
on xp, hope it is not much different on 7. . . .

--
Tom

"Mike [MSFT]" wrote:

> What's the scenario? Are you plugging a new device into the system and
> trying to prevent PnP from installing the Inbox USB driver? If so then
> preloading a better ranked driver is the best option. Which operating
> system you are targeting would help as well.
>
> -Mike
>
> "Tim Roberts" <timr(a)probo.com> wrote in message
> news:pl5co5hbnqggev5r8hfimduvcigk0t834a(a)4ax.com...
> > dracipmot <dracipmot(a)discussions.microsoft.com> wrote:
> >>
> >>without (or at least in the interim prior to) re-spinning silicon.
> >>
> >>for instance, say ven id - 0001, dev id = 0001, class code = (this is a
> >>lie)
> >>ehci compatible
> >>how do i modify registry so ms usb driver wont even start to load
> >>
> >>for reasons easy to imagine i cannot wait till driver fails to load and
> >>then
> >>disable in device manager
> >
> > If you pre-install your INF file, it should be matched first. If you
> > don't
> > have a driver ready, you can pre-install an INF file with a null driver.
> > --
> > Tim Roberts, timr(a)probo.com
> > Providenza & Boekelheide, Inc.
>