Topic: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

This is my problem:

I nLite a clean XP Pro version and subsequently run DPs_BASE to integrate the driver packs.

When I fire the result up in VMWare (or a real machine), I get the error message: 'Windows cannot find 'd:\OEM\WatchDriverSigningPolicy.exe' instead of seeing the driverpacks extract.

When I slipstream the DriverPacks onto a clean XP version, everything works fine, and the drivers are properly extracted and installed, so, at first I figured this might be nLite related rather than DP_BASE related. Now, I'm not so sure anymore.

It seems to me that presetup.cmd is either not being invoked at all or not finding the proper files.

winnt.sif, presetup.cmd, et.al. all look OK to me (though I am a noob at this...), so I thought something might be wrong in the setup.exe area. I followed Pyron's instructions, but with no apparent success.

I have managed once to slipstream an nLited version that would extract and install the drivers. This version did not include any hotfixes, but was otherwise identical to all other attempts. When I compare the successful attempts (i.e. on nLite w/o hotfixes and on untouched original XP) with the multitude of failed attempts, the only difference I can find in the files that I believe to be relevant is in setupORG.exe. In the successful attempts, it is 23.040 bytes and in the others 5.120 bytes. Afaik this file is generated by DPs_BASE. winnt.sif, presetup.cmd and cmdlines.txt are identical, as are the OEM and $OEM$ folders. Replacing the smaller setupORG.exe file with the larger one does not change anything.

Nobody else seems to experience this, so I must be missing something fundamental. But what?

Any help will be received with gratitude.

Cheers!

Log:

2007-12-27 03:56:18 : <INIT> DriverPacks BASE 7.05.2 initialized.
2007-12-27 03:56:18 : <INIT> Host environment: WIN_XP Service Pack 3, v.3244 on X86 CPU.
2007-12-27 03:56:18 : <INIT> Created temporary working directory.
2007-12-27 03:56:18 : <INIT> Imported proxy settings from Internet Explorer.
2007-12-27 03:56:18 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack Chipset 7.10.1!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack CPU 7.04.1!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack Graphics A 7.10!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack Graphics B 7.12.1!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack Graphics C 7.12!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack LAN 7.12!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack LAN 7.12.1!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack MassStorage 7.12!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack Sound A 7.12!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack Sound B 7.12!
2007-12-27 03:56:18 : <INIT> 	Detected DriverPack WLAN 7.12!
2007-12-27 03:56:18 : <INIT> 	Detected 3rd party DriverPack(s).
2007-12-27 03:56:18 : <INIT> 	Finished scanning.
2007-12-27 03:56:18 : <INIT> Detected settings file "C:\XPDP\DPs_BASE.ini".
2007-12-27 03:56:19 : <INIT> Windows XP Professional -  Retail SP2 detected.
2007-12-27 03:56:19 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-12-27 03:56:19 : <INIT> Imported settings from settings file.
2007-12-27 03:56:19 : <GUI>  Initialized GUI.
2007-12-27 03:56:19 : <GUI>  Created a list of all available language files.
2007-12-27 03:56:19 : <GUI>  Set the last used language, English, as the GUI language.
2007-12-27 03:57:07 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to C:\XPCD.
2007-12-27 03:57:07 : <GUI>  Windows XP Professional -  Retail SP2 detected.
2007-12-27 03:57:07 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-12-27 04:06:33 : <GUI>  Saved settings!
2007-12-27 04:06:33 : <GUI>  Closed GUI.
2007-12-27 04:06:33 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2007-12-27 04:06:33 : <PREP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2007-12-27 04:06:34 : <PREP> Removed all attributes from \I386.
2007-12-27 04:06:35 : <PREP> Created a backup of \I386\winnt.sif.
2007-12-27 04:06:35 : <PREP> Created a backup of \I386\txtsetup.sif.
2007-12-27 04:06:35 : <PREP> Created a backup of \I386\dosnet.inf.
2007-12-27 04:06:35 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2007-12-27 04:06:35 : <SLIP> Created necessary directory structure for method 2.
2007-12-27 04:06:35 : <SLIP> Copied files necessary for method 2.
2007-12-27 04:06:35 : <SLIP> Extracted files necessary for method 2.
2007-12-27 04:06:35 : <SLIP> Created \I386\presetup.cmd file.
2007-12-27 04:06:35 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2007-12-27 04:06:36 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2007-12-27 04:06:58 : <SLIP> Copied DriverPacks to \OEM.
2007-12-27 04:06:58 : <SLIP> Extracted and deleted \I386\svcpack.in_.
2007-12-27 04:06:58 : <SLIP> Updated \I386\svcpack.inf file to support KB888111 and KB921401.
2007-12-27 04:06:59 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2007-12-27 04:07:01 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2007-12-27 04:07:01 : <SLIP> Updated \I386\dosnet.inf file to support KB921401.
2007-12-27 04:07:04 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2007-12-27 04:07:08 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2007-12-27 04:07:08 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2007-12-27 04:07:39 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2007-12-27 04:07:39 : <SLIP> Updated \I386\winnt.sif to support method 2.
2007-12-27 04:07:39 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2007-12-27 04:07:39 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2007-12-27 04:07:39 : <SLIP> Slipstream finished in 1 minutes and 6 seconds.
2007-12-27 04:07:48 : <CLNP> Temporary working directory successfully deleted.
2007-12-27 04:07:48 : Program terminated.


.ini

