[Pyron]

Yes.

--
Pyron

[bilemke]

Sweet, thanks for the minor, but very usefull changes Pyron!!

Now that it is possible to resolve the little issue with setup.exe not being original, I am going to finish finding where the info in unnattend.sif gets called in to play during setup.. Then try to get that same info there without having the .sif file in txtsetup mode.

My goal is still to have a unnattended wtihout the use of a unnattended config file.

[Pyron]

*After* the last reset? At that point all drivers should be installed already (well, most of them).
I assume you are installing exe-only drivers like from ATI or Creative, so you can tune Windows' behaviour by changing these registry keys:

REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Driver Signing]
"Policy"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing]
"Policy"=hex:00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing]
"BehaviorOnFailedVerify"=dword:00000000

Just import a regfile before installation, that should help. Windows won't bother anymore when you install unsigned drivers. But I would recommend setting these keys back to their original values after you are finished.

--
Pyron

[big_gie]

@Pyron:
Great tool that SetDevicePath.exe!!

I'm using a tool of mine, mt39, to execute multiple programs from winnt.sif's DetachedProgram. With this, I extract each of 7zip compressed (not sfx) archive containing my drivers. That way its easier to maintain drivers (one archive for each driver):

mt39's config file said:

<?xml version="1.0" encoding="ISO-8859-2" standalone="no"?>
<mt39 version="0.8.1" testingmode="0" logging="1">
<item>
  <!-- nVidia video card's driver -->
  <program>%SourceDrive%\Programmes\7zip\7z.exe</program>
  <arguments>x -y -o"%systemdrive%\setup\drivers\nvidia" "%SourceDrive%\Programmes\drivers\nvidia.7z"</arguments>
  <hide>1</hide>
  <wait>300</wait>
</item>
  <!-- Scanner's driver -->
  <program>%SourceDrive%\Programmes\7zip\7z.exe</program>
  <arguments>x -y -o"%systemdrive%\setup\drivers\scanner" "%SourceDrive%\Programmes\drivers\scanner.7z"</arguments>
  <hide>1</hide>
  <wait>300</wait>
</item>
<item>
  <!-- dbmsmbus's driver -->
  <program>%SourceDrive%\Programmes\7zip\7z.exe</program>
  <arguments>x -y -o"%systemdrive%\setup\drivers\dd4550\dbmsmbus" "%SourceDrive%\Programmes\drivers\dd4550\dbmsmbus.7z"</arguments>
  <hide>1</hide>
  <wait>300</wait>
</item>
...

Right now, I need to include the OemPnPDriversPath in my winnt.sif to point to each of the folder:

   OemPnPDriversPath="setup\drivers\nvidia;setup\drivers\dd4550\dbmsmbus;setup\drivers\dd4550\ecran;setup\drivers\dd4550\gameport;setup\drivers\dd4550\hp845c;setup\drivers\dd4550\lan;setup\drivers\dd4550\sound"

As suggested by Bilou_Gateux on this thread, running SetDevicePath.exe from this could prevent from using the winnt.sif's OemPnPDriversPath section.

What I did was to add this:

<item>
  <program>%SourceDrive%\Programmes\drivers\devpath.exe</program>
  <arguments>%systemdrive%\setup\drivers</arguments>
  <hide>1</hide>
  <wait>300</wait>
	</item>

to mt39's config file and commented the OemPnPDriversPath section. But it didn't worked

There is surely no registry @ t-39 so its surely impossible to edit it... So using this tool from there can't be done...

Does anyone think that editing $winnt$.inf could do it? Or maybe any other way to tell windows to go find its drivers to a certain path (@ t-39, not latter...), without specifiying them in winnt.sif?

thanx

[edmoncu]

hey pyron, just wanna say congratulations!

everything worked well now with xpsp2 with your updated setup.exe! cool!!!

[Pyron]

@edmoncu:
Thanks!

@big_gie:
Well, there definitely is a rudimentary registry at t-39, because I usually add my RunOnceEx Keys before starting the setup and also use SetServicePath.exe at that point. Technically it is even before t-39, since the countdown starts with the setup. Although I cannot tell where your problem exactly lies, I don't think it has anything to do with the registry.
EDIT: I assume you renamed the program, so that
<program>%SourceDrive%\Programmes\drivers\devpath.exe</program>
is not a typo?
--
Pyron

[big_gie]

No its not a typo, I renamed the program

Thanx for the clarification on the registry...

[big_gie]

Does anyone used SetDevicePath.exe @ t-39 succesfully? I'm still looking for a correct way of using it...

[serialzs]

big_gie, on Aug 21 2004, 08:29 AM, said:

Does anyone used SetDevicePath.exe @ t-39 succesfully? I'm still looking for a correct way of using it...

@big_gie

this is the correct way...
SetDevicePath.exe %cdrom%\Drivers

the 1st part is SetDevicePath.exe is for command for your REGISTRY

and the 2nd part is %cdrom%\Drivers is for the folder were you put the drivers files...

to test it if its working...
1. Run REGEDIT
2. goto HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion dont close REGEDIT... remember what data is in DevicePath key...
3. execute the SetDevicePath.exe with the Drivers folder path.
(eg. SetDevicePath.exe D:\drivers)
4. go back to REGEDIT then then press F5 to Refresh Registry, look @ DevicePath
if it add the Drivers Folder Path on DevicePath Key then it works good...


