ilko_t

I have found a small utility, which does pretty much the job we need- CHKBTINI, which comes with 16 and 32bits versions. I have just tested it and it works fine, however with very limited options. It can fix only errors or discrepancies in rdisk(X)partition(X), if multi(X), disk(X) are wrong or signature part is present it cannot fix it, but these parts are created properly anyway and signature is avoided by not using mapping. In summary- using direct chainloading creates boot.ini like multi(0)disk(0)rdisk(1)partition(1)\WINDOWS and the utility fixes it to: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS when launched during GUI part. If only 2 lines are in boot.ini- default and under "operating systems" it changes both lines, if there are more than 1 line under "operating systems" it changes only "default" line. On the test system it works just fine, but on my working system it cannot find the windows partition, listing it as NON-NT PRIMARY PARTITION and skips it, 1 NTFS primary partition which is active with NT boot sector, and 3 NTFS logical partitions, I need to test why it skips it. BOOT.INI can be system/read-only, it's not a problem. A little drawback, if a proper boot.ini is present and no mapping is used TXT Setup may not see windows installation to be repaired, I'll test this further. @AlexTitov- welcome and thanks for info. Idea- $win_nt$.inf could be changed during GUI part, lets say by a script, launched at T-9 instead of boot_ren.cmd, will jaclaz or cdob create something to test with? ilko

Well, it's nice you fixed it If combofix did the trick and you are sure nothing was in HJT logs then you definitely had a rootkit variant, and I wonder why you didn't scan for. Whatever, hopefully nothing will come back, don't forget to flush system restore.

Hi, it could be a rootkit hiding it, do a scan with at least 2 of the following programs: BlackLight Beta Gmer RootkitRevealer Sophos Anti-Rootkit If it comes up clean post a fresh HiJackThis log here.

Tested it with both mapping and no mapping, result is a "proper" boot.ini, however no copy of the original file is present, just bootini.new, which is exact copy of the final boot.ini. I would prefer to set the attributes of the 3 files on the root at the end of the script. With mapping signature must have been present, in my test both ways ended up with the same boot.ini, haven't checked though whether signature was used, but should have been. Jaclaz, there is a lot more of "usable" ideas in that script, but unfortunately (for me) I cannot make use of it, due to general lack of capabilities in this field The first script you made for creating boot.ini works fine too. Is there any way to get the proper arcpath and amend or create a new boot.ini according to it? Something like: 1. Scan for windows installations and get their arcpath 2. Find a marker file, which is present only in prepared for GUI part partition, and set this partition default This will simulate pretty much the function of bootcfg command, which we need. @Biohead have a look also at differences in both winnt.sif files, can you also post the folder structures on the CD and the USB stick?# Regards, ilko

Hi everyone Short and unexpected holidays are always nice and welcome Thanks for finding, fixed now. Have you read the red note at the end of the last guide? I think you fall in that case. Make sure your USB hard disk is NOT listed first, play a bit with the other IDE devices as described in the previous posts. I have tested it under working XP and it works, however attrib must be used in order to access the existing BOOT.INI, in GUI mode setup I think it's already hidden/system.Next few days I will be testing your and jaclaz's scripts and will report results. ilko

Looks quiet promising I have to urgently go abroad for a week or so, as soon as I get back I will join the party. Regards, ILKO

@jaclaz - what we need is a way to get the proper ARC path is it would be seen if no USB stick's BOOT.INI is used to call the GUI mode, find in what directory windows was placed in and amend or create a new BOOT.INI. The issues I can see: - bootcfg.exe doesn't change entries when working in this mode, it works as if run in normal XP environment. So no options to add boot entries. - If GUI setup is called by ntldr/ boot.ini on the stick, hard disk is seen by GUI SETUP and supposedly by any suitable tool for getting ARC path as HD1, instead of HD0. - If Grub mapping is used (hd0->hd1 and hd1->hd0) boot.ini will be created by Setup with the proper ARC path, but with a signature, which we liked to avoid. May be a script can replace the signature part with "multi", resulting in proper boot.ini? Can you do it by script? signature(de33eaf8)disk(0)rdisk(0)partition(1)\WINDOWS ---> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Menu.lst in this case would be like: map --read-only (hd0) (hd1) map --hook root (hd1,0) chainloader (hd1,0)/ntldrstp restricting us to one hard disk only, if one plans to install it on another, mapping should be modified, which is a bit restricting. Thats why I preferred not to use mapping at all. In summary: with mapping- signature part must be removed and Menu.lst amended if use more than 1 HD. With no mapping- "universal" boot.ini must be used on both USB stick and the one we copy to hard disk. Next few days I will be working on cdob's ideas. BTW you mean bootcfg.exe, not bootfix.bin, right?