[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	= "disc"
; trailing backslash is allowed, but not necessary
location	= "C:\XPCD"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "all"
; 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		= "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl		= "CCP"

Last edited by MarioS (2007-12-28 00:57:56)

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

I don't think that OverFlow is done writing the Service Pack 3 compatability.  You may need to use a nightly build to even attempt it.

~TigerC10~

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

Welcome to Driverpacks - We are glad your here!

@Tiger his "HOST" OS is winXP sp3 - however his source is SP2 so that will not affect him...

WatchDriverSigningPolicy.exe is not a driverpacks file... ?
What PYRON instructions are you refering to?
the OEM folder is an exclusively DriverPacks folder so you must be making changes after you run DriverPacks

you must be doing somthing with nLite or manually to cause this.
the best advise i can give you is make sure you are running driverpacks LAST in your disk creation process.

To reiterate you cannot make ANY changes after you run driverpacks if you do it will most likely fail to operate correctly.
Run driverpacks base followed imediately by creating the ISO image.

Thanks for including your logs it makes it much easier to help you!

PS please use code tags...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

OverFlow wrote:

Welcome to Driverpacks - We are glad your here!

@Tiger his "HOST" OS is winXP sp3 - however his source is SP2 so that will not affect him...

WatchDriverSigningPolicy.exe is not a driverpacks file... ?
What PYRON instructions are you refering to?
the OEM folder is an exclusively DriverPacks folder so you must be making changes after you run DriverPacks

1. Glad to be here!

2. Don't know if WatchDriverSigningPolicy.exe is a driverpacks file or not. Can't see it, but DSPdsblr.exe includes it's functionality of creating the registry hooks allowing unsigned drivers to be installed.

3. Afaik Pyron came up with the general approach used by driverpacks, i.e. changing the setup to invoke presetup.cmd before "setup.exe -newsetup". presetup.cmd then identifies the CD drive and calls on the functions in \OEM\bin to extract the drivers etc. His post here covers this in some detail, and DP uses his setup.ex_, DevPath.exe and his approach for presetup.cmd.

Somewhere here is where it is going wrong in the non-working attempts. Even if some function of DP would be looking for WatchDriverSigningPolicy.exe, it should, afaik, only do this after the extraction of the DriverPacks, and the extraction never happens in these cases. I get the error message instead.

4. I'm not touching the OEM folder and it is identical in the working and non-working attempts.

OverFlow wrote:

you must be doing somthing with nLite or manually to cause this.
the best advise i can give you is make sure you are running driverpacks LAST in your disk creation process.

5. Doing nothing with nLite, except installing hotfixes. Doing nothing manually.

6. Good advice, but already adhered to. DriverPacks are run last in the creation process and they are run with exactly the same settings for the working and the non-working attempts. In both cases, DP produces identical presetup.cmd, winnt.sif and cmdlines.txt files. I have no idea why it generates a different setupORG.exe and what else is different.

OverFlow wrote:

To reiterate you cannot make ANY changes after you run driverpacks if you do it will most likely fail to operate correctly.
Run driverpacks base followed imediately by creating the ISO image.

7. Yep, as noted above already sticking to that.


Cheers!

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

Just a few more notes:

1. As noted above, it should not matter that I run this on a machine with SP3, but just in case I have also run this on a different machine with a new clean install of SP2 with the same results (and also inside a Virtual Machine on SP2).

2. I have also re-downloaded and re-installed all software and DP's to exclude some strange file corruption as the cause of this.

This is what is so strange. I appear to be experiencing something unique that nobody else has a problem with and still I can repeat it in different hard- and software/OS environments.

Bugs me to no end, this does...

Cheers!

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

SOLVED!

Turns out all this was caused by a bug in brain.exe...

Some idiot (ooops...) by mistake included "ENU_Addons_M2OEM-Drivers_v150907.rar" among the hotfixes and addons. Apparently, nLite extracts and executes this with the result that presetup.cm_ is created together with a modified setup.ex_ and an \i386\OEM directory. When DPs_BASE comes along to do it's thing, it's too late and the previous changes retain precedence.

Apologies for taking your time with this, but it really had me stumped for quite a while.

Cheers!

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

well ther is no wonder you are haveing trouble...

the instructions you were useing were written Dec 21 2003, 08:38 AM  those are no longer useful except as a historical (or was that hysterical) review of where we started. Much has changed since 2003. Heck much has changed since 2007.

Please only use the directions you recieve here and you wont be led down the wrong path.


where in the heck did you get ENU_Addons_M2OEM-Drivers_v150907.rar ?

Glad you were able to remove the "meat virus" from your ISO.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

OverFlow wrote:

well ther is no wonder you are haveing trouble...

the instructions you were useing were written Dec 21 2003, 08:38 AM  those are no longer useful except as a historical (or was that hysterical) review of where we started. Much has changed since 2003. Heck much has changed since 2007.

Just used them for "debugging". For this they were quite helpful since in essence DriverPacks still works like that.

OverFlow wrote:

where in the heck did you get ENU_Addons_M2OEM-Drivers_v150907.rar ?

From here. Been playing around with it for grabbing drivers off my computers, and must have placed a copy of it in the addons folder by mistake...

Thanks for all your help and input!


Cheers!

Re: [SOLVED] nLite + DriverPacks => Windows cannot find 'd:\OEM\WatchDr

yes the method itself is still very much alive although it has evolved over time.

the addon is based on the original Pyron code and may see a facelift if you were to point it out to the author.
it may also be worth noting in that thread that it may not be used with the driverpacks in its current form.
although with a little tweaking it might be able to coexist... however the driverpacks are quite complete and i would like to think that if we were missing some drivers they would show up here and request them (we like that).

I can see how this tool would be very useful if you intended to make a disk only to be used on a specific type of PC.

Thanks for your input. it was enlightening for me as well.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.