[erik_demon]

Okay, thanks

I will give it a try

[Bâshrat the Sneaky]

@RogueSpear: thanks, then I'll do that.

[erik_demon]

I just tried it, and it didn't work .

This is what I tried:

winnt.sif

[GuiUnattended]
      DetachedProgram = "%SYSTEMDRIVE%\D\drivers.cmd"

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

driver.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:

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.

EDIT:

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

[RogueSpear]

First, I've never used a directory as my tag file in determining the source CD letter. I don't know if this is causing a problem or not but I would suggest setting the tag file to the file WIN51.

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.

[erik_demon]

@RogueSpear

Thanks for your reply

Quote

First, I've never used a directory as my tag file in determining the source CD letter. I don't know if this is causing a problem or not but I would suggest setting the tag file to the file WIN51.

This works, I've done it many times now.

Quote

I think you could and probably shoud keep the WatchDriverSigningPolicy.exe in your presetup.cmd

Thanks, I will change this!

Quote

but I think the BTS DPs are designed so that the various batch files expect to find the DPs as %SYSYEMDRIVE%\D

Bashrat changed this in his pack. (This only works if you make the choice to keep the driver (a special option in his batch).

Quote

Ok and in looking carefully here you are putting driver.cmd in %SYSTEMDRIVE%\D but the DPs themselves decompress to "%SystemRoot%\BtS_DriverPacks.

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

[Bâshrat the Sneaky]

DOH You guys wanted to 'hide' the DriverPacks folder from the end-user. So far this is only possible with M2. (And of course only enabled when using KtD)

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.

[billgbuds]

The gui run once section is missing the command to install the control panels now. It worked on the previous base pack.

[Bâshrat the Sneaky]

I know, I'm working on a new version.

[X-Savior]

Hey,

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!

[Bâshrat the Sneaky]

It seem there's a problem with unsigned drivers. Anyone having problems with those drivers too?

[kingofthing]

Windows XP Service Pack2 (Manual Integration)
+ RyanVM's Hotfixes v1.21 (Manual Integration)
+Method 2 + Keep the Drivers
+All driverpacks
problems...

ABIT BE6-II

hpt366 not working
DUS NOT SEE DRIVE

[X-Savior]

Hey There,

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.

Next...

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?

[erik_demon]

@X-Savior

Yes, the way it is used now, and the way it is implanted in Bashrat's pack works fine.

I tested it on my WLAN card, and two onboard devices and it worked great (all installed without a window popping-up)

[Bâshrat the Sneaky]

@X-Savior: eh... the SATARAID drivers just work fine for the SATALINK devices too That's why I excluded the SATALINK drivers, when I included them it gave problems with RAID setups!

[X-Savior]

@Bashrat

Interesting. Wasn't sure if it was on purpose or not. No Big Deal.

@Erik

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.

[Bâshrat the Sneaky]

It seems several users of my DriverPacks have reported that, when SetupCopyOEMInf.exe is doing its job, alot of annoying 'not WHQL signed warnings' pop up. I found a way to easily circumvent this:

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 )

[Acheron]

This method works

Here's the AutoIt script I use at detached programs stage:

Winnt.sif

[GuiUnattended]
    DetachedProgram=autoit3.exe
    Arguments="%systemroot%\System32\presetup.au3"

PreSetup.au3

$CD = DriveGetDrive("CDROM")
For $I=1 to Number($CD[0])
    $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.

[Bâshrat the Sneaky]

Interesting, didn't think that it would work at that stage

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?

[Acheron]

Currently I'm in testing phase. Approximately 10 drivers will be installed. (Around 15 MB compressed). However I thought everybody was using this method prior setup (using the fake setup launcher) or during detached program period. On what time do you run the SetupCopyOEMInf.exe tool?

[mark49]

M3 ,with high prior ,maybe can extract all driver to hd in time before system go to next step to install device ...?