Should work just fine. I spent a lot of time searching for a tool, which creates or amends properly BOOT.INI during GUI part with the correct entries, in order to avoid the brute-force way of copying generic one. Had no luck, BOOTFIX doesn't work during GUI part the way it does in Recovery Console, it works the way as in full XP environment. Couldn't find any other suitable tool for the purpose and ended up copying it from stick. If you can get the windows directory and apply it to the generic boot.ini it would make the guide more universal. Actually ATM only boot.ini creation differs the last guide from normal setup. Your ideas about mapping setup floppies via GRUB is nice, hopefully this can be done. Thanks for tip ---------------- Perfect as usual Stick was formated by PEtoUSB - MBR_USB_Before.dat Later rewritten by TEXT mode setup- MBR_USB_After.dat, leaving some files unreadable and stick no longer bootable. If I format the same stick from XP with FAT16 or 32 I cannot boot from it. 2,046,820,352 bytes, formated by PEtoUSB as before. The only difference is that ATM I am using Hitachi microfiter driver to keep it as fixed, thus allowing me quickly to image it with Acronis TI. May be that's why it differs form your calculations?BTW Roadkil's Disk Image v1.1 always gives me "image creation failed" with all USB sticks I have, formated by various tools, most of the time I can see progress going beyond 100%, i.e. 102, 105 and I completely stopped using it as a backup solution. This would be nice, but is it necessary since all of the preparation is done in 2K/XP/2003 system anyway? Yep, if we find a way to invoke setupldr.bin directly from BOOT.INI GRUB will be no longer needed. At the moment if it is called, result was restart as far as I remember, because stick at that time is initialized as hd1, perhaps newer or HEX edited versions of these files will avoid it, but that's beyond my capabilities. I don't think patching MBR will be of any use at this stage, it should be setupldr.bin or ntdetect.com which cause that reboot. I will redo the tests and will report what may be causing reboots later. The idea for multiple entries was to have as much universal BOOT.INI as possible, for example if one installs on different than 1st HD 1st partition. If it can be properly created that would be nice The files are meant to be hidden and system exactly as a normal install will make them. There is no need to make them such, but it's good idea to have them, if installing it for non- technical users, which like to delete anything what they don't like or find strange, lets stay on the safe side BTW on Dell Dimension E520 with Intel P965/G965 MB I had BSOD 7B when starting XP SP2 Setup from the same stick, right after loading drivers and showing "windows is starting". Plugging stick in diff. front/rear ports made no difference. The fix was to use Dietmar's modified NTDETECT.COM, no more BSODs. Bart PE, based again on XP SP2 was giving the same 7B, and a full XP on another stick was freezing before loading shell. Modified file fixed them all.

Another interesting for me thing- I had Bart PE minint folder on the root of the same stick, while testing I have noticed that if txtsetup.sif in root is missing or renamed, Bart PE is launched instead of TEXT mode setup. It might have been already discussed somewhere, but gives a good idea how both may coexist, without having to create second partition for it. I am going to test it further and report results. @buseeliu- try some random shots to see why your USB stick is so slow: 1. Update your BIOS 2. Check setting in BIOS for USB, make sure USB2.0 is enabled, play a bit with the other settings for USB- legacy support etc. 3. Test the same stick on another motherboard/system, which is known to support faster speeds 4. Test on your motherboard another stick, which is known to be fast 5. Unplug all other USB devices while testing 6. Use one by one the rear USB ports, try do disconnect fron USB ports from motherboard May be jaclaz can help you with some other ideas, hes knowledge about usb sticks is amazing @jaclaz- Have you had a chance to look what was going wrong with MBRs?

The long wait at T-1 is finally fixed, also no need to write-protect the stick during GUI mode, as we are going to rename temporary the 2 folders and txtsetip.sif and rename them back during first logon. Here is the revised guide, tested on XP Pro SP2, both clean and repair install. With RED color are marked new or changed entries, strikethrouh font is for entries or files no longer needed compared to the old guide. If you are starting from a scratch just skip those entries or files: 1. Format stick using PEtoUSB or any other utility of your choice, which makes it bootable with 2k/XP boot sector 2. Copy NTDETECT.COM, NTLDR to root and create BOOT.INI BOOT.INI [Boot Loader] Timeout=15 Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS [Operating Systems] c:\grldr="Start GRUB" multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="GUI Setup" /FASTDETECT If you are going to install on another partition/disk amend entries to reflect that. Make sure you can boot from stick and reach the menu. 3. Get the latest GRUB4DOS and copy GRLDR to the USB root. If you have any issues use the last stable version. Create in USB stick root MENU.LST color black/cyan yellow/cyan timeout 15 default 0 title Phase 1 WinXP Text Mode Setup chainloader (hd0,0)/setupldr.bin 4. Backup your local BOOT.INI and in the XP setup folder \I386 run winnt32 /makelocalsource /noreboot after it's finished restore BOOT.INI you backed up. 5. Copy two new folders onto the USB stick root - $WIN_NT$.~BT and $WIN_NT$.~LS 6. In \$WIN_NT$.~BT modify WINNT.SIF and MIGRATE.INF [Version] Signature = "$Windows NT$" [Addreg] HKLM,"SYSTEM\MountedDevices",,0x00000010 HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",%REG_DWORD%,1 [Strings] ;Handy macro substitutions (non-localizable) REG_SZ = 0x00000000 REG_BINARY = 0x00000001 REG_DWORD = 0x00010001 REG_MULTI_SZ = 0x00010000 REG_SZ_APPEND = 0x00010008 REG_EXPAND_SZ = 0x00020000 If you wish to preserve your USB storage drive letter use CDOB's script to create MIGRATE.INF, don't forget to add the above entries : MkMigratgeInf.cmd @echo off REM MkMigratgeInf.cmd v0.01 REM created by cdob setlocal EnableExtensions set Drive=%~d1 if %Drive%.==. set Drive=%~d0 set FileName=%~2 if %FileName%.==. set FileName=MIGRATE.INF.TXT set MigrateDrive=U: if not %~d3.==. set MigrateDrive=%~d3 set Value= FOR /F "skip=2 tokens=1-2*" %%a IN ('reg query HKLM\System\MountedDevices /v \DosDevices\%Drive%') DO set Value=%%c if %Value%.==. (echo drive settings %Drive% not found & goto :EOF) set MigrateStr=%Value:~0,2% set count=2 :begin_parse call :exec set MidStr=%%Value:~%count%,2%% if %MidStr%.==. goto :exit_parse set MigrateStr=%MigrateStr%,%MidStr% set /a count+=2 goto begin_parse :exit_parse (echo [Version] echo Signature = "$Windows NT$" echo. echo [Addreg] echo HKLM,"SYSTEM\MountedDevices","\DosDevices\%MigrateDrive%",0x00030001,\ echo %MigrateStr%)>%FileName% goto :EOF :exec %* goto :EOF 7. Create a folder BOOTFILES in USB stick root, and copy NTDETECT.COM, NTLDR and create there your custom BOOT.INI, which will be copied on hard disk later, during the first logon. Set them system, hidden and read-only in advance. BOOT.INI [boot loader] timeout=15 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP Professional 0 1" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Professional 0 2" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="XP Professional 0 3" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="XP Professional 1 1" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="XP Professional 1 2" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="XP Professional 1 3" /noexecute=optin /fastdetect 8. Create: undoUSBWP.reg no longer needed ! hiveOEM.inf no longer needed ! BOOT_REN.CMD @echo off SET TAGFILE=\bootfiles FOR %%h IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET USBDRIVE=%%h: xcopy %USBDRIVE%\bootfiles\*.* %SYSTEMDRIVE%\ /y /h /r /k ren %USBDRIVE%\txtsetup.sif txtsetup.bak ren %USBDRIVE%\$WIN_NT$.~BT WIN_NT.BT ren %USBDRIVE%\$WIN_NT$.~LS WIN_NT.LS exit UndoRen.CMD @echo off SET TAGFILE=\BOOTFILES FOR %%h IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET USBDRIVE=%%h: ren %USBDRIVE%\txtsetup.bak txtsetup.sif ren %USBDRIVE%\WIN_NT.BT $WIN_NT$.~BT ren %USBDRIVE%\WIN_NT.LS $WIN_NT$.~LS exit and place them in $WIN_NT$.~LS\i386 9. Copy TXTSETUP.SIF and SETUPLDR.BIN from \$WIN_NT$.~BT to root of USB stick and add the following lines to TXTSETUP.SIF -------- Install XP and leave stick plugged in until after the first logon screen. Notes: 1. If you use an answer file when launching WINNT32.EXE make sure you delete the whole [unattend] section in WINNT.SIF, otherwise you won't be able to use System Restore and SETUP will not prompt on which partition to install. 2. If you use BTS mass storage DP method 2 and repair install then include the following line in \$WIN_NT$.~LS\I386\PRESETUP.CMD DEL /F %systemroot%\system32\setupold.exeor GUI Setup stops at start, complaining about fake setup being executed. 3. If during TEXT MODE your usb stick is listed first when SETUP searches for disks , above SATA/SCSI disks, disable in BIOS IDE channels including the ones with CDROM/DVD attached or disconnect them, this should fix the order. Do not continue install if stick is listed first, this will corrupt files and MBR on it. ------------------------------------ The problem described in post #156 turned out to be that the script launched by CMDLINES.TXT was being executed from within $WIN_NT$.~LS, giving "access denied" error, so I have tried to launch same script via WINNT.SIF [setupParams] section which worked flawlessly. Wait at T-1 is about 1-2 seconds now, this also saved a few files and entries to be written edit1 (15.Jun.07): Undo_Ren.cmd corrected to UndoRen.cmd

@buseeliu NTDETECT.COM and NTLDR are the same files as on root of your USB stick, you can copy them from your XP install source i.e. \I386 or \$WIN_NT$.~BT on your USB stick. BOOT.INI code is described right under 7., you need to CREATE it, you don't copy it from anywhere. As I already wrote- prepare the stick in advance and at once, from working XP/2k whatever system you have. Once it's prepared no further steps are needed. As for the HAL missing error please post here your BOOT.INI file found on root of your USB stick. As for the slow speed- are you sure your motherboard supports USB2.0? Once drivers in TEXT mode setup are loaded and you are presented the screen to choose REPAIR/INSTALL if motherboard supports USB2.0 you should have it. P.S. please be careful when quoting, it's hard to understand which part was written by you and which is quoted.

@buseeliu I believe your BOOT.INI file points to the wrong partition on the hard disk. Are installing on first hard disk, first partition? If not you need to amend the BOOT.INI on the USB stick.If that's not the case then did you leave USB stick plugged in? Please give as much as possible information for your setup, how many partitions, how many hard drives you have, where do you install it on etc. I really don't get what you don't understand in this step Using winnt.exe or the procedure described? Please try to be as much informative as possible, don't make the other party guessing what you are trying to say.

