[ Closed ] Integrate DP in already installed Windows

Hi.
do you want to read how great tools missed a final ingredient?
to read what you no longer have to do, but learn something about how it is done: read on.
------------

KTD AFTER installing..
Like for a hardware testbed..
That's been asked before.
The batchfile was rewritten, and the topic that was in is discussing other stuff as well, so..

Here is the batchfile

It takes little work.
Just make the batch, put it in the folder you integrated with method 2, et viola.

NOTE.. THE BATCH ONLY REQUIRES THE OEM FOLDER AND WHAT'S IN IT..

The batch that does what KTD does is called doPNF because that's what KTD did.

doPNF.cmd

SET TAGFILE=\OEM\BIN\un7zip.exe
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:
 
%CDDRIVE%\OEM\BIN\un7zip.exe %CDDRIVE%\OEM\BIN\DP*.7z "%SystemDrive%\dump"
%CDDRIVE%\OEM\BIN\un7zip.exe %CDDRIVE%\OEM\DP*.7z "%SystemRoot%\DriverPacks"
start %SystemDrive%\dump\Mute.exe on
start %SystemDrive%\dump\DSPdsblr.exe
%SystemDrive%\dump\makePNF.exe "%SystemRoot%\DriverPacks"
%CDDRIVE%\OEM\BIN\DevPath.exe "%SystemRoot%\DriverPacks"
taskkill /f /im DSPdsblr.exe
%SystemDrive%\dump\Mute.exe off
RD /Q /S %SystemDrive%\dump
exit

Now, on a vanilla install, one of the problems you could come across is that no exceptions are used, and some control panels will not be installed.
------------------------

The following one was written to run Finisher, and it does KTD too.

I called it FINI.cmd

SET TAGFILE=\OEM\BIN\un7zip.exe
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:
 
%CDDRIVE%\OEM\BIN\un7zip.exe %CDDRIVE%\OEM\BIN\DP*.7z "%SystemDrive%\"
%CDDRIVE%\OEM\BIN\un7zip.exe %CDDRIVE%\OEM\DP*.7z "%SystemRoot%\DriverPacks"
start %SystemDrive%\Mute.exe on
start %SystemDrive%\DSPdsblr.exe
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
xcopy %SystemRoot%\Driverpacks\*.* %SystemDrive%\ /y /i /e /h
start %SystemDrive%\DPsFnshr.exe
%SystemDrive%\makePNF.exe %SystemRoot%\DriverPacks
%CDDRIVE%\OEM\BIN\DevPath.exe %SystemRoot%\DriverPacks
taskkill /f /im DSPdsblr.exe
%SystemDrive%\Mute.exe off

exit

you will see an xcopy is made that gets deleted when finisher cleans up.
This copy is made so that the finisher can work, and the drivers will still be on the drive for later use.

-----------------------------
Now, not everybody needs KTD (makePNF and devpath, etc.) along with a POST-INSTALL-FINISHER session.

When I wrote FINI.CMD, I assumed that the source was not slipstreamed with KTD selected.

A POST install Finisher without KTD looks like this.

NoKTD.cmd

SET TAGFILE=\OEM\BIN\un7zip.exe
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:
 
%CDDRIVE%\OEM\BIN\un7zip.exe %CDDRIVE%\OEM\BIN\DP*.7z "%SystemDrive%\"
%CDDRIVE%\OEM\BIN\un7zip.exe %CDDRIVE%\OEM\DP*.7z "%SystemDrive%\"
COPY /Y %CDDRIVE%\OEM\bin\DPsFnshr.ini %SystemDrive%\
start %SystemDrive%\Mute.exe on
start %SystemDrive%\DSPdsblr.exe
start %SystemDrive%\DPsFnshr.exe
taskkill /f /im DSPdsblr.exe
%SystemDrive%\Mute.exe off

exit

NOTE; this could be used with a source that has KTD, and that would then do KTD for you.

------------------

Save the batchfile you wish like this.
Copy, and paste into notepad >> then "save as".
Select ALL FILE TYPES (so that it does not automagically adds TXT as extention..)
Save as fini.cmd (or whatever name you wish, as long as you stick to the 8.3 format.)
Voila, you have the batchfile, ready to use.

You can put this on a new burn, along with the slipstreamed source (you have to use method two), or, you burn only the OEM folder and all that's in it plus the batchfile(s) to a CDR.

