Search options (Page 139 of 213)

well a google search revealed warm-snows application... that is not supported by DriverPacks you will need to post in that thread for him...

I, incorrectly, believed your question was DriverPacks related...
IE how to run DriverPacks automaticaly...

but You are NOT useing DriverPacks since warm snows application is a third party app   
we don't support third party software ...

by providing good details and the info from Read BEFORE you post in my signature you can avoid confusion.
always provide DriverPacks BASE version and a GOOD (through) description of your situation...
IE waht you are experienceing or waht you are try to accomplish...

Sweet!

Thanks again!

if you would use the search feature... (That is how I find references)

gui=no in the ini will automate the install...
if you can't get that far on your own...
you probably don't need to be automateing your install...

can we ahve a link to the driver that did work for you?

\

man... you are kicking um... arse and taking names lol...

REwritable disks can be unreliable... if you are useing one...

there are known issues with updateding MCE with SP3
- it is not recomended...
last i heard the better method was to slipstream updates to a sp2 source
this avoids several packages being corupted / downgraded in MCE 

best of luck and thanks for reporting

moved... ect...

now your getting it... ding the light bulb comes on... ;p

by useing iniRead() you will also get better access to the data (similar to your reading the file into an array)
in fact i frequently import an entire ini (or inf) section into an array. for the same reason...

you may also find that Fedit.exe (in the DriverPacks bin folder) is even better at inf manipulation   IE
this line uses Fedit because with the -once switch fedit will only add the line ONCE in the entire section
(so if it exists already it doesnt get added again )  PS seems like you could use this for sysprep output
_runDos(@scriptDir & "\bin\Fedit.exe -add -once -f """ & $_I386 & "\dosnet.inf"" -s Files -l d1,setupORG.exe")
and some other nice features that are not native to autoit ini functions...

We have a handful of dedicated team members who do the packs, allowing me to focus my free time on the base code...

I rarely need to update the packs unless there is a problem that is unresolved...
i used to do the mass storage pack because it is / was one of the most difficult to understand.
several of the team are now well experienced with that now too...

I have not used it yet but i will be very interested in the output of your tool for sysprep,
as i intend to add sysprep as a platform, so seeing what is known to work will be most helpful.

we are quite lucky to have such a team in place
It really makes me appreceate how hard Bâshrat the Sneaky worked when it was just him...

no we cant rename teh infs it breaks driver signing... same for ide.inf
i assume the one ide driver is seperate because it is included with a signed chipset driver...

it is probably also a replaceme3nt driver
(meaning you dont want it for sysprep = conflict with existing driver)