All the steps are being done within working XP. You need to run that from command prompt of your local XP setup folder. An easy way to do that is by adding this registry info:CMDHERE.REG Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Directory\shell\Command Prompt Here] @="Command &Prompt Here" [HKEY_CLASSES_ROOT\Directory\shell\Command Prompt Here\command] @="cmd.exe /k cd %1 " When you import it you may right-click on the desired forder (I386) and from the context menu select OPEN COMMAND WINDOW HERE. @wimb- I just hope I did not make typos or missed a thing, as I usually do

As CDROM I think, which is different than USB stick, seen as hard drive/removable storage. If you "fool" SETUP USB stick to appear as CDROM- GRUB gives some options via mapping, but have no idea will it be possible as of now- the issue will be solved.Another way is if Grub4Dos or other bootloader fully supports ISO boot, then we can simply copy the ISO file and call it. Again no idea how to do it, it may be possible. Sorry, I didn't get this, winnt.exe is just preparing the disk for the next stage- TEXT mode, has nothing to do with setupldr.bin in that stage and the order disks are found.

@snowden- the problem when using ntldr and ntdetect.com to boot from stick or setupldr.bin renamed /ntdetect.com is that USB stick is second hard drive as seen and enumerated by them, but setupldr.bin expects files to be on first hard drive. Using GRUB overrides this issue. Unless modified/other/new boot files mentioned are used I don't see a way to fix this issue. Copying the whole contents of XP CDROM and patching setupldr.bin will save you no more than 2-3 minutes, the time to create $WIN_NT$.~BT and $WIN_NT$.~LS by WINNT32.EXE, but may lead to other issues or incompatibility. I prefer not to use patched files when possible. Surely any other ideas are welcome, as long as this would save time and give better results. Another idea, which will save you all the steps above is to create an image of a hard disk prepared with $WIN_NT$.~BT and $WIN_NT$.~LS (check winnt32 switches and /system in particular ) folders and place the image from USB using your favorite imaging program, either from PE or from DOS/LINUX. When working with large files USB sticks are usually much faster. Using Bart PE and running winnt32.exe has always been an option and gives greater flexibility.

Here is the edited guide for Windows XP SP2, on 2k/2k3 should work too. 1. Format stick using PEtoUSB or any other utility of your choice, which makes it bootable with 2k/XP boot sector 2. Copy NTDETECT.COM, NTLDR to root and create BOOT.INI BOOT.INI [Boot Loader] Timeout=15 Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS [Operating Systems] c:\grldr="Start GRUB" multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="GUI Setup" /FASTDETECT If you are going to install on another partition/disk amend entries to reflect that. Make sure you can boot from stick and reach the menu. 3. Get the latest GRUB4DOS and copy GRLDR to the USB root. If you have any issues use the last stable version. Create in USB stick root MENU.LST color black/cyan yellow/cyan timeout 15 default 0 title Phase 1 WinXP Text Mode Setup chainloader (hd0,0)/setupldr.bin 4. Backup your local BOOT.INI and in the XP setup folder \I386 run winnt32 /makelocalsource /noreboot after it's finished restore BOOT.INI you backed up. 5. Copy two new folders onto the USB stick root - $WIN_NT$.~BT and $WIN_NT$.~LS 6. In \$WIN_NT$.~BT modify WINNT.SIF [data] msdosinitiated="1" floppyless="1" AutoPartition="0" UseSignatures="no" InstallDir="\WINDOWS" winntupgrade="no" win9xupgrade="no" [GuiRunOnce] "regedit /s %systemdrive%\windows\system32\undoUSBWP.reg" "%systemdrive%\windows\system32\BOOTFLS.CMD" and MIGRATE.INF [Version] Signature = "$Windows NT$" [Addreg] HKLM,"SYSTEM\MountedDevices",,0x00000010 HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",%REG_DWORD%,1 [Strings] ;Handy macro substitutions (non-localizable) REG_SZ = 0x00000000 REG_BINARY = 0x00000001 REG_DWORD = 0x00010001 REG_MULTI_SZ = 0x00010000 REG_SZ_APPEND = 0x00010008 REG_EXPAND_SZ = 0x00020000 If you wish to preserve your USB storage drive letter use CDOB's script to create MIGRATE.INF, don't forget to add the above entries : MkMigratgeInf.cmd @echo off REM MkMigratgeInf.cmd v0.01 REM created by cdob setlocal EnableExtensions set Drive=%~d1 if %Drive%.==. set Drive=%~d0 set FileName=%~2 if %FileName%.==. set FileName=MIGRATE.INF.TXT set MigrateDrive=U: if not %~d3.==. set MigrateDrive=%~d3 set Value= FOR /F "skip=2 tokens=1-2*" %%a IN ('reg query HKLM\System\MountedDevices /v \DosDevices\%Drive%') DO set Value=%%c if %Value%.==. (echo drive settings %Drive% not found & goto :EOF) set MigrateStr=%Value:~0,2% set count=2 :begin_parse call :exec set MidStr=%%Value:~%count%,2%% if %MidStr%.==. goto :exit_parse set MigrateStr=%MigrateStr%,%MidStr% set /a count+=2 goto begin_parse :exit_parse (echo [Version] echo Signature = "$Windows NT$" echo. echo [Addreg] echo HKLM,"SYSTEM\MountedDevices","\DosDevices\%MigrateDrive%",0x00030001,\ echo %MigrateStr%)>%FileName% goto :EOF :exec %* goto :EOF 7. Create a folder BOOTFILES in USB stick root, and copy NTDETECT.COM, NTLDR and create there your custom BOOT.INI, which will be copied on hard disk later, during the first logon. Set them system, hidden and read-only in advance. BOOT.INI [boot loader] timeout=15 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="XP Professional 0 1" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Professional 0 2" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="XP Professional 0 3" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="XP Professional 1 1" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="XP Professional 1 2" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="XP Professional 1 3" /noexecute=optin /fastdetect 8. Create: undoUSBWP.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorageDevicePolicies] "WriteProtect"="0" hiveOEM.inf [Version] Signature = "$Windows NT$" DriverVer=07/01/2001,5.1.2600.2180 [AddReg] ;WriteProtect USB HKLM,"SYSTEM\CurrentControlSet\Control\StorageDevicePolicies","WriteProtect",0x10001,1 and BOOTFLS.CMD @echo off SET TAGFILE=\BOOTFILES FOR %%h IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET USBDRIVE=%%h: xcopy %USBDRIVE%\bootfiles\*.* %SYSTEMDRIVE%\ /y /h /r /k exit and place them in $WIN_NT$.~LS\i386 9. Copy TXTSETUP.SIF and SETUPLDR.BIN from \$WIN_NT$.~BT to root of USB stick and add the following lines to TXTSETUP.SIF [SourceDisksFiles]..... ..... hiveOEM.inf = 100,,,,,,_x,,3,3 undoUSBWP.reg = 100,,,,,,_x,2,0,0 BOOTFLS.CMD = 100,,,,,,_x,2,0,0 .... .... [HiveInfs.Fresh] AddReg = hiveOEM.inf,AddReg [HiveInfs.Upgrade] AddReg = hiveOEM.inf,AddReg -------- Install XP and leave stick plugged in until after the first logon screen. Notes: 1. If you use an answer file when launching WINNT32.EXE make sure you delete the whole [unattend] section in WINNT.SIF, otherwise you won't be able to use System Restore and SETUP will not prompt on which partition to install. 2. If you use BTS mass storage DP method 2 and repair install then include the following line in \$WIN_NT$.~LS\I386\PRESETUP.CMD DEL /F %systemroot%\system32\setupold.exeor GUI Setup stops at start, complaining about fake setup being executed. 3. If during TEXT MODE your usb stick is listed first when SETUP searches for disks , above SATA/SCSI disks, disable in BIOS IDE channels including the ones with CDROM/DVD attached or disconnect them, this should fix the order. Do not continue install if stick is listed first, this will corrupt files and MBR on it. ------------------------------------ All credits for the most important part- how to write- protect the USB flash go to cdob Many thanks to jaclaz, wimb and porear

