Macster, on Nov 28 2008, 11:05 PM, said:
Now for another matter, is there some way to add a user developed script to the WinSetupFromUSB program so as to include other files and folders outside of the usual &OEM&, COMPONENTS, I386, etc., etc; that the program (WinSetupFromUSB) uses to make the bootable USB? Because I am having a problem of knowing when the $WIN_NT$.~LS renames to WIN_NT.LS and back again. This tends to make for messy scripts to try to compensate and impossible in certain conditions like when I have multiple reboots to install drivers and access scripts from the USB, during the GUI (user account phase, I don't know what this is called but it would be during the RunOnceEx phase). Cause I have noticed that this folder ($WIN_NT$.~LS) changes at certain times during the install and has broken my scripts on a number of occasions. Anyway the only cure I see is being able to add this user generated script so that other folders and/or files can be added to the bootable USB on an alternate directory that is outside of the usual directories (like $WIN_NT$.~LS and $WIN_NT$.~BS) that is created on the bootable USB.
Hi,
Have a look at this post, it's a summary what actually is happening:
http://www.msfn.org/board/index.php?showto...st&p=797585
~BT and ~LS folders are renamed at T-9, the last possible place before end of GUI mode. They are renamed back upon first login.
You can put any script, using the various options you have BEFORE SetupParams (T-9), when ~LS/~BT names are intact. You may also add your script or launch it by ren_fold.cmd, before the renaming occurs. Or use presetup.cmd if that early stage suits you.
If you need to launch a script during first logon, you can add it to undoren.cmd or make it launch by the same, after the renaming part in it.
In all scripts USB drive letter is already found for you.
http://unattended.ms...xp/view/web/13/
If I add our stuff, the timeline would look like:
»Text-mode Setup
1. Loads Drivers
2. Copies files required for Setup to the Hard Disk
3. Copies the contents of your $OEM$ folders to the Hard Disk <--- this is done by presetup.cmd because we have to remove unattended section in winnt.sif
4. Reboots the PC...
» GUI-mode Setup
0. Presetup.cmd is launched
1. DetachedProgram executes from winnt.sif at T-39 stage
2. Installs Devices
3. Installs Network
4. Installs Start Menu Items
5. Registers Components
6. svcpack.inf executes at T-13 minute stage
7. cmdlines.txt executes at T-12 minute stage
8. SetupParams executes from winnt.sif at T-9 minute stage <----ren_fold.cmd is launched renaming ~BT and ~LS in order to avoid 10.
9. Saves Settings
10. Deletes temporary files then reboots...
» First Logon
1. Windows logs you in and loads personal settings
2. Both GUIRunOnce from winnt.sif and RunOnceEX executes at the same time <----undoren.cmd is launched to rename back ~BT and ~LS folders
3. Desktop and Taskbar loads
Note: What presetup.cmd does:
1) merges the removed unattended section from winnt.sif to \windows\system32\$winnt$.inf
2) If oempreinstall=1 is found in winnt.sif, copies $oem$ folders
3) If OemPnPDriversPath is found spdrvscn32/64.exe is launched to add those paths in registry,
details
4) launches binifix.cmd to fix boot.ini on the target hard disk from rdisk(Z) to rdisk(Z-1)
In vers. 0.2, which is nearly ready, ~BT and ~LS folders will not be renamed anymore, instead, $winnt$.inf is changed by binifix.cmd to msdosinitiated=0 thus at T-1 Setup does not delete ~LS and ~BT folders and we do not need to rename them to avoid that.
0.2 was delayed until figure out how to amend $winnt$.inf on x64 windows from 32bit environment, but luckily this is now resolved with the help of this excellent info:
http://blogs.sepago.de/nicholas/2008/03/13...on-windows-x64/
I hope knowing more how all this works, will let you add whatever you want to the USB stick.
yahoogle, on Nov 29 2008, 02:35 AM, said:
Hi. I made boot-able my transcend 8gb usb pen drive. I formatted it as FAT32. I tried to install my windows xp professional service pack2, but it works only at the first step. It doesn’t permit me to complete the installation with the 2nd and 3d step. I choose 2nd and 3d step when it boots from the usb pen drive, but it begin the installation again. Some suggest pls.
Thanks!
Can you post your menu.lst and winsetup.lst in root of the USB disk?
As I get it you select Second part of setup, but actually the first part (Text mode) is launched instead, right?
niwa_kun, on Nov 29 2008, 09:18 AM, said:
This guide is really cool...
though i made some changes on it..... like i edited the WINNT.sif
[Data]
MsDosInitiated=1
floppyless=1
[GuiRunOnce]
"binifix4.cmd c:"
"undoren.cmd"
sc config rdummy start= disabled
[SetupParams]
UserExecute = "ren_fold.cmd"
i deleted most all of of the unattended configurations ..cause it bypass some steps of installations... and also deleted the $OEM$ cause the configuration is not good.. so i decide to not include it....
and one more thing....
why in my boot.ini show 4 OS menus:
[Boot Loader]
timeout=0
Default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="USB Repair NOT to Start Microsoft Windows XP Professional" /noexecute=optin /fastdetect
maybe there's something wrong on. binifix4.cmd
The program does not add anything extra to winnt.sif, except a few required lines. If you used the earlier versions- they use unattended.txt if found in your I386 folder AND if winnt.sif was not found.
The program does not add anything to $OEM$ as well, it's copied unmodified from your source.
As for the boot.ini- if you do a few installations one after another, Setup reads the existing boot.ini and add it's contents to the new boot.ini, hence the duplicate lines.
The last line is to be able to perform repair install from USB or Recovery console if started from USB to be able to see your installation. Without it neither will happen.