Search options (Page 47 of 77)

1) is already answred by Helmi

2) that depends: as long as YOU don't delete the files necessary for the Finisher, NOR the DriverPacks directory, then you can execute it at whatever time/order you prefer.

@FhM: since SP2, Windows XP ignores that setting...

And jtdoom is right: if you do it according to what I posted earlier, you might get a HUGE amount of Driver Signing Policy error dialogs - but if you only apply KTD on signed drivers you will get none...
So here's my updated guide:

Basically it's this:
1. Extract the DriverPacks to your PC, for example to %SystemRoot%\DriverPacks.
2.
a) Start closeDSP.exe:

closeDSP.exe

b) Execute makePNF.exe:

makePNF.exe %SystemRoot%\DriverPacks

c) End closeDSP.exe:

taskkill /f /im closeDSP.exe

3. Execute DevPath.exe:

DevPath.exe %SystemRoot%\DriverPacks

That's it.

@jtdoom: that's just an INTERNAL setting: it has read it from the settings file. You're the second one to make a remark about it, so I'll just change the log entry then.

@Ravennt: well... what can I do more than just start the setup with the correct switches? I can't control what the ATI CCP setup does, can I? If you do it manually, how much faster is it then? I have never measured the time required for that, so I don't know. I know it's always been working just fine though.

Yes indeed...

So why are you asking, McStarfighter?

@Helmi & midiboy: the version is still at 10.5.1.59 as far as I can see... But check this in the changelog:

So I guess it's safe to use them...

That's the tool I've used too to mod the drivers

It already was included, but some exotic additional driver files were not yet included, I have included them now: that will probably fix it. DriverPack WLAN 6.08 will do the trick for you!

The Russian translation must be updated. It's NOT invalid, it's just missing some new entries. That's all.

And your installation worked and did most definitely not hang according to your log:

2006-08-26 02:48:02 : <EXEC> Executing all commands (3) for exception [wnt5_x86-32__0002__D-G-A-1].
2006-08-26 02:48:02 : <EXEC>     Executing command 1 of 3: "%DPSROOT%\D\G\A\1\ATICCP.exe -y -o%DPSTMP%"
2006-08-26 02:48:05 : <EXEC>         No STDOUT output occurred.
2006-08-26 02:48:05 : <EXEC>     Executing command 2 of 3: "start /wait %DPSTMP%\Setup.exe /K"
2006-08-26 02:53:16 : <EXEC>         No STDOUT output occurred.
2006-08-26 02:53:16 : <EXEC>     Executing command 3 of 3: "rd /s /q %DPSTMP%"
2006-08-26 02:53:16 : <EXEC>         No STDOUT output occurred.
2006-08-26 02:53:16 : <EXEC> No exceptions left to execute: none have met all requirements!

Of course it 'lags', simply because it must take the time necessary to install the CCP!

Basically it's this:
1. Extract the DriverPacks to your PC, for example to %SystemRoot%\DriverPacks.
2. Execute makePNF.exe:

makePNF.exe %SystemRoot%\DriverPacks

3. Execute DevPath.exe:

DevPath.exe %SystemRoot%\DriverPacks

That's it.

It didn't take long at all, DigeratiPrime Are you using the latest DriverPack Sound B? (6.08.6) There was a bug in the older versions.

P.S.: the DriverPacks Finisher has a built-in HWID logger

You should use the DriverPack Sound B 6.08.6, not 6.06. But I think you ARE but that you just mistyped it.

Please post your DPs_BASE.log.

I will need your DPs_BASE.log and in particular, your DPsFnshr.log!