"Alexander Nagel",
On occasion, an independent hardware manufacturer (IHV) produces a driver that
they wish to place at the Windows Update site. This is done to address issues
they receive from various issue reports that they receive. If that driver is
placed at the Windows Update site, it is given a 4-part version ID such as you
mentioned: "8.24.3.3."
All of this is fine so far, but that new driver may *not* be for your particular
hardware configuration. I'll give you an example:
1. XYZ produces the JANC 10/100 Ethernet Network Interface Card (NIC) that they
sell in various locations.
a. Sold as XYZ JANC, by itself (shrink-wrapped on a shelf), at the largest
computer store chains.
b. Sold as a component of ABC computers, an online computer retailer who
specializes in building PCs and shipping them to customers. ABC is an original
equipment manufacturer (OEM) and they test this card on several of their models
and use it in about 90% of their lower priced computer models.
c. In an agreement with OPQ Motherboards, XYZ incorporates the exact chipset
of the JANC NIC into 5 different Intel 32-bit compatible motherboards that are
sold both at the largest computer store chains and are found in 3 of the large 5
OEMs.
In the above example, XYZ receives bug reports concerning the chipset in 2 of
the 5 OPQ motherboards, but are not receiving consistent errors anywhere else.
To head off the problem, XYZ builds and tests a driver that seems to address the
issue with the 2 OPQ motherboards. To address the problem quickly, they post
the driver with Windows Update and set the priority of this driver to Critical,
so that many of their customers will get it sooner and not experience the issue.
XYZ also posts the new driver on their own website, so customers can get it.
The detection "logic" for this update includes detection for a proper chipset
and for a given version ID on the driver -- and nothing else.
This new driver was not intended for any group other than the OPQ motherboard
customers, but the driver alerts every customer with an XYZ NIC chipset on their
computers that visits the Windows Update website.
For many of these customers, the package has not been tested by their OEM, and
was not offered to them at the OEM website. Despite this, many customers
download this driver and a few find problems with their system. This problem is
remedied by "rolling back" the driver.
I hope this has made your situation a little easier to understand, and please
let me know if I can be of further help.
Sincerely,
Pat Walters [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. Use
of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
"Alexander Nagel" <> wrote in message
news:OSQriY$...
> Hi everybody,
> i have installed the new marvell network (8.24.3.3)driver for my
> onboard-gbitlan on asus k8v se deluxe and since then the network connections
> hangs and i get time outs in the browser after several minutes. The internet
> connection is not set to break the connection after idle time.
> I had to reinstall an older version.
> Does anybody share my experiences?
> Thanks for any comments
> Alex
|
Similar Threads
Linear Mode