(some folks do not have a DVDrom reader in their machine, and even when one collects all packs, this will still fit on a CDR...)

This will still not do all the work for you, tho.
I hope that one of these days a method will be found to make Windows run a minisetup style hardware detection after installing windows has already finished.
I already read articles and am sure sysprep users know these articles as well.

--------------------

And LAST, I must at least mention this.
I read Quite a few guys slipstream a source with all packs and some third party packs, and use method 1.
They do not use it to run setup.
They use the content of $OEM$ folder as their collection of drivers.

Last edited by Jaak (2008-04-21 16:44:55)

Dumping a KTD on an already installed Windows wouldn't be much use to me. I'd much rather have an executable like DP_BASE scan my hardware and perform all upgrades.

KTD would be a poor testbed because it would be rarely used. The way I want it would be an excellent testbed since it would get used all the time.

For example, say a DP install crashes. The solution is to install from a non DP enhanced media and install all the drivers after Windows gets up and running. The end result would be exactly the same and hopefully the malfunctioning driver would be easy to identify.

Driverpacks is too good to limit it to new installs from custom media.

Last edited by severach (2007-08-20 10:50:04)

Here's what I have done so far by following your posts:

SET TAGFILE=\\RISSERVER\MSI\Driverpacks.net
SET LOCATION=\\RISSERVER\REMINST\SETUP\ENGLISH\IMAGES\WINDOWSXP\$OEM$\$1

%TAGFILE%\BIN\un7zip.exe %TAGFILE%\Driverpacks\DP*.7z "%SystemDrive%\"

COPY /Y %LOCATION%\DPsFnshr.ini %SystemDrive%\
start %LOCATION%\Mute.exe on
start %LOCATION%\DSPdsblr.exe
start %LOCATION%\DPsFnshr.exe
taskkill /f /im DSPdsblr.exe
%LOCATION%\Mute.exe off

exit

I'm using DP with my RIS installs, however I'm trying to make a driver pack finisher that will install updated drivers on computers that will not install through PXE (I have to use a CD for these). My variables point to the location of the needed apps, and %LOCATION% points to the OEM directory of one of my images that I have slipstreamed with DP_Base. I have ran this script, and from what I can tell it extracted all the drivers to the hard drive of the computer I ran the script on (good) but once it ran the finisher it deleted them all without updating the drivers on the actual machine. Is there a setting that I'm missing or a line that isn't in my script?

DPs_BASE.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    = "E:\RemoteInstall\Setup\English\Images\WINDOWSXP"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks    = "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod    = "1"
; 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"

; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset    = "yes"
DP_Graphics_A    = "yes"
DP_Graphics_B    = "yes"
DP_LAN        = "yes"
DP_Sound_A    = "yes"
DP_Sound_B    = "yes"
DP_MassStorage_textmode = "no"

; 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"

/aol on

me too!

/aol off

Seriously, has anyone done any recent work on these batch files?

This forum is for adding driverpacks after the installation
IE it was installed without driverpacks KTD and we wish to upgrade it.

WHY? what a silly thing to do...  " i want KTD so i disabled it " [and now it doesnt work - DUH!]

Did you read Jaaks post???

you are trying to manually duplicate this process needlessly since the DP base already provides teh functionality you want and why should we help you when we have provided a simple way to get the result you desire.

If you are able to get something useful working by all means let us know. If it doesnt work it's not much help is it?

since you are installing clean you can just enable KTD from base and your done. 

it's that simple.  please post in the appropriate threads.

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!.

KTD=false will remove your drivers when finisher runs. Since you did not rerun windows setup it wont update existing devices in your machine you have to do that by hand.

i dont' know how many times i have to say this the DriverPacks Finisher DOES NOT INSTALL DRIVERS. - - - PERIOD!

it adds SOFTWARE to PREVIOUSLY INSTALLED drivers (like control panel files or raid management GUI, ect... things that are normaly installed by running an executable installer program)

example i run an install without the driverpacks on a machine that has an ATI card
it gets added to device manager as a standard VGA card
i run a KTD script like above and run the finisher since the ati card is not installed the finisher will not install the ATI control panel and why should it since there is not ATI card in the system per device manager???

Do you see why this cannot work???

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!.

jaak checkout benjamminzIS other thread i found the problem its in sound b can we get that in the nightly...

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!.