At the end of GUI Setup attempts to delete temp. folders, but since they are write-protected it's kinda stuck at this point until time-out occurs and it stops trying. In my tests it takes about 2 to complete that point, if you unplug the stick for example at T-1 or even earlier it' takes like 1 or 2 seconds. That's why in one of the previous posts I tried to rename the 2 folders on USB stick using a simple script in CMDLINES, but only ~BT folder survived. Either SETUP deletes files earlier, before CMDLINES is executed, or when it's executed folder is in use or somehow protected by SETUP, causing rename not to complete. For these tests I left stick unprotected. For now I will not do any other attempts to avoid this, since delay is not severe. About 911CD forum- I think you haven't received your activation email, if I remember right they are using manual validation, you are able to logon using your user name, but some parts are behaving strangely. I waited more than a week to receive that email and activate the account. In my first attempt few months back email didn't arrive at all, so I had to re-register.

Hi wimb, nice to read that, in a few days I am going to sum up all changes in a single post, I believe everything is sorted out, except the minor issue with the long delay at T-1. I think it's still there, check your browser settings, clear cache etc. Regards, ilko

Hi, this was easy I think Add the following line in TXTSETUP.SIF : No files were deleted in my tests.About BOOT.INI- CMDLINES is not executed, I noticed BOOT.INI gets changed 3 times: 1. TEXT Setup adds default entry pointing to the partition it installs on as it sees it, in our case it's rdisk(1), instead of (0) and timeout 1 2. At beginning of GUI Setup same entries, but after PRESETUP.CMD is launched if present, so PRESETUP.CMD won't work for us 3. Before end of GUI Setup, but before CMDLINES is executed if doing clean install. At this stage it (may be only) changes timeout to 30 So if we execute BOOT_REN.CMD at the first logon screen by adding the following lines we should be fine. No need to use CMDLINES anymore, but even if it's used boot files will be rewritten twice if performing an repair. This line is executed in repair mode too. TXTSETUP.SIF and WINNT.SIF May be it's about time to rewrite the guide once we confirm the results edit: If one uses BTS mass storage DP method 2 and repair install then include the following line in \$WIN_NT$.~LS\I386\PRESETUP.CMD or GUI Setup stops at start, complaining about fake setup being executed.

I can see it, it's the first post in USB booting subforum:http://www.911cd.net/forums//index.php?showforum=37 I am still in touch with Gigabyte, surprisingly they are investigating this further Copy of their last reply: Well, DOS and Bart PE... at least they are trying, hopefully some progress could be achieved. That's interesting result, but I believe normal, actually we have never tried so far to use the repair option when SETUP uses different approach. The way now USB write-protect is implemented by MIGRATE.INF and oemHIVES.inf applies only for new installations only. Further investigation will be needed how to fix it, thanks for bringing this up

Hi wimb, I am glad it worked fine Sorry about the messy post of mine I beleive this topic, as well as Grub4Dos README.TXT will give you the ideas how to launch Ghost. About the slow boot- it's because your motherboard supports USB1.1 boot only, once control is passed to a USB2 driver it operates at it's full speed. Bart PE loads much more before USB2 driver is loaded (may be driver could made to load earlier?) than XP Setup. My laptop Dell Inspiron 6000 supports USB2 boot and believe me XP setup loads in a flash, no more than 10-12 secs. I can't read the names of the drivers being loaded, whereas on the Gygabyte DS3P and Abit AN7 motherboards it's much much slower. Bart PE loads at horrible speed too on them. Once USB driver takes control it's fast again. I have written recently to Gigabyte support about that, in the first few responses they had no idea what I was talking about, once we made it clear no more responses ... for now. I also phoned tech. support in UK and the guy got the idea, but only adviced me to unplug all other USB devices and not to use front ports, no difference at all. Next to call is support in Taiwan Update of BIOSes didn't do any change, for now. I have just started a new topic in 911cd.net about that, you may keep an eye what is going on : http://www.911cd.net/forums//index.php?showtopic=19731 Hopefully we will collect some useful database. Regards, ilko

Sorry, yes, I will edit the long post. In a few cases I noticed that they are not written there, but may be SETUP tried to put them on stick or skipped because saw them on stick. That way we are sure everything needed to boot is in place. rdisk(1) is because no mapping is made via GRUB, that was the reason we used map (hd0) (hd1) in the previous guide. It also won't add signature, because no mapping is made and SETUP sees the disks as they are.The working line rdisk(0) I beleive is a copy of the one on the USB stick, I have no idea when SETUP adds it, but I noticed the same behavior. If mapping was used on my last test it was ending with signature and disk couldn't be booted with that signature, no idea why it worked before. That's why I decided to be brutal and replace the whole BOOT.INI as this would resolve all issues with it. Your BOOT.INI was not copied, I believe CMDLINES was not set up properly, or switches in WINNT.SIF were missing. I am going to repeat all this step by step to make sure I haven't missed anything when was writing the post. Thanks for your time edit: Are you sure that CMDLINES.TXT and BOOT_REN.CMD were placed in the right subfolder \$WIN_NT$.~LS\$OEM$ ? edit2: Ahh, silly me I missed to copy the tag. Post edited. CMDLINES.TXT

