[Bâshrat the Sneaky]

Are you saying this?


I think he wants to say this:

Excuse me for my bad English, don't pay attention to my mistakes.

I like the DriverPacks and I want them to load from a DVD with several OSes.
Should I create a new boot folder after integrating the DriverPacks?


If this is what you wanted to say, please copy/paste it in one of the DriverPack topics, this topic only concerns a METHOD, not the DriverPacks!

[fc.dobriy]

Sorry

[Thauzar]

@evilvoice

Everything works great man!!! thank you so much. Thus I now have a valid alternative to svcpack.inf And for Ryan's driver pack, well it's sad but I was not planning on using them anyway.

[yanghaijun]

When i start the windows 2000 setup from CDROM, the presetup.cmd and the svcpack.inf can works verywell, but when i boot to dos, and run setup from dos command line, like this : winnt /s:e:\i386, the svcpack.inf can't works, why?

I want to install the cat File manually, what should i do?

[Muschi]

You can also start presetup.cmd @T13 Setup Stage.

winnt.sif

[GuiUnattended]
DetachedProgram = ".\system32\cmd.exe"
Arguments="/C START /MIN FOR %I IN (D: E: F: G: H:) DO (IF EXIST %I\$OEM$\Setup\Presetup.CMD (%I\$OEM$\Setup\Presetup.CMD) ELSE (FOR /D %J IN (%I\*) DO (IF EXIST %J\$OEM$\Setup\Presetup.CMD (%J\$OEM$\Setup\Presetup.CMD))))"

presetup.cmd

REM Hide cmd Window
@cmdow @ /HID

[ile5]

Hi
I think i found (after one day digging) what is Problem with "svcpack won't run" in Pyron's method.
OPENED "presetup.cmd" window (hide or not) is main TroubleMaker.
Obviously windows "setup.exe" don't like "*.cmd" window opened in back.

For testing i made setup.exe (in Delphi) with next process:

1. Open "presetup.cmd" and wait for close.
--- In "presetup.cmd" above "Setup.exe" is renamed to "setupold.exe".
--- "Setuporg.exe" is renamed to "setup.exe".
--- Other stuff....
--- Exit "presetup.cmd".

2. Open original "setup.exe -newsetup" ex. "Setuporg.exe" and wait for close.

I tested this file and every time svcpack run normaly.

----------------------------------------------------------------------------------------------

I don't know how to parameter passing to original "setup.exe" so i put default " -newsetup"

Pyron's method is fantastic, simple and multipurpose and this problem stop my almost finish unattended CD.
I also use Bâshrat the Sneaky's Method_2 for lan & sound drivers which also use this Pyron's method.

@Pyron maybe you change your "setup.exe" and test this method. (maybe i am totaly wrong)

svcpack_fix.zip include:

1. setup.ex_ ---------- Normal version - hidden "presetup.cmd" window.
2. setup_dbg.ex_ ---- Debug version - open "presetup.cmd" window.(If you want use this version rename file in "setup.ex_")
3. presetup.cmd ------ I slightly change this file at the end.


Good luck and sorry for bad english.

iLE

Attached File(s)

•  svcpack_fix3.zip (49.77K)
  Number of downloads: 156

This post has been edited by ile5: 07 November 2004 - 08:58 PM

[Thauzar]