-=[serialzs]=-

[big_gie]

Yes thats what I did during my unattended installation.
I extracted my drivers (since they are compressed on the cdrom) to C:\setup\drivers. I then called, at t-39 (winnt.sif's DetachedProgram) SetDevicePath.exe C:\setup\drivers but my drivers aren't installed (I checked in the device manager and got plenty of small yellow "!").

Thats why I wanted to see if somebody else did the same as me but successfully...

[serialzs]

@big_gie

can i see what you put in your winnt.sif...
i wanna help you.. i will try it out...
and what kind of file compression are you using???


@Pyron

why i can't execute a compiled autoit file in your presetup.cmd???
i test and modify it many times but no luck...

-=[serialzs]=-

[big_gie]

serialz said:

can i see what you put in your winnt.sif...

[Unattended]
;OemPnPDriversPath="setup\drivers\nvidia;..."
DriverSigningPolicy=Ignore

[GuiUnattended]
DetachedProgram="%systemdrive%\setup\mt39.exe"
Arguments="/xml:%systemdrive%\setup\dd4550u.xml:/xml"

mt39 is a tool of mine to execute multiple program.

mt39 then extract 7zip compressed archieve:

dd4550u.xml said:

...
<item>
  <!-- nVidia video card's driver -->
  <program>%SourceDrive%\Programmes\7zip\7z.exe</program>
  <arguments>x -y -o"%systemdrive%\setup\drivers\nvidia" "%SourceDrive%\Programmes\drivers\nvidia.7z"</arguments>
  <hide>1</hide>
  <wait>300</wait>
</item>
<item>
  <!-- Scanner's driver -->
  <program>%SourceDrive%\Programmes\7zip\7z.exe</program>
  <arguments>x -y -o"%systemdrive%\setup\drivers\scanner" "%SourceDrive%\Programmes\drivers\scanner.7z"</arguments>
  <hide>1</hide>
  <wait>300</wait>
</item>
...

And then run devpath.exe (renamed SetDevicePath.exe):

dd4550u.xml said:

...
<item>
  <!-- Add OEM drivers' location to registry -->
  <program>%SourceDrive%\Programmes\drivers\devpath.exe</program>
  <arguments>%systemdrive%\setup\drivers</arguments>
  <hide>1</hide>
  <wait>300</wait>
</item>

But after trying this it didn't worked. Its quite hard to test since drivers can't be tested in a virtual machine, except the vmware/virtualpc svga drivers...
I'll try to make some testing with them...

Thanx for helping

[serialzs]

@big_gie

Arguments="/xml:%systemdrive%\setup\dd4550u.xml:/xml"

what is this for???

i test it with no arguments and "logging" = 0 and "testingmode" = 0...
it woks great to me...

QUESTION:
did you test it to run this program in presetup.cmd???
is it working???

-=[serialzs]=-

[big_gie]

Quote

Arguments="/xml:%systemdrive%\setup\dd4550u.xml:/xml"

what is this for???

%systemdrive%\setup\dd4550u.xml is the mt39's xml config file. It contains programs to execute.

Quote

did you test it to run this program in presetup.cmd???
is it working???

No, I don't use batch files.


So your telling me that you were able to remove the winnt.sif's OemDriverPath, execute SetDriverPath.exe (with whatever technic) @ t-39 and that your drivers were installed?? Testing this in a vmware wont work as your drivers aren't needed in a virtual machine (it could be tested with vmware's svga drivers though).

[Pyron]

@serialzs:
The startup environment is very limited, maybe compiled autoit-scripts just don't work there, I didn't test it however. Running Autoit.exe with an uncompiled script does work, I am using this technique in my unattended installs.

--
Pyron

[serialzs]

@big_gie

i did'nt test it in vmware or MS Virtual PC... i test it in my PC...
vmware or MS Virtual PC have a different hardware, even you run it in your PC...
thats why it does'nt install the unattended drivers...

@pyron

thanks for your reply...


-=[serialzs]=-

[BennyC]

bilemke, on Aug 4 2004, 06:19 PM, said:

@ovilla2001

I am looking for what makes the call to setup.exe... The special something that would normally call the stock setup.exe, and make it run a different file name. That way we never have to rename setup.exe to begin with.

Isn't it in "HKLM\SYSTEM\Setup\cmdline" in the rudimentary registry installed by text-mode setup?

BTW renaming setup.exe does work, and here's why: windows maps the executables it runs to memory, very similar to the way CreateFileMapping works. At that point, it doesnt care much for the filename anymore, just the raw blocks on the filesystem. Renaming should not be a problem, but moving to another filesystem will not work. Deleting should work on UNIX, because that OS only frees data blocks once all filehandles to it are closed. Not on Windows however.

[edmoncu]

@pyron: i plan on doing this method but instead from the CD, the drivers are compressed and be extracted on the target partition... anyways, with the new scheme used in presetup.cmd with regards to xpsp2, i am curious, may i see your entire presetup.cmd file? i just have to make sure where to place the file-renaming portion used by presetup.cmd. thanks.