Some help needed here: I did a few attempts to resolve the long wait at T-1, used only write protection in MIGRATE.INF. No files are deleted during TXT part. I added these lines to BOOT_REN.CMD : and created UNDOREN.CMD, which is executed by [GUIRunOnce] in WINNT.SIF along with the relevant entries in TXTSETUP.SIF UNDOREN.CMD TXTSETUP.SIF and $WIN_NT$.~LS get deleted, $WIN_NT$.~BT - not Removed UNDOREN.CMD and can confirm WIN_NT.BT is on stick, properly renamed. This means for me that either $WIN_NT$.~LS was deleted earlier, before T-1, or is in use or somehow protected and script cannot rename it on time. Here is result of exact time when BOOT_REN.CMD is executed as logged in CMDLINES.LOG: Here is part of SETUPLOG.TXT 05/15/2007 01:31:22.656,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5948,END_SECTION,DoRunonce 05/15/2007 01:31:22.656,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5957,BEGIN_SECTION,Configuring Setup 05/15/2007 01:31:23.046,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service Spooler 05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service Spooler 05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\printer.c,131,,StartSpooler: Just opened service Spooler 05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\printer.c,134,,StartSpooler: Just started service Spooler, ret=0, error=1056 05/15/2007 01:31:23.062,d:\xpsprtm\base\ntsetup\syssetup\printer.c,253,,StartSpooler: Just closed service handler Spooler 05/15/2007 01:31:23.234,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service EventLog 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service EventLog 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service ClipSrv 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service ClipSrv 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service NetDDE 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service NetDDE 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,334,,MyChangeServiceConfig: LockingServiceDatabase for service NetDDEdsdm 05/15/2007 01:31:23.250,d:\xpsprtm\base\ntsetup\syssetup\services.c,408,,MyChangeServiceConfig: Unlocked ServiceDatabase for service NetDDEdsdm 05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3794,BEGIN_SECTION,Loading service pack (phase 4) 05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3796,END_SECTION,Loading service pack (phase 4) 05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3803,BEGIN_SECTION,Network setup handling Internet Server issues 05/15/2007 01:31:23.265,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3809,END_SECTION,Network setup handling Internet Server issues 05/15/2007 01:31:23.281,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3836,BEGIN_SECTION,Setting up virtual memory 05/15/2007 01:31:23.296,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,SetUpVirtualMemory: ENTER 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: C:\, spc=8, bps=512, freeclus=1042209, totalclus=1279167 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: C:\, FreeSpace = 04268888064 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: C:\ had 120586240 byte pagefile, new FreeSpace = 194507008 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: Free space on C:\ is 4186 MB 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: U:\, spc=64, bps=512, freeclus=48429, totalclus=62454 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: U:\, FreeSpace = 01586921472 [b]05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,BuildVolumeFreeSpaceList: Free space on U:\ is 1513 MB[/b] 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,SetUpVirtualMemory: loc 1 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Setup configured the system to place a 1536 MB pagefile on drive C:. 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Crashdump was enabled. 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,SetUpVirtualMemory: EXIT (1) 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3844,END_SECTION,Setting up virtual memory 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3855,BEGIN_SECTION,Processing [RunPrograms] section 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3857,END_SECTION,Processing [RunPrograms] section 05/15/2007 01:31:28.859,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,2622,,Power scheme: desktop. 05/15/2007 01:31:28.875,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,2626,,SetActivePwrScheme succeeded. 05/15/2007 01:31:29.140,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,The external program boot_ren.cmd returned exit code 0. 05/15/2007 01:31:29.187,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,The external program rundll32 advpack.dll,LaunchINFSection nLite.inf,U returned exit code 0. 05/15/2007 01:31:29.187,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3915,BEGIN_SECTION,Saving hives 05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3929,END_SECTION,Saving hives 05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3958,BEGIN_SECTION,Copying optional directories 05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,3963,END_SECTION,Copying optional directories 05/15/2007 01:31:29.203,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5959,END_SECTION,Configuring Setup 05/15/2007 01:31:29.218,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5964,BEGIN_SECTION,Configuring Common 05/15/2007 01:31:29.218,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,4231,BEGIN_SECTION,Generating security templates 05/15/2007 01:31:38.906,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,4233,END_SECTION,Generating security templates 05/15/2007 01:31:38.906,d:\xpsprtm\base\ntsetup\syssetup\copy.c,627,,SETUP: Marked file perfmon.msc read-only 05/15/2007 01:31:38.921,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5966,END_SECTION,Configuring Common 05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6065,BEGIN_SECTION,Fix the security on <All Users\Application Data\Microsoft\Windows NT> 05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,Setup invoked the external program shmgrate.exe Fix-HTML-Help. 05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6067,END_SECTION,Fix the security on <All Users\Application Data\Microsoft\Windows NT> 05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6072,BEGIN_SECTION,Migrating exception packages 05/15/2007 01:31:38.937,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6074,END_SECTION,Migrating exception packages 05/15/2007 01:31:38.953,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6090,BEGIN_SECTION,Running SFC 05/15/2007 01:31:39.000,d:\xpsprtm\base\ntsetup\syssetup\registry.c,1551,BEGIN_SECTION,DeleteCurrentProductIdInRegistry 05/15/2007 01:31:39.015,d:\xpsprtm\base\ntsetup\syssetup\registry.c,1564,END_SECTION,DeleteCurrentProductIdInRegistry 05/15/2007 01:31:39.015,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6216,BEGIN_SECTION,Saving repair info 05/15/2007 01:31:42.734,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6218,END_SECTION,Saving repair info 05/15/2007 01:31:42.734,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6227,BEGIN_SECTION,Removing Temporary Files 05/15/2007 01:31:42.750,d:\xpsprtm\base\ntsetup\syssetup\utils.cpp,18,,Setup: Activationrequired 05/15/2007 01:31:42.843,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,4904,,Setup: (Information) activation icons removed 05/15/2007 01:31:42.859,d:\xpsprtm\base\ntsetup\syssetup\cmdline.c,228,,SETUP: SpSetupLoadParameter was unable to find DynamicUpdateAdditionalPostGuiDrivers. 05/15/2007 01:32:04.421,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5416,BEGIN_SECTION,Setting up Crash Recovery 05/15/2007 01:32:04.437,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,5420,END_SECTION,Setting up Crash Recovery 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6245,END_SECTION,Removing Temporary Files 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6252,,SETUP: CallSceSetupRootSecurity completed 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6269,,SETUP: Changing registry quota from 111848106 to 55924053... 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6274,,SETUP: ... succeeded 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\services.c,496,,SetupStartService: Sending StartService to <Eventlog> 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\services.c,498,,SetupStartService: Sent StartService to <Eventlog> 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\welcome.c,934,END_SECTION,Copying Files Page 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6294,END_SECTION,FinishThread 05/15/2007 01:32:08.234,d:\xpsprtm\base\ntsetup\syssetup\welcome.c,1096,BEGIN_SECTION,Finish Page 05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6640,END_SECTION,Wizard 05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6644,BEGIN_SECTION,Recovery 05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6648,END_SECTION,Recovery 05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\syssetup.c,6650,BEGIN_SECTION,Shutdown [b]05/15/2007 01:32:08.250,d:\xpsprtm\base\ntsetup\syssetup\log.c,133,,GUI mode Setup has finished.[/b] Note that at 01:31:28.859 SETUP reports free space on stick as its supposed to be if no files were deleted. Either that's incorrect or $WIN_NT$.~LS is deleted after 01:31:28.859 (about T-12- T-8). Or as I think folder is in use and cannot be renamed on time. May be one can spot something in the log. Also, the idea to remove stick during T-1 to avoid long wait seems not so good, I can see SETUP is still doing something else at that stage, apart form deleting temp files. Any ideas how to proceed further? @Jaclaz - if you are still interested the attached files contains MBR and bootsector saved by HDhacker when formated by PEtoUSB and rewritten by TEXT mode SETUP. @wimp - The IDs you have are for SIS IDE, and I can't see them in generic XP SP2 CD TXTSETUP.SIF HIDs, that means for me probably that yours are splipstreamed in your CD, SISIDE.SYS, which is later renamed and copied as NTBOOTDD.SYS. Can you search in your TXTSETUP.SIF on the CD for VEN_1039&DEV_5513 and give all results here? XP_from_USB.zip