@ile5 TESTED AND PROVEN WORKING!!! Wow man, thanks a lot, appart from doing another setup.exe (which I don't have the competences for), I really tried everything else to make it work. I knew something that stupid was preventing svcpack.inf from running, and you found it out in one day! GREAT! Now if pyron can replace the 1st post with the new files, this thread can now be recommanded as a proven method that works perfectly

[evilvoice]

only problem is -newsetup is now hardcoded...instead of being able to pass commands through presetup.cmd

[ile5]

Command Parameter(s) is not hardcoded anymore !
In the new version command parameter(s) pass to the Original setup.exe.
This version is more error verbose in pre setup stage.
Feel free to test this version and post any problem.

svcpack_fix3.zip include:

1. setup.ex_ ----------- Normal version - hidden "presetup.cmd" window.
2. setup_dbg.ex_ ---- Debug version - opened "presetup.cmd" window.
--------------------------- (If you want to use this version rename file in "setup.ex_")
3. presetup.cmd ------ IMPORTANT - I slightly change this file at the end.
--------------------------- (Delete line "start /WAIT setup.exe %*" in your "presetup.cmd" it is not needed anymore.)


iLE

Attached File(s)

•  svcpack_fix3.zip (49.77K)
  Number of downloads: 217

This post has been edited by ile5: 04 November 2004 - 06:17 PM

[jquintino]

this fix is only for 2k?

[jquintino]

if i use your methodo my installation just reboot at -t39

there is a problem and i dont now here?

[new_user]

@ile5

I tried to use your svcpack_fix3.zip in my UA XP CD together with

RyanVM Windows XP SP2 Update Pack: 04-Nov-2004 EDIT: 1.0.3
http://www.msfn.org/...showtopic=29536

and

Bâshrat the Sneaky's DriverPacks Method 2
http://www.msfn.org/...showtopic=30190

- DriverPacks BASE - version: 4.10.2
- DriverPack LAN - version: 4.10.3
- DriverPack MassStorage - version: 4.10
- DriverPack Sound - topic - version: 4.10.1

By the way @Bâshrat the Sneaky
in your presetup.cmd (contained in Driver BasePack) the /F parameter is missing here:
[CODE]
REM +=======================================================+
REM | Reset DriverPolicy |
REM |-------------------------------------------------------|
reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1 /F
reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1 /F
reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01 /F
REM +=======================================================+
Otherwise setup displayed and sits at a blue background forever!
Because the "Reg add" command waits for a "y" input (you can't see this in the batch)


@ile5
I get the following error messages:
1. "Pesetup.cmd" file is missing ! Try to continue normal setup ?
2. setupORG.exe file is missing, Setup Abort!

But your presetup.cmd is still there in the i386 folder of the UA XP CD
(see message screens)
Any tip ???

Thanks in advance

[ile5]

@jquintino

Quote

this fix is only for 2k?

Not only for win 2k!

1. This is not my method just a "setup.exe" (Pyron's method).
2. I don't know in your case is it windows setup begin and then restart at t-39 or
setup not even begin.

@new_user

1.
For test try to put this three files in the same directory:
- setup.exe,presetup.cmd,SetupORG.exe
("SetupORG.exe" is renamed original windows "setup.exe")
Edit presetup.cmd and leave only this:

presetup.cmd:

if exist setup.exe ren setup.exe setupold.exe
if exist setupORG.exe ren setupORG.exe setup.exe
exit

Execute "setup.exe".

If "windows Xp Setup" window is pop up with "Please go to Control Panel..."
everything is fine because setup is started without parameter.

2.
Check your "Txtsetup.sif" in i386 folder
Txtsetup.sif:

.
.
.
[SourceDisksFiles]

setupORG.exe = 1,,,,,,,2,0,0 ; must exist
presetup.cmd = 1,,,,,,,2,0,0 ; must exist
.
.
.

3.setup.ex_, setupORG.exe, presetup.cmd - must be in i386 folder on your xp cd.

iLE

[new_user]

@ile5

Thank you for the detailed guide! It works now!
I did not notice the this before !

[SourceDisksFiles]
setupORG.exe = 1,,,,,,,2,0,0; must exist
presetup.cmd = 1,,,,,,,2,0,0; must exist
.
.

There is another error message in presetup.cmd
(see my attached file)
But i will find it by my self
Good to have your setup_dbg.ex_ Debug version - open "presetup.cmd"

Thank for your help.

new_user

Attached File(s)

•  persetup_err2.JPG (53.8K)
  Number of downloads: 287

[new_user]

@ile5

I come a small step further, I could solve the problem
"Windows cannot find 'e:\OEM\bin\WatchDriverSigningPolicy.exe'
In your prestup.cmd included in svcpack_fix3.zip there is the following line:

REM +=======================================================+
REM | Enable installation of unsigned drivers               |
REM |-------------------------------------------------------|
start %CDDRIVE%\OEM\bin\WatchDriverSigningPolicy.exe
REM +=======================================================+

The "start" Command ??? I removed it now setup continues here.
Now the SetDevicePath.exe could not be found. (see image)
But the file is still the on CD-ROM in \OEM\bin !
I cannot understand it ???
For assistance I would be grateful

Thanks in advance

Attached File(s)

•  svcpack_fix3_err2.JPG (49.81K)
  Number of downloads: 220

[Phoenyx]

Pyron and excessively understood in the subject, if will be able to follow and to give its opinions on this in case that, related to the new SETUP.EXE, I am very grateful.
http://www.msfn.org/board/index.php?showto...ndpost&p=230642

PS: Sorry my bad english.

[a06lp]

ok, so after making a successful UCD, I decided to make it better by running everything from the CD, and not copying anything (besides what i MUST) to the harddrive.

i am a little afraid to try this "drivers from cd" installation...

right now I accomplish my driver installation by using this code (in winnt.sif):

[Unattended]
OemPnPDriversPath="Drivers\001_LAN;Drivers\002_display;Drivers\003_modem;
Drivers\004_audio\SMAXWDM\W2K_XP;Drivers\005_sound\SMAXWDM\W2K_XP;
Drivers\006_infared;Drivers\007_SD;Drivers\008_wifi\Setup;
Drivers\008_wifi\Setup\I8500;Drivers\unidenwlan"

and all my drivers are in: XPCD\$OEM$\$1\Drivers

so...I have some q's:

1) If I follow the steps in the first post by Pyron (Major Update 12. Sep 2004); steps 1-7 - will this be EVERYTHING I need to do? or have issues been brought up/problems/etc.

2) Does this interfere at all with RyanVM's Update pack 1.03?

3) In step2, he says to "create a directory OEM\bin in the root of your CD-folder". Is this the same thing as the $OEM$ folder I already have there? Or is it different?

