JFX

Need more infos, simple /Add-Package for langpack works alright for me. Did you used /Set-UILang, /Set-UILangFallback, /Set-Syslocale, /Set-UserLocale, /Set-InputLocale, /Set-AllIntl, /Set-SKUIntlDefaults, /Set-SetupUILang ? Why are there so many possibilities anyway

Yes, it applies the WIM file and setup bootmgr and the \Boot\BCD store Not sure want happened there. How was that image created?

Thanks, have fixed this. Btw: You will need to add leading and trailing quotes if the command includes spaces. -RunAfter:"myprogram.exe parameter 1 parameter 2 parameter n" RunAfter will now also add infos to log file.

Update: Version 2.2.1.1 - fixed command line -drivers not worked in some cases (Thanks Atari800XL) - fixed command line -NT5/-NT6 not standalone (Thanks IceBlackIce) - fixed command line -RunAfter not works with relative path (Thanks IceBlackIce) - fixed some bugs with the ISO file option (Thanks Lancelot) - fixed Windows 7 N and KN versions were not accepted for nativeVHDBoot - fixed GUI respond a bit slow in last versions - added bootmenu now contains edition name and VHD mark - added log file now contains details of successfull and failed driver integrations (Win7 only)

For Windows Vista and 7 the offline servicing tools pkgmgr and dism are use directly on the selected folder. XP and 2003 Install are a bit different: - drivers are copied in "Drv" folder in the root of the installation drive - all sub folder from this will be listed in "OemPnPDriversPath" of the unattended file "winnt.sif" - MSSTMake is used on this folder to extract mass storage drivers and required information to load them in TXTMode of setup - MSSTMake results are merge in txtsetup.sif and setupreg.hiv, found driver files are copied to $WIN_NT$.~BT folder in the root of the selected boot drive

Hi LeoZhu, You very quick finding the language.ini. This "feature" is not ready yet and will change in subsequent version. Well it's up to you, I've uploaded version 2.2.0.3 that will accept the file in "unpacked" form. @Atari800XL, You would need the rebuild the ISO with these files added to \I386 folder. Carefully deleteing the lines in txtsetup.sif may help, have not tryed this. Maybe the same goes for dosnet.inf also. But you could also copy these files after WinNtSetup has run. Place them inside \$WIN_NT$.~LS\i386\ folder. The nomral Windows setup parses the txtsetup.sif and dosnet.inf to build up the $WIN_NT$.~LS folder. WinNTSetup just copies the complete i386 folder. @IceBlackIce Thanks, fixed in version 2.2.0.3

I think The reason of these errors is that setup somehow request these files in both states, compress (oleacc.dl_) and uncompressed (oleacc.dll)If you only have oleacc.dl_ than try add expanded version to the same location. (with expand.exe or 7Zip) if you only have oleacc.dll than just make a copy and rename it to oleacc.dl_ (does not need to be compressed API accept it both ways, just the extension matters ) Thanks! Actually I highly appreciate feedback! Supporting all these windows version is very time consuming. Knowing problems helps a lot.

Atari800XL, Please download again, I used wrong return code in one function that must cause failure of the "-drivers:" parameter. For nlite packs, I only fixed some that were reported multiple times. Fixing the root of this nlite problem would be way to much work. Thanks for reporting these bugs

Sure have added Data File Host Mirror to first page

Update: Version 2.2.0.1 - Use "Noerr lines" in VHD creation only if needed - multi boot improvements - automatically unload system BCD if necessary - creates a log file in the system root of the new installation - copies NT6.x $OEM$ folder content to its respective location - all registry operations are done through the offline registry libary - no longer depends on reg.exe and bcopy.exe - fixed save settings to ini forgot some options - fixed file copy errors for some nlite update packs - reduced CPU usage - cosmetics

You didn't missed anything, I should have give this information earlier.

WinNTSetup uses a "fast" install mode The complete section <settings pass="windowsPE"> is ignored in this way of setup. You should get unattended setup by adding SkipMachineOOBE and SkipUserOOBE in your <settings pass="oobeSystem"> <OOBE> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <NetworkLocation>Home</NetworkLocation> <ProtectYourPC>2</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE>

