Unlimited number of drivers + keeping the drivers. Exception: MassStorage drivers.
Posted 24 April 2005 - 08:34 AM
This is what I tried:
[GuiUnattended] † † †DetachedProgram = "%SYSTEMDRIVE%\D\drivers.cmd"
SET tagfile=\WINXP\OEM 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 z) do if exist "%%i:%tagfile%" set CDDRIVE=%%i: CD /D %SystemRoot%\system32 CD /D %SystemDrive% %CDDRIVE%\WINXP\OEM\bin\7za.exe x -y -aoa %CDDRIVE%\WINXP\OEM\DriverPack_*.7z -o"%SystemRoot%\BtS_DriverPacks\" EXIT
SET tagfile=\WINXP\OEM 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 z) do if exist "%%i:%tagfile%" set CDDRIVE=%%i: START /WAIT %CDDRIVE%\WINXP\OEM\bin\SetupCopyOEMInf.exe %SystemRoot%\BtS_DriverPacks\D START %CDDRIVE%\WINXP\OEM\bin\WatchDriverSigningPolicy.exe EXIT
The file driver.cmd is in my $OEM$\$1\D folder
I never used DetachedProgram before so maybe I made a mistake.
In never saw the SetupCopyOEMInf.exe during setup.
Don't pay attention to the fact that I use WINXP multiple times. I install from a second harddrive, and the folder WINXP can be seen as the root of my CD.
This post has been edited by erik_demon: 24 April 2005 - 08:49 AM
Posted 24 April 2005 - 08:48 AM
Second, while I am not totally versed in everything Method 2 I think you could and probably shoud keep the WatchDriverSigningPolicy.exe in your presetup.cmd file. I think the way this works is that it will stay resident and running when executed from presetup.cmd, but I'm not so sure it will do that if executed from DetachedProgram.
Third, I don't know if this will make a difference for sure, but I think the BTS DPs are designed so that the various batch files expect to find the DPs as %SYSYEMDRIVE%\D. You've nested D inside another directory. Again, I don't know for sure if this will make a difference or not, but you may as well eliminate any potential problems right off the bat.
Ok and in looking carefully here you are putting driver.cmd in %SYSTEMDRIVE%\D but the DPs themselves decompress to "%SystemRoot%\BtS_DriverPacks.
Suggestion: decompress all DPs to %SYSTEMDRIVE% and put your drivers.cmd file inside $OEM$\$1 in your install media. Make the appropriate changes to your presetup.cmd and drivers.cmd files.
Posted 24 April 2005 - 09:02 AM
Thanks for your reply
Thanks, I will change this!
Yes, I did this on purpose. I can't delete the %SystemRoot%\BtS_DriverPacks folder because I want to preserve the drivers. I can however delete the %systemdrive%\D folder (which also has the control panels batch inside)
I will try to put everything on the %SYSTEMDRIVE%. I don't have any time to test some more today. But I will try it soon.
Thanks for all your help
Posted 24 April 2005 - 01:34 PM
That's why I changed the default folder for M2+KtD from %SystemDrive%\D to %SystemRoot%\BtS_DriverPacks\D. But now you're talking about the control panels, I realize that the CPL batch file will have to be updated as well! DOH
I'll set it to the old default folder for now.
Posted 29 April 2005 - 03:46 PM
Well, I can see there are both Pro's and Cons. for both Methods. I will see how the results turn out on this and see if it is worth all the extra work to integrate it. Like I said, simplicity is ALWAYS the best course of action. The More Complicated, the problems can arise.
But I must say everyone is doing some VERY fine work!
I Commend all of you for all the hard work!
Posted 02 May 2005 - 07:06 PM
I would do the Traditional Mass Storage Method. It works great and it is not a big deal for space. I am not familiar with that driver, but I know Bashrat forgot to include the SI3112 SATA-Link and SI3114 SATA-Link drivers. He had the RAID but not the regular ones. I made the addition for my DVD.
I know you dont NEED the drivers for OS install but it leaves the Drivers outstanding after. This way ALL drivers are installed during detection.
Ok, Do we actually have a WORKING Method here yet? I havn't started experimenting with it yet. Anyone with Success or is the method still in it's development stages?
Posted 04 May 2005 - 04:58 PM
Interesting. Wasn't sure if it was on purpose or not. No Big Deal.
Great. Well, if I get some time I might start experimenting with it. I like the idea. Is it more difficult to setup and organize or is it Straight-Forward? I havn't been following too closely on the method.
Posted 05 May 2005 - 02:26 AM
START %DPDIR%\WatchDriverSigningPolicy.exe START /WAIT %DPDIR%\SetupCopyOEMInf.exe %DPDIR% TASKKILL /F /IM WatchDriverSigninPolicy.exe
That is: using WatchDriverSigninPolicy.exe to get rid of them! (Thanks again, Pyron )
Posted 08 May 2005 - 01:59 PM
Here's the AutoIt script I use at detached programs stage:
[GuiUnattended] DetachedProgram=autoit3.exe Arguments="%systemroot%\System32\presetup.au3"
$CD = DriveGetDrive("CDROM") For $I=1 to Number($CD) $pa = $CD[$I] & "\win51ip.SP2" If FileExists($pa) Then $instDrv=$CD[$I] Endif Next ProcessSetPriority ( "setup.exe", 0) Run(@SystemDir & "\WatchDriverSigningPolicy.exe") ProcessWait("WatchDriverSigningPolicy.exe") RunWait(@SystemDir & "\SetupCopyOEMInf.exe " & $instDrv & "\Drivers") ProcessClose("WatchDriverSigningPolicy.exe") ProcessSetPriority ( "setup.exe", 2) FileDelete(@SystemDir & "\presetup.au3") FileDelete(@SystemDir & "\WatchDriverSigningPolicy.exe") FileDelete(@SystemDir & "\SetupCopyOEMInf.exe")
It's also compatible with the Driver Compressor Tool.
Posted 08 May 2005 - 02:13 PM
But unfortunately unusable for my DriverPacks - they would not yet be extracted at that stage... unless you use method 2 or method 1.
May I ask on how many drivers (the number of .inf files) you're applying this? And how many megabytes?
Posted 08 May 2005 - 03:02 PM