buymycorp
asked on
HP ProLiant ML115 Windows XP Pro (32-bit) drivers
I quoted my client a Proliant ML115 server (Model 480417-005) to function as an Avaya Voicemail Pro Server for (20) mailboxes. My original quote included a copy of Windows 2003 Server with 5 CALs. Well, long story short, my client balked at the price for the O/S and demanded that I swap it out for Windows XP Pro (32-bit). I verified that Avaya VM Pro could run on Windows XP Pro (32-bit). I changed my quote and the client gave me a PO.
The server arrived today. I opened the separately packaged Windows XP Pro CD and installed it. Next, I went to install the HP Drivers to get my chipset, display adapter & NIC drivers installed. You guessed it...Windows XP Pro drivers were not available. Doh!
I need help finding bandaid drivers that will simply work.
nVidia Chipset & NIC drivers being the most coveted.
Thanks.
The server arrived today. I opened the separately packaged Windows XP Pro CD and installed it. Next, I went to install the HP Drivers to get my chipset, display adapter & NIC drivers installed. You guessed it...Windows XP Pro drivers were not available. Doh!
I need help finding bandaid drivers that will simply work.
nVidia Chipset & NIC drivers being the most coveted.
Thanks.
This may be a long stretch, but have you tried using nvidia's website for the chipset drivers?
"I verified that Avaya VM Pro could run on Windows XP Pro (32-bit)."
Regardless if someone told you it works or not, I *always* tell the client that it's not built for XP, and I am essentially hacking the drivers to be compatible. Although, this may sound very primitive, it gets the point across, and no one is shocked when they findout that they have to purchase a 3rd party NIC.
I have a major tip for you and I do hope you consider this. Get a USB to ETHERNET adapter that is well known for being plug n play compatible. Then you can connect that comptuer to windows update, and usually yank the drivers directly. ;) Shhhh.... that's our secret, EE.
Regardless if someone told you it works or not, I *always* tell the client that it's not built for XP, and I am essentially hacking the drivers to be compatible. Although, this may sound very primitive, it gets the point across, and no one is shocked when they findout that they have to purchase a 3rd party NIC.
I have a major tip for you and I do hope you consider this. Get a USB to ETHERNET adapter that is well known for being plug n play compatible. Then you can connect that comptuer to windows update, and usually yank the drivers directly. ;) Shhhh.... that's our secret, EE.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This solution was just what I needed. I quickly discovered that the NICs were Broadcom NICs - and soon I knew EXACTLY what model they were. This information was all I needed to search Broadcom's site for drivers. This was an excellent tip. I feel smarter after having read it. I feel confident that I can fix driver problems that would stump others! Thanks.
For NIC Driver, Try this link. http://www.versiontracker.com/dyn/moreinfo/win/151936&mode=info
for nVidia Chipset, http://www.nvidia.com/object/nforce_winxp_15.16.html
for nVidia Chipset, http://www.nvidia.com/object/nforce_winxp_15.16.html
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1238448211083+28353475&threadId=1251357
Seems like you can get the NIC drivers you need there. Will have to work on those chipset drivers and get back to you.