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.
