Raf takes on HP's use of ancient device drivers in MediaSmart home server

Rafael Rivera examines HP's use of less-than-recent drivers in its Windows Home Server-based MediaSmart Server:

For some time now, I’ve been having issues in which my HP MediaSmart Server (powered by Windows Home Server) would experience less-than-stellar network throughput and even fail to respond at times. Given the fragile nature of Windows Home Server and value I place on my data, I dared not deviate from the baseline HP configuration. Until now.

Given this was clearly a network-related issue, I checked out the SiS191 network adapter in Device Manager. I was shocked to find HP baselined the server on drivers over a year old. I ran a benchmark using AIDA32 3.92 from my desktop to the server.

According to SiS, the latest driver for SiS191 chipsets is 2.0.1039.1100 dated 03/03/2008. After ignoring all the warnings and legalese on SiS’s website, I down’ed the package, remoted into my server, installed the driver, and rebooted, fingers crossed. The server went down, flashed its cute LEDs in a multitude of scary colors (e.g. red), and came back up… without issues. I ran a second benchmark to see if there were any improvements. And there were!

The newer drivers yielded an increase in average speed and a much more stable level of throughput. It appears my server-went-to-sleep syndrome has disappeared as well.

I'm nervous about screwing around with my Windows Home Serer for various reasons (heck, I just used Remote Desktop to access the server directly for the first time ever the other day), but this is compelling. I might have to go for it. Obviously, this isn't for the faint of heart/typical consumers out there.

Discuss this Article 2

Lindy
on Mar 30, 2008
SIS and VIA the Mother of all hardware problems. Intel chipsets only please.
Waethorn
on Mar 30, 2008
"According to SiS, the latest driver for SiS191 chipsets is 2.0.1039.1100 dated 03/03/2008." I kind of wonder if SiS even bothered to sign those drivers, or if they considered getting Microsoft to post it to Windows Update. Their track record isn't exactly the greatest for that. There's a reason why newer, sometimes faster (and oft times more buggy) drivers don't always get applied to hardware designs - validation. It's altogether possible that HP hasn't validated the new drivers for their hardware design. Remember that WHS is based on Server 2003 code, and drivers need to be signed and validated separately for it than for XP or Vista. Not only would SiS need to sign the newer driver version themselves, but HP would need to update their WHQL testing procedures for the system to allow for the new driver version. If the WHQL tests fail because of incompatibilities with other components in the system, they wouldn't be able to carry any Windows Home Server certification logos on the system.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• 120 Technical
Sessions
• Networking with Peers
• Expert Speakers


Come See Paul Thurrott & Mary Jo Foley in Person!

Register Now

Office 365 InfoCenter

Get the latest insight and info from Paul

Read Now!

What I Use