I agree, but my experience is like yours -- I haven't seen this problem in *years*
The issue used to be related to poor/inaccurate detection of hardware, particularly 3rd tier providers, and laptop chipsets. -ASB: http://XeeSM.com/AndrewBaker On Mon, May 17, 2010 at 5:48 PM, Ben Scott <mailvor...@gmail.com> wrote: > On Mon, May 17, 2010 at 5:35 PM, Andrew S. Baker <asbz...@gmail.com> > wrote: > > Also, the drivers that are available are written by the vendors in > question, > > not Microsoft. They are simply provided at Microsoft Update for > convenience > > to all concerned. > > That doesn't alleviate Microsoft of responsibility. Under the > warranty laws in most US states, a middle-man still retains liability > for products/services they provide. They cannot simply throw up their > hands and say, "I was just passing it along". Especially since > Microsoft ships many of these drivers "in the box" with Windows. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