3a) If it's different, do I have to call it OEM\bin? can i call it anything i want?

4) is there anything else i should know about..?

[Bâshrat the Sneaky]

a06lp, on Dec 9 2004, 03:45 AM, said:

so...I have some q's:

1) If I follow the steps in the first post by Pyron (Major Update
12. Sep 2004); steps 1-7 - will this be EVERYTHING I need to do?  or have issues been brought up/problems/etc.

2) Does this interfere at all with RyanVM's Update pack 1.03?

3) In step2, he says to "create a directory OEM\bin in the root of your CD-folder".  Is this the same thing as the $OEM$ folder I already have there?  Or is it different?

3a) If it's different, do I have to call it OEM\bin?  can i call it anything i want?

4) is there anything else i should know about..?

1) Yes it's everything.

2) I don't think so...

3) It's different from the $OEM$ folder

3a) Maybe you could name it something else, but then you'd have to change several files, so I'd stick with OEM

4) You don't have to add the OemPnPDriversPath to your winnt.sif!!!!!

[tkoc]

hi i am sitting here and thinking can i use this metode to connect to a network drive and get the driver from there

from
Kenneth Foli Jørgensen

[a06lp]

Pyron, on Dec 21 2003, 10:38 AM, said:

Things to do after the installation:
Microsoft recommends to reset the DevicePath to "%SystemRoot%\Inf" after setup:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]
"DevicePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
  00,74,00,25,00,5c,00,49,00,6e,00,66,00,00,00

If you used WatchDriverSigningPolicy.exe, you should reset the appropriate keys if you don't want unsigned drivers to be installed without warning:

REGEDIT4

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

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

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

(Apparently this does not work at the end of presetup.cmd after the invocation of setup.exe. It seems that Windows is in some weird limbo state there and registry-changes are ignored/reset.)

Final notes:
Please note that you cannot start all programs in presetup.cmd.
The environment is rather limited at this point of the setup.
regedit.exe for example does not work, but reg.exe does.
taskmgr.exe does not work either. They will work a minute later, when the real setup has started.
rundll32.exe works so you can install custom infs.
WinRAR-sfx-archives only work with consolemode-sfx-module, 7z-sfx archives work out of the box. (figured out by edmoncu here)
BTW, things added to RunOnce will be executed somewhere at mark 34min, parallel to the driver installation.
RunOnceEx gets executed at mark 13min, as usual.

You can also use AutoIt to automate the installation in case you don't want to use winnt.sif. (for a repair cd)

My old version of setup.exe started GUI-setup automatically after presetup.cmd had finished, this new one does not! You have to do it youself at the end of presetup.cmd. This way you can do stuff after setup as well, like cleanup.
This version of setup.exe forwards its parameters to presetup.cmd. This means that you should start the installation like this:

setup.exe %*

(thanks, Biggles, for the shorter version) in case Windows wants to do some special stuff, like ASR (Automated System Recovery). This was mentioned by ovilla2001 here, although he reported the repair option failed, I just assume he meant ASR. (AFAIK "-newsetup" is used by normal and repair setup, only the entries in $winnt.inf$ change)
SetupORG.exe must be renamed to setup.exe before installation to resolve a bad signature issue reported by ovilla2001 here, look into the example presetup.cmd to see how this is to be done.

I don't understand this whole "Things to do after the installation" section.

I followed steps 1-7. (I have my "OEM" folder with "bin" and "drivers", i extracted my "setup.ex_" to "setuporg.exe" and i replaced the "setup.ex_" with the one in the first post, added "presetup.cmd" to i386, and edited "TXTSETUP.sif")
do i still need to do more?

can someone help me out? Do i need to do these 'extra' things? - specifically the registry entries about driversigningpolicy or something?
and what's all this about not starting GUI-setup? is that just explaining why the line "setup.exe %*" is there?

please help me!

Also, the first post says "Major Update 12. Sep 2004 (finally!)" - this should be UPDATED since I went back and read through this huge post (everything since sept. 12 2004), and found that many things suggested had already been incorperated into the first post - at least add a line or two mentioning when the FIRST POST was LAST UPDATED, so I can see what NEW errors there are and know which ones have been SOLVED (for example, the whole "setup.exe %*" code line, as opposed to the %1, %2, etc.).
Right now, I have no idea about the info on the last 2-3 pages of this post - all the stuff by ile5: is that incorperated into the first post?
All this stuff about RyanVM's packs not working - has that been resolved? Because I use his pack (1.04), and must be able to have it run!

@ile5
I noticed you have the line

REM | Reset DevicePath   
REM |-------------------------------------------------------|
REG ADD %KEY%\999 /V 1 /D "%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemRoot%\Inf" /f
REM +=======================================================+

in your presetup.cmd - do i need that in mine? i got my presetup.cmd from the first page of this huge post.