Hi Atari800XL, The system drive needs an extra parameter: -sysletter. WinNTSetup2_x86.exe -nt6 -source:f:\sources\install.wim -syspart:c: -setup -unattend:"autounattend.xml" -savedriveletters -sysletter:C EDIT: Just found a parsing bug: -sysletter only accept C but not C:

Hi amitri, Seems I forgot the $OEM$ folder for Vista and newer windows version. Will be fixed in next release.

1. select your windows distribution 2. choose a installation partition 3. push the setup button hmm, maybe not my biggest talent to explain things... Could you make a list of questions that arise while using the tool? So i can address every thing that is not so clear.

You can load /save settings with CTRL +S and CTRL +L XP Setup Launcher, I don't know this tool and screen shots and download links aren't working anymore. If this all about having gui options for unattended file then no won't be integrated. You could easily create your own editor tools for this with autoit3, that could do exactly what you want.

None. So let's say freeware Actually by the high download count I should consider changing to the beerware license

Yep, since version 2.1.0.0 Windows 8 is fully supported

This was wrong, right would have been: imagex /export H:\s1\sources\bootsetup.wim 1 H:\s1\sources\bootpe.wim "Microsoft Windows Setup (x86)" -boot to fix this simply use imagex -info H:\s1\sources\bootpe.wim -boot 2 @Kullenen how does this affect all the pathes inside HKLM\Classes? Will they be auto adjusted during boot or still point to the old location ((X:$windows.~bt\window) ?

Giving exact commands used would be easier to know what's happen. Seems the boot index is wrong, the winpe index 1 is not suppose to run from WIM Ramboot. Change the index to boot the "setup" image: imagex -info boot.wim -boot 2

Update: Version 2.1.2.0 - fixed WIM file selection only shows "install.wim" Thanks click-click - fixed UniqueID issue with instant VHD creation since version 2.1.0.0 - changed "LANG" folder from 2000/XP/2003 source now always copied - removed option for "XP Partition Mode" - added option "No Reboot on BSoD" - fixed GPT Partitions could not be selected - fixed MountedDevices entrys for MBR/GPT devices - display Alignment for select partitions

Hi click-click, WIM file name should not matter, seems that i have set up the filter for "Choose the install.wim file" dialog wrong. Will be fixed in next release. For now just type "*.wim" and hit Enter, it should display all wim files now.

Hi ilko, great work on WinSetupFromUSB small cosmetic fix: http://ayende.com/blog/4360/how-to-opt-out-of-program-compatibility-assistant Applications with "Setup" in their name need supportedOS entries in their manifest on Windows Vista and later.

Update: Version 2.1.1.0 - ISO File support* - fixed instant VHD creation no longer requires fsutil.exe - add "F" button that bring up the windows format dialog - accept "Preview" edition type for native VHD Boot - added bootice button, if bootice.exe is in same folder - updated tool MSSTMake * check up the WinNTSetup2_iso.cmd batch and define how to mount the ISO

@maanu I truly respect the work on alternative file backed disk drivers like winvblock, firadisk or vboot. But at current development state their are just far cry from Microsoft's own drivers. They never will be supported if this not change. Anyway it's up to the end user to decide. You currently can launch winntsetup with option -DisableVHDChecks which let you install any system on a mounted VHD. Next version will ask on click of the VHD icon. @ghfujianbin Yes i tried all of this, MBR/PBR icon are not important if one choose option to update boot sector (default set). Only active primary icon is highly recommended to be green. 0xc0000225 - means inaccessible device so far it seems that the destination of the boot entry for your new Win2008 install point to an invalid location. maybe it helps if you boot your winxp and try fixing the BCD store with tools like bcdedit/easybcd. most interesting would be the output of: bcdedit -store C:\Boot\BCD -enum all where C: is the drive you selected as boot drive in winntsetup. @jaclaz don't think he meant anything to circumvent the VHDBoot license restrictions. The first time one noticed that a system isn't licensed for nativeVHDBoot is on the first login. To avoid that "useless" install i added a check right before installing into a VHD mounted drive.