Search options (Page 77 of 213)

What method do you use to update your source with the DriverPacks?

The HWIDs from that driver are...

PCI\VEN_8086&DEV_27C3&CC_0104 is supported by D\M\I4 ICH7R/DH - 82801GR/GH
PCI\VEN_8086&DEV_2652&CC_0104 is supported by D\M\I2 ICH6R - 82801FR
PCI\VEN_8086&DEV_24DF&CC_0104 is supported by D\M\I1 ICH5R - 82801ER
PCI\VEN_8086&DEV_25B0&CC_0104 is supported by D\M\I1 ESB - 6300ESB

at least four different drivers might match the HWIDs from that OEM IASTOR.inf file
however HP states that is is a 945GM Express Chipset...
Google tells me 945GM uses ICH 7...

I will Guess that
PCI\VEN_8086&DEV_27C3&CC_0104
- ICH7R/DH
- 82801GR/GH
is your HWID...

currently supported by 909r6 in D\M\I4 iastor Version 8.9.2.1002

the version of iastor from your download is Version 5.5.0.1035
That version is the same version as in D\M\I1

Could you try moving your HWID from D\M\I4 to D\M\I1 (section [I4] to section [I1]) in the DriverPack_MassStorage_wnt5_x86-32.ini file and testing?

Note PCI\VEN_8086&DEV_27C3&CC_0104 is actually supported by all four folders I1, I2, I3, I4...
1 is oldest 4 is newest....
It would be nice to use the latest driver that works...

so if you were in a really really good mood you could try them in reverse order
by moving the HWID to each of the appropriate sections in the mass INI;
I4 we already know fails
I3 ?
I2 ?
I1 ? - Should definately work since it matches with your download from HP

You may for purpose of creating a BartPE plugin just comment the lines...

with a normal DriverPacks BASE slipstream to a Win NT5 source if you do not remove the folder there might still be a conflict created...

That should work...

try our latest nightly and please report success or failure.

http://driverpacks.sytes.net/driverpack … 2_909r6.7z

Welcome to DriverPacks

thanks for reporting it helps everyone!

LOL

don't sysprep... (not exactly what i said to do)

I said that offline sysprep was probably the BEST WAY to inject drivers. (i still think so)

DON'T run sysprep. that will definately be a mess...

You are not facing as big of a task with the mass storage controller as you will be with the network bindings...
all of your networking functions will depend on having the identical network card(s) which you probably will not...
In which case that is going to be your biggest problem.

Adding mass storage drivers manually is a good amount of work... but it's doable.
Try OffLine sysprep first (you have a backup image ) it is likely that the HAL will be the same.

OffLine sysprep is not even close to MS SysPrep Two completely different animals

That is an excellent question...  answer; No.

At least not directly... We have a Team of highly talented individuals that contribute to the DriverPacks.

One such outstanding individual is Galapo who provides a tool called OffLine SysPrep.
http://forum.driverpacks.net/viewtopic.php?id=3312

OffLine SysPrep will update your Source with DriverPack MassStorage flawlessly It also has some other cool features like automatic hal detection ect. IDK if 2k3 is supported for certain but it is definitely your best shot.

You might also look at the Universal Imaging section here at DriverPacks
http://forum.driverpacks.net/viewforum.php?id=30

Welcome to DriverPacks!

Excellent first post

yes if you put a pack INI in with the proper commands it will run setup...

docs for the pack ini are in the DriverPacks BASE DOCs folder.

Lets use mr_smartepants work as a perfect example from the graphics pack A

[DriverPack]
platform	= "wnt5_x86-32" 
name		= "Graphics A"
; version 906 
; includes BartPE Code
rootDir		= "D\G"
; OPTIONAL
classes		= "Display"
driverCount	= 3
decompSize	= 162
compSize	= 70

--snip--

--snip--

[N1]
; BartPE Code 
ms_count	 	= 1
ms_1_tag 	= "N1_nv4"
ms_1_sysfile 	= "nv4_mini.sys"
ms_1_exc_skipIfOS="wxp,w2k3"
; REQUIRED
exc_count		= 2
; OPTIONAL
exc_1_tagFiles	= 2
exc_1_tagFile1	= "%SystemDrive%\nvidia.ins"
exc_1_tagFile2	= "%SystemRoot%\system32\drivers\nv4_mini.sys"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\G\N1\*.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 2
exc_1_command1  = "regedit /s %systemdrive%\nvidia.ins" 
exc_1_command2  = "cmd.exe /c DEL /F /S /Q %SystemDrive%\nvidia.ins"

let's apply your layout to that shining example

DP_WICustom_wnt5_x86-32_09.09.14.1.7z contains:
D
  3
    S
      E
        inf and all unpacked cab files

Let's assume you want to trigger the setup.exe when the local machine matches a HWID with a HWID contained in one of the four supplied inf files.

[DriverPack]
platform	= "wnt5_x86-32" 
name		= "WICustom"
; version 909 
rootDir		= "D\3\S"
; OPTIONAL
classes		= "Imaging devices"
driverCount	= 
decompSize	= 
compSize	= 

[E]
exc_count		= 1
; All tag files must exist or this will not execute!
exc_1_tagFiles	= 2
; Select a tag file that will only exist if the hardware was detected and the basic driver files were installed...
exc_1_tagFile1	= "%SystemRoot%\system32\Setup\escndvrs.dll"
; according to es3c.inf the target folder is "32" Layout.inf says that is system32\Setup (not confirmed don't have hardware)
;
; Make sure the setup file exists
exc_1_tagFile2	= "%DPSROOT%\D\S\E\Setup.exe"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
; If the HWID is not found in the inf(s) this will not execute!
exc_1_+infFiles	= 4
exc_1_+infFile1	= "%DPSROOT%\D\S\E\Es3c.inf"
exc_1_+infFile2	= "%DPSROOT%\D\S\E\Es4f.inf"
exc_1_+infFile3	= "%DPSROOT%\D\S\E\Es41.inf"
exc_1_+infFile4	= "%DPSROOT%\D\S\E\Es43.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 1
exc_1_command1  = "cmd.exe /c %DPSROOT%\D\S\E\Setup.exe"

or somthing close to that

make sure that you put your DriverPack_WICustom_wnt5_x86-32.ini
in the same folder as you have your \D\ folder
so that when it is extracted your D is written to the same folder as the DriverPacks D and your WICustom.ini is extracted to SystemDrive with the other DriverPacks ini files

D
DriverPack_WICustom_wnt5_x86-32.ini
  3
    S
      E
        infs
        all packed cab files
        setup.exe
        LIB and all subfolders it contains

observation;

There is no feedback from BASE during the time the site is unreachable
BASE does seem to be locked-up / frozen during this time.
None of the navigation keys respond
There is no cancel feature. or other option to abort.

I will be updating this section of the code ASAP

Let's Post a link here and make it an official RC (Release Candidate)

I was not able to find the latest changelog... but from my memory;

I belive it was updated because it was in french...
We always use the english versions with DriverPacks. (and provide language packs as a 3rd party DriverPack)
so the .CAT files and friends needed to be swapped out.
and i belive there were som minor fixes to the packs .INI

Link outdated - removed

I will investigate...