[larciel]

yeah i played with nlite

i'm going to make one from clean install

[a06lp]

try a real cd, without using nlite. let me know what happens.

[a06lp]

@Everyone:

Well, I performed two more real-world tests, and thought I'd share:
1) Following all my steps from my post, but leaving my "drivers" folder empty (to see whether the drivers were really being installed, or happened to be WinXP default drivers)
Result: Drivers did not install. (That's good. This shows that the drivers, when placed in the "drivers" folder, actually DO install, as shown in the test immediatly below.)
2) Followed all my steps (as written)
Result: Drivers did install.

Once again, this is more proof that the method works. 3 fully operational trials proves this very well for me.

[Cunning1inguist]

After adding this driver pack (extracted to c:\Drivers and running your installation method, my windows installation hangs on 12min (registering components)

Should I only include the drivers specific to my hardware, or is it okay to use the full driver pack at once?

[Bâshrat the Sneaky]

Cunning1inguist, on Jan 23 2005, 10:54 PM, said:

After adding this driver pack (extracted to c:\Drivers and running your installation method, my windows installation hangs on 12min (registering components)

Should I only include the drivers specific to my hardware, or is it okay to use the full driver pack at once?

Of course you can add as many drivers as you want!

[Cunning1inguist]

Cunning1inguist, on Jan 23 2005, 02:54 PM, said:

After adding this driver pack (extracted to c:\Drivers and running your installation method, my windows installation hangs on 12min (registering components)

Should I only include the drivers specific to my hardware, or is it okay to use the full driver pack at once?

I figured out what I did wrong. I set the wrong path for the drivers in the presetup.cmd

[Amel]

Hi All! Thanks Pyron and all others for this method
But it should be remembered that You can write your own Setup.exe (a.k.a. ile5 ) using Autoit! Simple convert "setup.au3" to "setup.exe"

RunWait ("CMD /C PreSetup.cmd")
RunWait (@SystemDir & "\Setup.exe " & $CmdLineRaw)

The good idea is converting all PreSetup.cmd cmds to Setup.au3, and may be use space after finishing original Windows setup process (i.e. resetting DevicePath). In my opinion this method is more flexible, but require additional compile step after each modification of Setup.au3. And it WORK with SVCPACK.INF! Look in attach my result of converting...

COMMENT: I use other locations of files, correct it for Your! (i.e. $oem$ instead OEM). And it not full tested, only in my needs... And this method require some modifications to a06lp steps - Leave out all entries about PreSetup.cmd file

Attached File(s)

•  Setup.au3 (4.38K)
  Number of downloads: 91

[Bâshrat the Sneaky]

Interesting post

I'll investigate this more

[a06lp]

Amel, on Jan 23 2005, 11:34 PM, said:

...You can write your own Setup.exe (a.k.a. ile5  ) using Autoit! Simple convert "setup.au3" to "setup.exe"
...And this method require some modifications to a06lp steps - Leave out all entries about PreSetup.cmd file

ah, but of course. as soon as i 'finish' explaining my mixture-method, and get it working great, this comes up...

I tried to make my guide real simple and step-by-step so that even most beginners can do it. I'm afraid that autoit (as easy as it is) may be an extra step that will confuse things.

I will wait to hear more from Bâshrat the Sneaky, but for now I'm sticking with my method.

[Amel]

@a06lp:
My first post is unpretentious and not in opposite to others methods - full tested and work fine...

My main causes is:
1. Verify guess of ile5 about SVCPACK.INF (and it's ok!)
2. Perhaps return control of runing original windows setup.exe as before in Pyron method (from presetup.cmd)

...and second cause - reduce modifications in original distributive (ideally - replace only one file setup.ex_) by means of integrating some functions in one .exe file (since every so often I miss smth. ). On the other hand CMD-file is the same script a.k.a. AUT-script, but with different language, and IMHO not easier...

@everyone:
ATTENTION: .AU3 --> .EXE (ver.3) scripts work fine in setup mode in Windows 2000 (my preffered OS), but exit with error in my Windows XP setup process. Windows XP PREVENT from executing AutoIt3 scripts in setup mode!

The system cannot execute the specified program

Fortunately .AUT --> .EXE (ver.2.x AutoIt) work in Windows XP as well. In attach this version of script...

Attached File(s)

•  setup.aut.rar (1010bytes)
  Number of downloads: 59

[Amel]

One non-muted line in WINNT.SIF in the following quote resulting that
WatchDriverSigningPolicy.exe NOT work (I test it in XP SP1 & SP2)

[Unattended]
;DriverSigningPolicy=Ignore
 NonDriverSigningPolicy=Ignore

This metod require muting BOTH lines in WINNT.SIF

[Unattended]
;DriverSigningPolicy=Ignore
;NonDriverSigningPolicy=Ignore

P.S. Same problem discuss in this thread
http://www.msfn.org/board/index.php?showto...ersigningpolicy

[andy_le2k]

I followed all the steps and i got a BSOD with "SESSION3_INITIALIZATION_FAILED"
any ideas? I got it right after the setup enters the blue setup screen and starts loading some drivers right where it says "Setup is loading windows" or something like that.

[Bâshrat the Sneaky]

andy_le2k, on Feb 11 2005, 03:00 AM, said:

I followed all the steps and i got a BSOD with "SESSION3_INITIALIZATION_FAILED"
any ideas? I got it right after the setup enters the blue setup screen and starts loading some drivers right where it says "Setup is loading windows" or something like that.

Which drivers did you add? Try again without any drivers, just to verify it isn't cause by the method itself.

[Amel]

Perhaps, I realize my goals, posted above... Now, I only replace ONE file (setup.ex_) in distributive!
Main AutoIt (setup.exe) script install all necessary files to temporary folder (%SystemDrive%\Unattend), run its and delete this folder at the end of setup.

If interesting, look my files in attach... Unpack its to new folder, and before run Compile!.cmd:
- Copy here two files from AutoIt (v.2.64) installation (Aut2Exe.exe, AutoItSC.Bin)
- Copy here expanded Setup.exe from Windows distributive and rename it to setupORG.exe
- Copy here Pyrons SetDevicePath.exe

I slightly modify Pyrons WatchDriverSigningPolicy.exe in order that it restore policy settings (and DevicePath) and exit immediately before end of setup process (and before saving registry by System). For this purpose I use SystemSetupInProgress parameter of "HKLM\SYSTEM\Setup" Key. Then, %Home% folder may be deleted...

P.S. I am not cool programmer and so posted VC++ source code... It base on code, earlier posted by Pyron (Thx!)

Attached File(s)

•  AUT_Pack.rar (29.21K)
  Number of downloads: 78
•  ccpSource.rar (1.14K)
  Number of downloads: 73

[gilesw]

I'm going to use the detached program method. I just wanted to know why it's necessary to pack the drivepacks as console expanding .exe's . Why can't 7za.exe be used to extract the driver packs in their original form off the cd and onto the hard disk. The detached program is a batch file with the commands. Is it something to do with the /wait command ?

thanks,

g.

[j4ever]

so am i supposed to leave the end of presetup.cmd like this:

REM +=======================================================+
REM | Finally start the installation with the originally |
REM | given parameters |
REM |-------------------------------------------------------|
start /WAIT setup.exe %*
REM +=======================================================+



REM +=======================================================+
REM | Cleanup |
RD /Q /S %SystemDrive%\drivers
REM | Reset DevicePath |
REM +=======================================================+

[Bâshrat the Sneaky]

About that last one: if you want the folder %SystemDrive%\drivers to be deleted, yes.

(it seems you have already removed the DevicePath reset code...)

P.S.: use code tags next time, please!

[RogueSpear]

@gilesw Here is a batch file that I call from DetachedProgram.

@ECHO OFF
set tagfile=\WIN51
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:

%SystemDrive%
cd \
Start /WAIT %CDDRIVE%\OEM\7za.exe x -y -aoa %CDDRIVE%\OEM\Drivers.7z -o"%SYSTEMDRIVE%\D"
Start /WAIT %CDDRIVE%\OEM\7za.exe x -y -aoa %CDDRIVE%\OEM\ProgFiles.7z -o"%PROGRAMFILES%"
Start /WAIT %CDDRIVE%\OEM\7za.exe x -y -aoa %CDDRIVE%\OEM\Sys32.7z -o"%SYSTEMROOT%\System32"
Copy %CDDRIVE%\OEM\7za.exe "%SYSTEMROOT%\System32\7za.exe"

Edit: I am actually using Method 1 for my drivers. I just modify the routine a little bit as you can see.

[gret]

hey...
this is great...

i have a question, though...
wat if i just want to go through the regular setup process but after the reboot, i want it to copy off the cd instead of trying to copy from the hard drive.

in short, i still want the winnt.sif file, but i just want the OEMPreinstall=No

is it possible?

[Bâshrat the Sneaky]

Of course, gret, that's even easier

Just use this code:

@ECHO OFF
set tagfile=\WIN51
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:

This code scans for a tagfile (which you can change of course) and then appends the var %CDDRIVE% to the drive in which the cd is located. Note that you can continue to use this variable in this batch file only!

The copy/install commands should be added by you, of course