HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- ProLiant Deployment and Provisioning
- >
- Re: WinPe 2004 - win32 SmartStart Toolkit - Lights...
ProLiant Deployment and Provisioning
1825769
Members
1991
Online
109687
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
Forums
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
11-03-2004 08:28 AM
11-03-2004 08:28 AM
WinPe 2004 - win32 SmartStart Toolkit - Lights-Out
When booting from my WinPE 2004 CD, that was built using the toolkit script file. The drivers for the ILO and Insight Management seem like they never get loaded. I am also unable to use the hponcfg utility.
Using Devcon, the HW ID's that do not have drivers are:
PCI\VEN_0E11&DEV_B204&SUBSYS_B2060E11
PCI\VEN_0E11&DEV_B203&SUBSYS_B2060E11
The .inf files are in the winpe inf directory, the sys files are in the drivers directory. Other files moved during the install are.
sm2user.dll = system32
insthlth.dll = system32
Any ideas why these can't be loaded? The system I am working on is a DL380 G4, but I have also tried the same build disk on a DL360 G3. Nic and SCSI drivers are working fine as I have both local disk and net access.
Using Devcon, the HW ID's that do not have drivers are:
PCI\VEN_0E11&DEV_B204&SUBSYS_B2060E11
PCI\VEN_0E11&DEV_B203&SUBSYS_B2060E11
The .inf files are in the winpe inf directory, the sys files are in the drivers directory. Other files moved during the install are.
sm2user.dll = system32
insthlth.dll = system32
Any ideas why these can't be loaded? The system I am working on is a DL380 G4, but I have also tried the same build disk on a DL360 G3. Nic and SCSI drivers are working fine as I have both local disk and net access.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2004 09:39 AM
11-04-2004 09:39 AM
Re: WinPe 2004 - win32 SmartStart Toolkit - Lights-Out
I have found out that the ILO and other Compaq management drivers only load if "factory -winpe" is run. I tend to use the following manual method. Is there anyway to get these management drivers loaded under the netcfg setup?
regsvr32 /s netcfgx.dll
factory -minint
netcfg -v -winpe
net start dhcp
net start nla
net start "TCP/IP NetBIOS Helper Service"
regsvr32 /s netcfgx.dll
factory -minint
netcfg -v -winpe
net start dhcp
net start nla
net start "TCP/IP NetBIOS Helper Service"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2004 04:58 AM
11-16-2004 04:58 AM
Re: WinPe 2004 - win32 SmartStart Toolkit - Lights-Out
Jim,
I was having the same problem also. I believe that the -winpe switch is what tells the OS to go and load OEM drivers. Without that it will just load up the default microsoft drivers. If you have found a way to do this without using the -winpe switch please post it.
Jeff
I was having the same problem also. I believe that the -winpe switch is what tells the OS to go and load OEM drivers. Without that it will just load up the default microsoft drivers. If you have found a way to do this without using the -winpe switch please post it.
Jeff
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP