Search options (Page 34 of 77)

Sorry, have read it too fast. That's correct, the directory structure should be \$OEM\$1\D\M.

You still need the DriverPacks Finisher for the cleanup of the drivers, unless you do that in your own scripts.

I will try to reproduce this issue.

Huh? The D directory is in your \$OEM$ directory instead of the \$OEM\$1 directory??? Please move it to the \$OEM$\$1 directory!

Are you sure you did not accidentally do this yourself? It would amaze me if no one else had reported this behaviour before, if it were caused by the DriverPack Sound B.

Just make a tiny 3rd party DriverPack with just this driver in it. (Do not forget to creat AT LEAST the 'D' directory though! )

That explains alot.

Please remove the compact command. It's completely useless: the %systemdrive%\D directory is only used for temporary storage of the DriverPacks. If you don't use KTD, all DriverPacks are simply deleted, if you do use KTD, then you should apply this command on the directory specified in the KTDlocation entry of your DPsFnshr.ini. I will add this functionality in one of the next versions of the DriverPacks Finisher anyway, by the way

That only leaves one of the two issues:

I've fixed that in the current nightly already!

It's a workaround for duplicate filenames. For example:

ati3112r.sy_ and si3112r.sy_ are in decompressed state both named si3112r.sys, but you cannot include two files with identical filenames in one directory when you use Windows. That's the one and only reason

I've been doing this for more than a year now, and I've yet to encounter the first issue with this workaround, so in case you're wondering, yes, this is reliable.

Yep, that's fine. Then it must be my mistake. Will try to reproduce this.

You must slipstream KB883667 to circumvent this. This only happens only for certain Windows XP SP2 installation discs. After you've slipstreamed the aforementioned hotfix, the popup will vanish.

You can disable it now, yes.

Ok, so it's actually two issues:

1) the DevicePath value is not cleaned up if you've used method 2

2) KTD is applied incorrectly, though it does work (aesthetical & pragmatic flaw)

Could you please post the Settings section of your DPsFnshr.ini?

No it is not. Please post your export of the following registry value:

HKLM\Software\Microsoft\Windows\CurrenvtVersion\DevicePath

to verify that it's similar there.

As far as I can tell, you have not yet slipstreamed the DriverPacks yet.

- your DPs_BASE.ini is in its original state, with no settings from you
- the same for your DPsFnshr.ini (that would have been configured by the DriverPack Sound B if you had slipstreamed the DriverPacks)
- your DPs_BASE.log just shows that you've started the DriverPack Sound B, not that you've slipstreamed the DriverPacks.