Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Trouble Loading Hp Mass Storage Drivers In WinPE

- - - - -

This topic has been archived. This means that you cannot reply to this topic.
2 replies to this topic

#1
MycroftHolmes

MycroftHolmes
  • Member
  • 5 posts
  • Joined 13-October 04
Hi,

I'm having trouble loading the mass storage controller drivers in PE. I ran the hp_winpe_customize.cmd command before making the disk. This batch file adds subdirectories to the system32 folder, and adds a [OemDriverParams] section to the winpeoem.sif file.

I checked to ensure the driver folders were created and contain files.
I checked the winpeoem.sif file to make sure the proper lines were added.

These are the lines added to the file:
[OemDriverParams]
OemDriverRoot=""
OemDriverDirs=cpqcissm, cpqcissm2, cpqcissm3, lsicsb6, megaide, megaide2, megaide3, symmpi

When I run devcon, none of the drivers from the sub-directories seem to be loaded.

For example the driver for this device is in one of the subdirectories:
PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11&REV_02\2&647397D&0&20
Name: RAID Controller
No driver information available for device.

and this driver loaded but it looks like the default driver:
PCI\VEN_8086&DEV_1229&SUBSYS_B1340E11&REV_08\2&EBB567F&0&10
Name: HP NC3163 Fast Ethernet NIC
Driver installed from x:\i386\inf\oem1.inf [D101M.ndi]. 1 file(s) used by driver:
X:\i386\system32\DRIVERS\n100325.sys


I also tried putting the drivers for the 5300 controller on a floppy and hitting f6 during the boot process.

I was warned that that a Microsoft driver already exists for this device and I told it to install the new one anyway.

Still no dice. The strange thing is that I have access to the drives on that controller. I can use diskpart to manipulate them. I assume that this means that some driver is loaded, is that correct?

The main reason I need the driver to work correctly is that I'm trying to use WMI to list all of the SCSI controllers. When I attempt that I get nothing back.

Does anyone have an idea what I may be doing wrong? Any help would be appreciated.

Regards,

-Jim


How to remove advertisement from MSFN

#2
ChrisBaksa

ChrisBaksa

    Member

  • Member
  • PipPip
  • 230 posts
  • Joined 05-March 04

Does anyone have an idea what I may be doing wrong? Any help would be appreciated.

PE has a 5300 driver in the OS by default.
You must modify the txtsetup.sif file and include the new PNP values as well as replace the driver files that already exist before you burn your new image.

The winpeoem.sif method is for mass controller drivers that do not exist at all.

As an example... Here is the chunk I modified in my txtsetup.sif to see the new controllers.

PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11 = "cpqcissm"
PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11 = "cpqcissm"
PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11 = "cpqcissm"
PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11 = "cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409A0E11 = "cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409B0E11 = "cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409C0E11 = "cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_40910E11 = "cpqcissm"
PCI\VEN_0E11&DEV_0046&SUBSYS_409D0E11 = "cpqcissm"

Without it.. you will never see a 6400 or 6i controller even if you replace the driver files.

Chris

#3
MycroftHolmes

MycroftHolmes
  • Member
  • 5 posts
  • Joined 13-October 04
Thanks Chris,

That seemed to work to a point. I can now see the driver when I do a "devcon drivernodes", but I still get the same results with "devcon driverfiles" and I still cannot get nothing back when I attempt enumerate the instances of the WMI win32_SCSIController class, which is my main problem. I need to be able to list all array controllers in the machine.

When I run devcon drivernodes within PE, I get this:

X:\i386\system32>devcon drivernodes *b060*
PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11&REV_02\2&647397D&0&20
Name: RAID Controller
DriverNode #0:
Inf file is x:\i386\inf\cpqcissm.inf
Inf section is cpqcissm_Inst
Driver description is Smart Array 5300 Controller
Manufacturer name is Hewlett-Packard Company
Provider name is Hewlett-Packard Company
Driver date is 1/21/2004
Driver version is 5.60.0.32
Driver node rank is 1
Driver node flags are 00002244
Inf is digitally signed
1 matching device(s) found.

I ran devcon on the same server while running Server 2003 and I got the following results:

C:\>devcon driverfiles *b060*
PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11&REV_02\2&647397D&0&20
Name: Smart Array 5300 Controller
Driver installed from c:\windows\inf\oem9.inf [cpqcissm_Inst]. 2 file(s) use
d by driver:
C:\WINDOWS\system32\DRIVERS\cpqcissm.sys
C:\WINDOWS\system32\cpqcissm.dll
1 matching device(s) found.

C:\>devcon drivernodes *b060*
PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11&REV_02\2&647397D&0&20
Name: Smart Array 5300 Controller
.
.
.
DriverNode #2:
Inf file is c:\windows\inf\oem9.inf
Inf section is cpqcissm_Inst
Driver description is Smart Array 5300 Controller
Manufacturer name is Hewlett-Packard Company
Provider name is Hewlett-Packard Company
Driver date is 1/21/2004
Driver version is 5.60.0.32
Driver node rank is 1
Driver node flags are 00003244
Inf is digitally signed
1 matching device(s) found.

Regards,

-Jim