Hi there,


I work for a graphics card manufacturer and we'd really
like to use Windows Update to distribute driver upgrades.

However, our driver ships with a co-installer dll that
does certain vital bits of PnP arcana that are necessary
on Win2K.

According to the document at
http://www.microsoft.com/whdc/hwdev/driver/WinUp.mspx,
"Drivers must install core functionality from the INF
file. (snip). There can be no setup utilities for files
that provide core device functionality."

Does this mean we're not allowed to have a co-installer?


Many thanks,



Reuben Harris

Re: Windows Update Driver Publishing - really no coinstaller allowed? by Alexander

Alexander
Tue Nov 18 08:58:13 CST 2003

See, for example, BeWAN DSL driver on WinUpdate. It includes a lot of crap,
such as Setup.exe, etc, and unsigned drivers, too!

"Reuben Harris" <anonymous@discussions.microsoft.com> wrote in message
news:0acc01c3adbd$42047b40$a301280a@phx.gbl...
> Hi there,
>
>
> I work for a graphics card manufacturer and we'd really
> like to use Windows Update to distribute driver upgrades.
>
> However, our driver ships with a co-installer dll that
> does certain vital bits of PnP arcana that are necessary
> on Win2K.
>
> According to the document at
> http://www.microsoft.com/whdc/hwdev/driver/WinUp.mspx,
> "Drivers must install core functionality from the INF
> file. (snip). There can be no setup utilities for files
> that provide core device functionality."
>
> Does this mean we're not allowed to have a co-installer?
>
>
> Many thanks,
>
>
>
> Reuben Harris



Re: Windows Update Driver Publishing - really no coinstaller allowed? by Eliyas

Eliyas
Tue Nov 18 10:36:50 CST 2003

> Does this mean we're not allowed to have a co-installer?

No, coinstallers are referenced in the INF files and they are considered a
part of the driver package. Only install applications are forbidden.

--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx



Re: Windows Update Driver Publishing - really no coinstaller allowed? by Maxim

Maxim
Tue Nov 18 10:44:18 CST 2003

Is it a driver for some El Cheapo USB DSL modem which does the signal
processing on host? or a PPPoE stack?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


"Alexander Grigoriev" <alegr@earthlink.net> wrote in message
news:uKdslRerDHA.2676@TK2MSFTNGP11.phx.gbl...
> See, for example, BeWAN DSL driver on WinUpdate. It includes a lot of crap,
> such as Setup.exe, etc, and unsigned drivers, too!
>
> "Reuben Harris" <anonymous@discussions.microsoft.com> wrote in message
> news:0acc01c3adbd$42047b40$a301280a@phx.gbl...
> > Hi there,
> >
> >
> > I work for a graphics card manufacturer and we'd really
> > like to use Windows Update to distribute driver upgrades.
> >
> > However, our driver ships with a co-installer dll that
> > does certain vital bits of PnP arcana that are necessary
> > on Win2K.
> >
> > According to the document at
> > http://www.microsoft.com/whdc/hwdev/driver/WinUp.mspx,
> > "Drivers must install core functionality from the INF
> > file. (snip). There can be no setup utilities for files
> > that provide core device functionality."
> >
> > Does this mean we're not allowed to have a co-installer?
> >
> >
> > Many thanks,
> >
> >
> >
> > Reuben Harris
>
>