DriverPacks not supressing 'Driver Signature' or 'New Hardware Found'

We need more info than what you provided.
DPs_BASE.log
DPsFnshr.log
Please read the "Read before you post" link in my signature.
What you've asked is similar to "Why won't my car start".  Impossible to answer without more info.
Also, KTD is known to cause problems.  We prefer users begin using SAD instead.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Thanks for the prompt reply guys, left work now, but will post logs tomorrow.

However, in response to OverFlow, this is what I have done so far to make a Universal Image (and has work on 2 different Compaq's and a Dell) but if your suggesting a better, more optimised way I'm all for it.

1. Extracted appropriate files (BASE, DPsFnshr.ini, DPsFnshr.7Z and ROE) to desired folders.
2. Extracted all desired Driver Packs to C:\D (Apart from MassStorage as they are causing huge issues - see: http://forum.driverpacks.net/viewtopic.php?id=4359)
3. Ran C:\DevPath.exe C:\D
4. Added paths to KTD (paths:D\G;D\L etc) and KTDlocation = "%SystemRoot%\Options\Drivers" to DPsFnshr.ini
5. Added UpdateInstalledDrivers=Yes and DriverSigningPolicy=Ignore to sysprep.inf
6. Issued the command C:\sysprep\ROE.exe 937
7. Downloaded and ran the Vernalex SysPrep Driver Scanner which added a reg entry for everything in C:\D and C:\Windows\Inf
8. Added the line UpdateUPHAL="ACPIAPIC_MP,%WINDIR%\inf\hal.inf" to sysprep.inf
9. Ran the .bat:

@echo off
cd C:\SYSPREP

echo Enabling image for AMD and Intel processors
reg add "HKLM\SYSTEM\ControlSet001\Services\intelppm" /v Start /t REG_DWORD /d 4 /f

echo Running sysprep and shutting down.
sysprep.exe -forceshutdown -mini -reseal

The resulting image was then captured with WDS (Equalling 9GB). If your saying theres a better and easier way to achieve this, PLEASE PLEASE do tell, as I need to get this 'image' live for about 200 machines in the coming weeks.

I looked at this SAD thing you suggested, it seems interesting but I am a little lost - is what your saying; I can SCRAP all what I've done above and JUST extract everything to C:\D (Minus MassStorage) and simply have a scripted called "DP_Install_Tool.cmd" in the \$OEM$\$1\ of my WDS server, with the command DPInst.exe /c /s inside it?

Thanks,
Jack

Last edited by Jack_F (2010-02-11 21:05:39)

I am not sure about sysprep proceedure with OLSP... I defer to the crazy sysprepers of our forum

But regarding the driver installation...

1) You simply call sysprep.inf with dp_inst_tool.cmd being called under 'runonce'.
    SAD M2 is better than extracting and running devpath on C:\D because the drivers remain archived.
    This saves you around 1 gig on your image

    Notes: Your other method would work as long as you don't EVER use KTD.
    Simply running devpath on the c:\d\ folder was all that was needed.
    KTD was killing you. As previously stated do not run makepnf...
    KTD uses makepnf... Therefore you failed . (Because you inadvertently used makepnf)

or

2) You could combine devpath and dp install tool methods together.
    Create a SAD M1 folder
     -  Be sure to enable QSC so you won't have to cab compress a pack more than once.
        QSC (Quick Stream Cache) keeps a copy of the cabbed drivers for M1 slipstreams.
           (The first run is slow because they are cabbed with makecab.exe, after the first run they are simply copied.) 
    Copy everything from the driverpacks.net M1 folder to c:\
    Run devpath on C:\D
    Call dp_inst_tool.cmd under 'runonce'

this Hybrid method both makes the drivers available to minisetup and runs the dpinst.exe and the DriverPacks Finisher. Effectively making two passes on the machine to ensure drivers are fully installed. Some drivers require two passes. IE you cant install a HDA device unless the HDA bus driver is installed first. chipset drivers have to be installed before drivers that rely on chipset etc...

In many cases dpinst.exe works fine but some failures have been reported in the forum.

Please note that even though M1 will take a long time to run on your first time it will save you a huge amount of space over simply extracting them.

Definately use the mass storage pack! (as long as you don't use makepnf or KTD it will not crash!)

I hope that helps

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Well after having great feedback from Galapo on the 911 forums concerning OfflineSysPrep I went ahead and did as he advised, but having some issues, after I:

Upload image to WDS, boot into Network PXE, Loads WDS - Grabs and installs Image from WDS.

Reboots to continue as is all normal, get to the "Please wait for Windows to setup..." screen, gets past that, start to see Black Background with Mouse Pointer then PC just Shutdown.....

The steps taken, I'll summarise the thread over at 911:

1. Run DP_Base using the S.A.D option (Using Method 2 you suggested above), move ALL files created under DriverPacks.net to C:
2. Extracted and ran 'DevPath' to C: \D
3. Ran 'sysprep.exe -reseal -forceshutdown' (had a previously created sysprep.inf with [SysprepMassStorage] populated by -bmsd)
4. Sysprep runs, shutdowns VMWare - I boot into LiveXP with OfflineSysPrep script installed
5. Run OfflineSysPrep on the offline VMWare HDD, using Administrator Profile and Automatic HAL detection on First Boot.
6. Select the 'Mini', 'PnP' and set to Quit - Hit Reseal and it does its thing.
7. Shutdown LiveXP
8. Reboot VMWare into PXE and capature and upload to my WDS
9. Then the above error occurs... well not really an error, just Shutdown.

Please help oh mighty ones

You don't state whether you actually injected the DriverPacks mass storage drivers. Did you?

Regards,
Galapo.

These are the ones I'd be using:

Regards,
Galapo.

Bump - just at work waiting anxiously... Should I be leaving DriverPacks.net or moving everything into C:...

Last edited by Jack_F (2010-02-18 16:13:24)

Ah I love you haha. Thats sum everything up very nicely, once I get into work tomorrow I'll go ahead and do as you state - out of interest though, if I was wanting to call dp_inst_tool from my Sysprep, an acceptable entry in sysprep,inf would look like the below correct?

[GuiRunOnce]
Command0 = "C:\dp_inst_tool.cmd"

One last thing (I hope lol) - Galapo mentions that I should be doing the following as I want to include -bmsd within my Sysprep.inf and OfflineSysPrep doesn't allow that:

1. Set up DriverPacks, sysprep'ing with '-reseal -forceshutdown', rebooting the machine and letting DriverPacks install;
2. THEN booting into LiveXP, running OfflineSysPrep, injecting MassStorage drivers and sysprep'ing the machine for a second time with '-reseal -pnp -mini';
3. Then image, upload to WDS and away I go.

Does that seem correct? My thoughts are that if I let DriverPacks install (after the 1st Sysprep) that the system I will Image in the end is then ONLY setup for that type Hardware? Wouldn't it be better to only Sysprep once or Sysprep twice but don't let the machine bootup before an Image is taken? I'm a little confused on this last part.

Would the follow work/be a better option:

1. Set up DriverPacks, sysprep with '-reseal -forceshutdown'; [Meaning that I can use a NEW sysprep.inf with OfflineSysPrep so as not to have -bmsd content]
2. Boot into LiveXP, running OfflineSysPrep, injecting MassStorage drivers and sysprep the machine with '-reseal -pnp -mini';
3. Then image, upload to WDS and away I go.

I'm just trying to think, if I do that, how do I get my -bmsd MassStorage drivers included as OfflineSysPrep doesn't allow that....?

Cheers

Last edited by Jack_F (2010-02-18 22:51:24)