Drivers from CD and WINNT.SIF method?

[Nucleus]

Is it possible to use the %CDROM% variable in WINNT.SIF?

I want to use the WINNT.SIF method for installing drivers, but I don't want them copied over to my hard disk. So if I could use the %CDROM% variable in WINNT.SIF (something like this)

OemPnPDriversPath="%CDROM%\Drivers\001_wpcibridge;%CDROM%\Drivers\002_wsmbus;%CDROM%\Drivers\003_wpcimem;%CDROM%\Drivers\004_wusbserial;%CDROM%\Drivers\005_haudio;%CDROM%\Drivers\006_waudio;%CDROM%\Drivers\007_hwebcam;%CDROM%\Drivers\008_wradiotv"

Then I could do what I want.

Thanks.

Edited December 15, 2005 by Nucleus

[RogueSpear]

Actually I think what might get you the results you're looking for would be to use SetDevicePath.exe in conjuction with DetachedProgram. Have DetachedProgram call a batch file named Drivers.cmd which could like like this:

SET TAGFILE=\WIN51IP.SP2
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:
%CDDRIVE%\D\SetDevicePath.exe %CDDRIVE%\D
START %CDDRIVE%\D\WatchDriverSigningPolicy.exe
EXIT

This assumes that on your CD/DVD the drivers are all within a subdirectory called "D" and that you place SetDevicePath.exe and WatchDriverSigningPolicy.exe in the same subdirectory. I forget what the exact registry key is, but SetDevicePath.exe populates it with the path to your drivers. And there is a limit to length which it can be, which is why I named it "D" instead of "Drivers".

[Nucleus]

Ok, I didn't fully understand this but let me tell you my thoughts.

DetachedProgram.exe can be used in WINNT.SIF for running a batch file. Correct? What if that batch file, creates the %CROM% variable by simply executing this line:

FOR %%i IN (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:\WIN51IP.SP2 SET CDROM=%%i:

and WINNT.SIF just uses it, like this:

OemPnPDriversPath="%CDROM%\Drivers\001_wpcibridge;%CDROM%\Drivers\002_wsmbus;%CDROM%\Drivers\003_wpcimem.

No, SetDevicePath.exe, no WatchDriverSigningPolicy.exe, nothing. Just DetachedProgram.exe to be able to run the batch file, and that's it.

Why do we need SetDevicePath.exe, and WatchDriverSigningPolicy.exe anyway? Windows can detect and install the proper drivers, once told the folder they are in. Right? I don't know if I'm thinking this the right way, I don't really know how the whole driver thing works.

I just need to be able to use the %CDROM% enviroment variable in WINNT.SIF :-/

Edited December 15, 2005 by Nucleus

[RogueSpear]

I think that OemPnPDriverPath is hard coded to look inside $OEM$\$1\UserDefined. They issue here being that $OEM$\$1 obviously translates to your hard disk, not the CD. It may not do this however, give it a whirl, but I think that's the case. SetDevicePath.exe populates the registry, as I stated earlier, with the path to your drivers. Windows looks here for your drivers.

If you have Advanced Registry Tracer or RegShot, try running it against a subdirectory and you'll get the proper reg key and see what it does.

[CMan]

Any news on this idea?

I like the idea of not using SetDevicePath.exe cause I want to make my install as fast as possible and waiting for the computer to recursively scan all the drivers from all the BTS Driverpacks takes too long.

So can you set a cdrom path in the OemPnPDriversPath variable?