- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ML370 G3 Boot Disk
ProLiant Servers (ML,DL,SL)
1752679
Members
5670
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2003 07:27 AM
03-20-2003 07:27 AM
I've been successfully using a dos network boot disk on our Proliant ML370G2 servers to attach to a build server and perform a scripted Win2k build but now I have the G3 model and the N100.dos driver does not load anymore.
Typically this would be down to a different PCI slot address (0x0002 for example) and if I had the wrong one for the NIC I was using, it would inform me of the correct one when the driver failed to load but not so with the G3 and it???s new PCIX GB NICS it seems.
Basically, does anyone know how you can tell what PCI slot number the G3 on board NIC uses and/or whether you can still use N100.dos?
Many thanks
Paul R.
Typically this would be down to a different PCI slot address (0x0002 for example) and if I had the wrong one for the NIC I was using, it would inform me of the correct one when the driver failed to load but not so with the G3 and it???s new PCIX GB NICS it seems.
Basically, does anyone know how you can tell what PCI slot number the G3 on board NIC uses and/or whether you can still use N100.dos?
Many thanks
Paul R.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2003 05:32 AM
03-24-2003 05:32 AM
Solution
Hi Paul;
The ML370 G3 has a Broadcom NIC on it. The older servers had an Intel chipset that used n100.dos.
You'll need b57.dos from SP20958.exe located at ftp://ftp.compaq.com/pub/softpaq/sp20501-21000/
Once you're using the correct driver, you should have the same ability to determine the slot number with n100.dos.
Hope that helps,
Janine
The ML370 G3 has a Broadcom NIC on it. The older servers had an Intel chipset that used n100.dos.
You'll need b57.dos from SP20958.exe located at ftp://ftp.compaq.com/pub/softpaq/sp20501-21000/
Once you're using the correct driver, you should have the same ability to determine the slot number with n100.dos.
Hope that helps,
Janine
To get results you've never had before, try something you've never tried before.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP