26 Reply by ef

(74 replies, posted in BartPE - UBCD4Win - WinPE)

Hi,
Happy New Year.

For the NC373i NIC the Hardware ID from Windows Device manager is

B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C&REV_12

For the NC373T it is

B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7037103C&REV_12

Although most of other servers run R2, this HP one runs a regular (not R2) W2k3 version.
As suggested, I tried also a regular (not R2) W2k3 Sp2 build and the result is the same.

Edoardo

Go to forum: BartPE - UBCD4Win - WinPE

27 Reply by ef

(74 replies, posted in BartPE - UBCD4Win - WinPE)

For the NC373i the Compatible IDs from Windows Device manager are

B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7038103C
B06BDRV\L2ND&PCI_164C14E4
B06BDRV\L2ND

For the NC373T they are

B06BDRV\L2ND&PCI_164C14E4&SUBSYS_7037103C
B06BDRV\L2ND&PCI_164C14E4
B06BDRV\L2ND

I will also try a regular W2k3 Sp2 build and report to you.


Edoardo

Go to forum: BartPE - UBCD4Win - WinPE

28 Reply by ef

(74 replies, posted in BartPE - UBCD4Win - WinPE)

OverFlow wrote:

in UBCD4Win350\plugin\DriverPacks.net\LAN\lan.inf

can you find these lines?

nt5\BXVBD.INF=20,,1
wnt5\BXVBDX.SYS=4,,1

I have
wnt5\BXVBD.INF=20,,1
wnt5\BXVBDX.SYS=4,,1

OverFlow wrote:

that HWID is actually for a Broadcom NIC... HP had to get it from somewhere wink

And is included in the pack you are using, in folder
DriverPacks\DP_LAN_wnt5_x86-32_90904\D\L\B3\BXVBD.INF

Sorry for my inexperience:
- where is supposed to be found the DriverPacks\DP_LAN_wnt5_x86-32_90904\D\L\B3\BXVBD.INF file? I simply copied the DP_LAN_wnt5_x86-32_90904.7z pack in my D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\DriverPacks folder before BASE configuring and ISO building. Did you mean the \D\L\B3\BXVBD.INF file contained in this .7z pack?

- what is the portion of the HWID string I have to search for in this bxvbd.inf file?
In the DP_LAN_wnt5_x86-32_90904.7z pack version of this file I can find only the generic string

%bcm5708c_desc% = bcm5708c_inst_x86, pci\ven_14e4&dev_164c

while in the downloadable HP version of that file I can find both

%NC373i_desc% = NC373i_inst_x86, pci\ven_14e4&dev_164c&subsys_7038103c

and

%NC373T_desc% = NC373T_inst_x86, pci\ven_14e4&dev_164c&subsys_7037103c

OverFlow wrote:

can you verify the md5 sum for that pack is E28C281D8933772E8E3BB9B3C62BF9C5 ?

OK, verified.

Thank you for your support.

Edoardo

Go to forum: BartPE - UBCD4Win - WinPE

29 Reply by ef

(74 replies, posted in BartPE - UBCD4Win - WinPE)

OverFlow wrote:

They are a very nice series of servers

I agree, very reliable and fast (at least for my needs).

Did you see anything wrong in my DPs_BASE.log?

Lan DriverPack 9.09.04 includes both bxnd.inf and bxnd52x.sys files at D\L\B3, but on the bxnd.inf file I can't find nor proper Localizable strings and their HWIDs.
They seem to be included in the downloadable version.

Hope it helps, I'm not very skilled on this.

Edoardo

Go to forum: BartPE - UBCD4Win - WinPE

30 Reply by ef

(74 replies, posted in BartPE - UBCD4Win - WinPE)

I forgot to mention that the server is a HP Proliant ML350 G5 (Product ID 416894-421).

I didn't try to add drivers myself, but they are available at

http://h20000.www2.hp.com/bizsupport/Te … &idx=2

The bxnd52x.sys file has the same driver name used in Windows Computer Management - NIC properties.

Go to forum: BartPE - UBCD4Win - WinPE

31 Topic by ef

(74 replies, posted in BartPE - UBCD4Win - WinPE)

- Platform: Ubcd4Win 3.50
- Source: W2k3 R2 Std SP2
- Base: 8.12.5
- MassStorage DriverPack: 9.09.r6
- Lan DriverPack: 9.09.04

- Issue: when starting network services from the Ubcd4Win boot disk, I have "Error installing network devices".

- Installed NICs:
HP NC373i Multifunction Gigabit Server Adapter (HP 2.8.13.0 Windows driver, 30/06/2006)
HP NC373T PCIe Multifunction Gig Server Adapter (same driver)

- From the HwIDs tool:

=========== 
PCI Devices 
=========== 
...
PCI\VEN_14E4&DEV_164C&SUBSYS_7037103C&REV_12\5&223905C6&0&000020: HP NC373T Virtual Bus Device
PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_12\5&43097C6&0&0000E0: HP NC373i Virtual Bus Device
...

- DPs_BASE.log content

2009-12-29 13:27:37 : <INIT> DriverPacks BASE 8.12.5 initialized.
2009-12-29 13:27:37 : <INIT> Host environment: WIN_XP Service Pack 3 on X86 CPU.
2009-12-29 13:27:37 : <INIT> Created temporary working directory.
2009-12-29 13:27:37 : <INIT> Imported proxy settings from Internet Explorer.
2009-12-29 13:27:37 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-12-29 13:27:37 : <INIT> 	Detected DriverPack LAN 90904!
2009-12-29 13:27:37 : <INIT> 	Detected DriverPack MassStorage 909r6!
2009-12-29 13:27:37 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-12-29 13:27:37 : <INIT> 	Finished scanning.
2009-12-29 13:27:37 : <INIT> Detected settings file "D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\DPs_BASE.ini".
2009-12-29 13:27:37 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2009-12-29 13:27:37 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-12-29 13:27:37 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2009-12-29 13:27:37 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2009-12-29 13:27:37 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-12-29 13:27:37 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-12-29 13:27:37 : <INIT> wnt5_x86-32_bartpe is the selected installation platform .
2009-12-29 13:27:37 : <INIT> Imported settings from settings file.
2009-12-29 13:27:37 : <INIT> [OptionalSettings]\QSC BartPE default (no)    was set.
2009-12-29 13:27:37 : <GUI>  Initialized GUI.
2009-12-29 13:27:37 : <GUI>  Created a list of all available language files.
2009-12-29 13:27:37 : <GUI>  Set the last used language, English, as the GUI language.
2009-12-29 13:29:03 : <GUI>  Saved settings!
2009-12-29 13:29:03 : <GUI>  Closed GUI.
2009-12-29 13:29:03 : <SEL>  Selected module: mod_slip_wnt5_x86-32_bartpe.
2009-12-29 13:29:03 : <PREP> D:\UBCD4Win_3.50\plugin\DriverPacks.net\LAN\LAN.inf info written.
2009-12-29 13:29:03 : <PREP> D:\UBCD4Win_3.50\plugin\DriverPacks.net\MassStorage\MassStorage.inf header info written.
2009-12-29 13:29:09 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2009-12-29 13:29:09 : <SLIP> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DPMtmp\DriverPack_MassStorage_wnt5_x86-32.ini
2009-12-29 13:29:10 : <SLIP> Processing the files now. This may take a minute.
2009-12-29 13:29:31 : <SLIP> Copied DriverPack MassStorage text mode driver files to BartPE Plugin folder.
2009-12-29 13:29:31 : <SLIP> Slipstreamed DriverPack MassStorage text mode driver files.
2009-12-29 13:29:34 : <SLIP> Updated the MassStorage.ini [SetValue] sections to support DP MassStorage text mode drivers.
2009-12-29 13:29:41 : <PLUGIN> Extracted DriverPack LAN.
2009-12-29 13:29:48 : <PLUGIN> Extracted DriverPack MassStorage.
2009-12-29 13:29:48 : <PLUGIN> Started CAB compressing DriverPack LAN (estimated 2 minutes).
2009-12-29 13:29:48 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\DriverPack_LAN_wnt5_x86-32.ini
2009-12-29 13:30:04 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, E1000325.SY?
2009-12-29 13:30:04 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, E1000MSG.DL?
2009-12-29 13:30:04 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, E1000NT5.SY?
2009-12-29 13:30:05 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, E1E5032.SY?
2009-12-29 13:30:05 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, E1E5132.SY?
2009-12-29 13:30:05 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, NICINST.DL?
2009-12-29 13:30:05 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\I2, \wnt5, NICINSTE.DL?
2009-12-29 13:30:10 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3, \wnt5, FDCO1.DLL
2009-12-29 13:30:11 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3, \wnt5, NVEFD2K.SYS
2009-12-29 13:30:11 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3, \wnt5, NVNRM.SYS
2009-12-29 13:30:11 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3\PreNRM\Win2K, \wnt5, FDCO1.DL?
2009-12-29 13:30:11 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3\PreNRM\Win2K, \wnt5, NVCOE.DL?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3\PreNRM\Win2K, \wnt5, NVENET.SY?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3\PreNRM\WinXP, \wnt5, FDCO1.DL?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3\PreNRM\WinXP, \wnt5, NVCOE.DL?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV3\PreNRM\WinXP, \wnt5, NVENET.SY?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, BDCO1.DL?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, FDCO1.DL?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVCONRM.DL?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVEFD2K.SY?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVEFDXP.SY?
2009-12-29 13:30:12 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVENETFD.IN?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVENETFD.INF
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVNETBUS.IN?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVNETBUS.INF
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVNETBUS.SY?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVNRM.SY?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVSNPU.SY?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV4, \wnt5, NVTCP.SY?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, BDCO1.DL?
2009-12-29 13:30:13 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, FDCO1.DL?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVCONRM.DL?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVEFD2K.SY?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVEFDXP.SY?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVENETFD.IN?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVENETFD.INF
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVNETBUS.IN?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVNETBUS.INF
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVNETBUS.SY?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVNRM.SY?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVSNPU.SY?
2009-12-29 13:30:14 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6, \wnt5, NVTCP.SY?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, BDCO1.DL?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, FDCO1.DL?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVCONRM.DL?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVEFD2K.SY?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVEFDXP.SY?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVENETFD.IN?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVENETFD.INF
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVNETBUS.IN?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVNETBUS.INF
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVNETBUS.SY?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVNRM.SY?
2009-12-29 13:30:15 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVPHY.BI?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVSNPU.SY?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV6A, \wnt5, NVTCP.SY?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, BDCO1.DL?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, FDCO1.DL?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVCONRM.DL?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVEFD2K.SY?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVEFDXP.SY?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVENETFD.IN?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVENETFD.INF
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVNETBUS.IN?
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVNETBUS.INF
2009-12-29 13:30:16 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVNETBUS.SY?
2009-12-29 13:30:17 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVNRM.SY?
2009-12-29 13:30:17 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\NV7, \wnt5, NVPHY.BI?
2009-12-29 13:30:18 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\R3, \wnt5, RTNICPROP32.DL?
2009-12-29 13:30:19 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\SIS2, \wnt5, SISGBE2K.SY?
2009-12-29 13:30:19 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\SIS2, \wnt5, SISGBEXP.SY?
2009-12-29 13:30:21 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\SU1, \wnt5, RTL8029.SY?
2009-12-29 13:30:21 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\U4, \wnt5, CB103ND5.SY?
2009-12-29 13:30:21 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\U4, \wnt5, NETCB103.IN?
2009-12-29 13:30:21 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\U4, \wnt5, NETCB103.INF
2009-12-29 13:30:21 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\U5, \wnt5, NETUSR.IN?
2009-12-29 13:30:21 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\U5, \wnt5, NETUSR.INF
2009-12-29 13:30:22 : <PLUGIN> D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\tmp\DriverPacks\DriverPack LAN\D\L\V3, \wnt5, VUINS32.DL?
2009-12-29 13:30:22 : <PLUGIN> Finished CAB compressing DriverPack LAN.
2009-12-29 13:30:25 : <PLUGIN> Saved settings!
2009-12-29 13:30:25 : <PLUGIN> Slipstream finished in 1 minutes and 22 seconds.
2009-12-29 13:30:34 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang	= "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform	= "bartpe"
; trailing backslash is allowed, but not necessary
location	= "D:\UBCD4Win_3.50\plugin"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "no"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_LAN		= "yes"
DP_MassStorage	= "yes"
DP_MassStorage_textmode = "yes"
2009-12-29 13:30:34 : <CLNP> Create a DPs_Base.log backup @ D:\UBCD4Win_3.50\plugin\DriverPacks.net\BASE\LogFiles\DPs_BASE_09-12-29_13-30.log
2009-12-29 13:30:34 : <CLNP> Program terminated.

Let me know if you need more info.
Thank you

Edoardo

Go to forum: BartPE - UBCD4Win - WinPE

32 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

I tried the latest 9.07r3 MassStorage DP and it works perfectly!
Thank you very much to the DriverPacks team.

Edoardo

Go to forum: DriverPack Mass Storage

33 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

Just tried building using WinXpSp3 and that driver in [P4]: it works fine too, like it did building with Win2k3.
I'm sorry I can't help with Win2k

Edoardo

Go to forum: DriverPack Mass Storage

34 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

JakeLD wrote:

Hi ef, I downloaded your driver and it seems to be compatible with all nt5 system (2k,xp, 2003). Have you tried the driver with other OS than 2003 ?

Hi, No I didn't yet because I need a W2k3 build to solve the other Ibm ServerRaid issue previously explained.
But I can test building using WinXpSp3: I will also replace the same driver in [P4] and report to you.
Thank you

Edoardo

Go to forum: DriverPack Mass Storage

35 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

If the driver I previously uploaded isn't trusted (I can understand that), you can download the Promise FastTrack S150 SX4 SATA RAID controller driver (W2k3) ver. 09/27/2004, 2.00.64.23 for Fujitsu-Siemens Primergy TX150 S3 (Fibrecat N20i) servers  at
http://ts.fujitsu.com/support/linkappli … p;ID=23386
Select "Industry standard server" - "PRIMERGY" - "PRIMERGY TXxxx" - "PRIMERGY TX150 S3 SATA" - "Microsoft Windows Server 2003 (32 bit)" - "SATA RAID" - "Promise Technology FastTrak S150 SX4 SATA-RAID controller" - "Drivers (SW-Kit 5.02)"
You can read "Version 2.0 0064 23  Date: 16.05.2006", but after downloading the fastsx.inf file contains 

DriverVer=09/27/2004, 2.00.64.23

as it should be.
Hope it helps to have it added to the MassStorage DP.

Edoardo

Go to forum: DriverPack Mass Storage

36 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

i belive it is createing a conflict with the drivers with the same name in the pack...
if you wish to use DriverPack MassStorage and a custom driver you will need to


In the mass storage INI is this section...

[P4]
ms_count=1
ms_1_deviceName="Promise FastTrak S150 SX4/SX4000 (WXP)"
ms_1_tag="fastsx"
ms_1_sysFile="fastsx.sys"
ms_1_hwids="fastsxPCI,PCI\VEN_105A&DEV_6621,PCI\VEN_105A&DEV_6622"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"

change ms_1_tag="fastsx"  to  ms_1_tag="fastsxXP"




OR replace the driver in [P4] with the update smile

Hi,
as you suggested I replaced the 9.05r2 driver in [P4S] (I used w2k3 to build) with the update and it works fine.
Since your latest post, I can see in the nightlies repository that DpMasstoragePack was updated to 9.06 (n1, n1 and r1): is it expected an updated nightly including that Promise driver?
Thank you and sorry for be boring.

Go to forum: DriverPack Mass Storage

37 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

yes we will make sure the driver is added to DriverPack MassStorage...

I assume you will be willing to test a nightly for us?

Hi Overflow,
did you have a chance to add that driver to the MassStorage DP?
Thanks for your support.

Edoardo

Go to forum: DriverPack Mass Storage

38 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

It's better (and simpler) for me testing your updated MassStorage DP, when it will be available to download.
Thank you.

Go to forum: DriverPack Mass Storage

39 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

@cdob

While waiting for latest DP by Overflow, I tried adding the plugin you suggested with MassStorage plugin enabled, but it didn't help. Still errors Source fastsxk3 and nvgts, Event Ids 4, no disks detected. I didn't enable the PnpInterface plugin you wrote about on 2009-05-02 at 19:05:16. Was it required?

Go to forum: DriverPack Mass Storage

40 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

yes we will make sure the driver is added to DriverPack MassStorage...

I assume you will be willing to test a nightly for us?

Sure, let me know when it's ready to test.

OverFlow wrote:

Thanks for reporting your issue - it makes DriverPacks better for everyone!

Thank you all guys for your efforts, it's the minimum I can do for helping you!

Go to forum: DriverPack Mass Storage

41 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

So what's next step: is it expected an updated MassStorage DP?
Or is there a working way to both enable MassStorage plug-in and add myself this driver in the "Drivers" folder before building the boot disk?

Go to forum: DriverPack Mass Storage

42 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

Update: that driver is OK when loaded from a floppy disk using F6 when booting UBCD4WIN. From the SataSX4\32x folder I copied to floppy
- fastsx
- fastsx.cat
- fastsx.inf
- fastsx.inf
Then I added to floppy the SataSX4\ORG.TXTSETUP.32x file renamed to TXTSETUP.OEM.
It works fine: Device management shows Promise 4 Disk RAID5 SCSI Disk Device (although an unknown RAID controller with the Promise HWID is still listed), Disk Management shows logical volumes and I can browse disks content.

Previously I tried building the boot disk after adding the 4 fastsx files to the drivers\SCSIAdapter\Promise\fastsx folder of my UBCD4WIN install root (disabling the MassStorage plugin), but it didn't detected disks, probably because I forgot adding also the txtsetup.oem file. This is my next test I will try.

Go to forum: DriverPack Mass Storage

43 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

This is the download link:
http://rapidshare.com/files/232790186/SataSX4.zip.html

And yes, it is the Promise FastTrak S150 SX4  Windows driver - Date 27/09/2004 - Ver. 2.0.64.23. It's the same I have installed on my box and it's copied from the FSC SmartStart disk.

Go to forum: DriverPack Mass Storage

44 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

No, but I have found those drivers in the FSC ServerStart first disk. If you have an email address for sending them to you let me know.

Go to forum: DriverPack Mass Storage

45 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

The server is running Windows Server 2003 Standard Edition SP2. Winver reports it as Windows Server 2003 Appliance Edition ver. 5.2 (build 3790.srv03_sp2_gdr.090319-1204: Service Pack 2).

Device Management:
- Promise 4 Disk RAID5 SCSI Disk Device
  HWID SCSI\DISK&VEN_PROMISE&PROD_4_DISK_RAID5&REV_1.10\5&2DC0664C&0&000
  Driver Microsoft 01/10/2002 ver. 5.2.3790.0
- Windows Promise FastTrak S150 SX4 (tm) Controller
  HWID PCI\VEN_105A&DEV_6622&SUBSYS_6622105A&REV_01\4&5A988DE&0&28F0
  Driver Promise Technology 27/09/2004 ver. 2.0.64.23

Regarding F6 at boot, I will test and let you know results.

For the Busmaster capable PCI slot, I don't know how to check: this is a link for the server datasheet, if useful:
http://www.ipso.it/prodotti/prodotti_nu … t_n20i.pdf

Go to forum: DriverPack Mass Storage

46 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

As suggested, I tried also creating an UBCD4WIN 3.50 (W2k3Sp2 - Base 8.12.4) with disabled MassStorage plugin and adding only Promise FastTrak S150 SX4 Windows drivers ver. 05/20/2004, 2.00.00.25: still no disks are detected.
What else could I try? Any help appreciated.

Edoardo

Go to forum: DriverPack Mass Storage

47 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

cdob wrote:

This event log message reminds to PnpInterface at nvgst.sys.

Strange:
Promise txtsetup.oem dosn't set PnpInterface.
And fastsy.inf does set PnpInterface.

There are used different driver names: fastsx.sys and fastsxk3.sys.
Adjust previous plugin.

[Version]
Signature="$Windows NT$"

[PEBuilder]
Name="Driver: addon PnpInterface"
Enable=1

[SetupReg.AddReg]
0x4, "ControlSet001\Services\3wareDrv\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\3wDrv100\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts5\Parameters\PnpInterface", "5", 0x1
0x4, "ControlSet001\Services\nvgts6\Parameters\PnpInterface", "5", 0x1

[SetupReg.AddReg.2600]  ;XP
0x4, "ControlSet001\Services\FastSx\Parameters\PnpInterface", "5", 0x1

[SetupReg.AddReg.3790]  ;2003
0x4, "ControlSet001\Services\FastSxK3\Parameters\PnpInterface", "5", 0x1

Sorry for the delay in my answwer: unfortunately disks aren't still detected, even with this plugin and I can still read in the UBCD4WIN system event log the same error event id 4, source FastSxK3.
I checked regedit and both "HKLM\SYSTEM\CurrentControlSet\Services\FastSxK3\Parameters\PnpInterface" and "HKLM\SYSTEM\ControlSet001\Services\FastSxK3\Parameters\PnpInterface" contain the "5" value set to 0x1.

Thank you all for any help.

Go to forum: DriverPack Mass Storage

48 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

Ibm ServeRaid 6m: building also with W2k3Sp2 as source solved the issue: the Virtual Disk Service starts and I can read the mirrored volume. So the combination of Ubcd4win 3.50, Base 8.12.4 and MassStorage DP 9.03.r1 is OK.

Promise FastTrak S150 SX4:even with W2k3Sp2 as source, the attached disks aren't found as previously reported using WinXpSp3. In the boot disk System event log, I have the following errors:
- Source fastsxk3, Event Id 4, Description: "The description for Event ID ( 4 ) in Source (fastsxk3) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event."
- Source Application Popup, Event Id 877, Description:" There was error [DATABASE NOT LOADED] processing the driver database"

Regarding the suggested test of creating a UBCD4WIN disk with only Promise FastTrak S150 SX4 drivers, what should be the procedure?

Go to forum: DriverPack Mass Storage

49 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

I updated to UBCD4WIN 3.50, WinXpSP3 as source, Base 8.12.4, MassStorage DP 9.03r1.

1. Promise FastTrak S150 SX4: I updated the SCSI controller BIOS to the 2.0.70.24 version as suggested, but UBCD4WIN doesn't find any disk. In the Hardware Management snap-in, I can see from the HWID the Promise controller listed as an Unknown "RAID device".
The RAID 1 array is hardware-based.

2. IBM ServeRAID 6M: the RAID 1 array is software-based (W2k3) with 2 dynamic disks.
Windows shows the mirrored volume in a healthy status.
UBCD4WIN's instead shows in the the Disk Management snap-in a failed mirrored volume (red cross) with no drive letter associated and 2 active disks. I can't assign a drive letter to the voume, only remove the mirror (I didn't try this operation). UBCD4WIN's Hardware management snap-in shows 2 "Ibm ServeRaid Scsi Disk device" and the Ibm ServeRaid controller listed as unknown "RAID controller" (recognised from the HWID).
If I boot the same UBCD4WIN disk on a xseries 445 server with disks attached on the onboard dual LSI controller and HW mirror, all is OK, so the LSI driver shouldn't be an issue.
From my previous UBCD4WIN 3.04 disk (which is able to see those software-mirrored disks) I noticed that the Virtual Disk Service is running: the 3.50 one instead has it stopped and it can't be started because the x:\i386\system32\vds.exe file is missing. Could it be the cause of my issue?

3. I read at http://forum.driverpacks.net/viewtopic.php?id=3690 about both Promise fastsx.sys and Ibm nfrd960.sys: could that issue being in same way related to mine?

Thank you

Go to forum: DriverPack Mass Storage

50 Reply by ef

(49 replies, posted in DriverPack Mass Storage)

Probably it's due to my poor experience, but I don't understand.
I do not have disks attached to the LSI on-board RAID controller PCI\VEN_1000&DEV_0030 of my IBM servers. As I wrote on my first post, is the IBM ServerRaid 6M controller (PCI\VEN_9005&DEV_0250&SUBSYS_02791014&REV_02\4&8C37DC5&0&4010) which isn't discovered with its disks. Is it important to update L8/L10 LSI drivers to discover the IBM controller?
And no, I didn't try the latest Base yet, but if you think it could be of any help I will do so.

Go to forum: DriverPack Mass Storage