:D Mistery solved When you have an IDE device attached, along with SATA disk, this breaks the order. IDE device could be CD/DVD or hard disk, and boot order on BIOS makes no difference. In this case the order SETUP enumerates devices is IDE-USB-SATA. If IDE device is disconnected or primary/secondary channel is disabled in BIOS order becomes SATA-USB. On Gigabyte DS3P with Intel ICH8R (6 SATA ports) and JMicron 363 (2 SATA/1 IDE) if both controllers are in AHCI or RAID mode order is SATA1-SATA2-USB. If Jmicron is in IDE mode this makes no difference, as its a separate controller, order is SATA1- SATA2- USB. However, if Jmicron is in AHCI or RAID and ICH8 is in native IDE mode order changes to IDE (ICH8R) - USB - SATA (Jmicron). 1 hard drive attached to both controllers and a DVDRW to the JMicron IDE port, DVD was never disconnected or disabled. So if IDE device is attached to external controller such as JMicron, this doens't change the order SETUP finds devices, and USB goes last, if a native IDE is connected it always goes first, then USB, and last is SATA. If only IDE hard disk and USB stick are connected (CD/DVD disconnected or primary/secondary channel disabled in BIOS) order is IDE disc- USB. This was confirmed on Abit AN7 too. If CD (secondary channel) is disabled order was SATA-USB, when IDE disc was connected order becomes IDE-USB-SATA That should clear any further issues with device order, once we ensure that USB is not first we can carry on with installation. Here is what I did to overcome signature problem in BOOT.INI and make the installation as universal as possible. Stick is formated by PEtoUSB, copy NTDETECT.COM, NTLDR and BOOT.INI, which is: BOOT.INI If you are going to install on another partition/disk amend entries to reflect that.Copy GRLDR to the root of stick and create MENU.LST Create a folder BOOTFILES in root, and copy NTDETECT.COM, NTLDR and your custom BOOT.INI which will be copied on hard disk. Set them system, hidden and read-only in advance. BOOT.INI In $WIN_NT$.~LS make a new folder if you don't have already $OEM$ and create in it CMDLINES.TXT In the same folder create BOOT_REN.CMD Leave space between %SYSTEMDRIVE%\ and /y /h /r /kWINNT.SIF [unattended] section and oempreinstall=yes is not needed.The rest is same as the first guide. This way GRUB mapping is not used, and once GUI setup is completed USB stick is no longer needed, we have brand new shining BOOT.INI along with all necessary boot files on the hard disk.

I am using XP with BTS mass storage drivers pack slipstreamed, so it's via txtsetup.sif. I tried to change the order in txtsetup.sif, moving the Hardware VID&PID lines for USB mass storage and Sil3112 above then below anything else, hoping that SETUP reads the lines and scans for devices according to the order written in txtsetup.sif but that didn't change anything. Also tried to set mass storage drivers as described here, but to no avail too:http://www.ngine.de/index.jsp?pageid=4176 As far as I remember I tried to swap order in these lines, everything was shoots in the darkness: [DiskDriverMap] abiosdsk = "%1!u! MB Micro Channel Disk" atdisk = "%1!u! MB IDE/ESDI Disk" disk = "%1!u! MB Disk %2!u! at Id %3!u! on bus %4!u! on %5" and [sCSI.Load] ........ I believe similar setup could be achieved in VMware, set 2 disks- 1 SCSI and 1 IDE and try to change the order SETUP detects them. Normally IDE goes first, SCSI second. If one could find how to swap them, same method could be used to set USB stick last. I will try first what happens to the stick when SETUP finds NT MBR on it, instead of GRUB. edit: interesting line in txtsetup.sif, not sure is it used only when upgrading : [Directories.DeleteOnUpgrade] 1, Prefetch 2, ReinstallBackups 2, os2 1,"Driver Cache\i386" 2, CatRoot2 1, $NtServicePackUninstall$ 1, ServicePackFiles 124, x86_comctl32_6.0.0.0_0000 124, x86_GdiPlus_1.0.0.0_0409 124, x86_Microsoft-Visual-CPlusPlus-Runtime-Libraries_6.0.0.0_0000 124, x86_Microsoft.Tools.VisualCPlusPlus.Runtime-Libraries_no-public-key_6.0.0.0_x-ww_4d05e542 124, x86_Microsoft.Windows.Common-Controls_no-public-key_6.0.0.0_x-ww_cd4c0d12 124, x86_Microsoft.Windows.GdiPlus_no-public-key_1.0.0.0_x-ww_fad9507f 124, InstallTemp