JFX

It's a virtual driver, not connected to real hardware, so dism will only add it to the driver store. There should be an uim exe file with the installation files that can install that driver.

Yes, if a drive already has a windows installation inside, it's better to format it.

1. Yes the drive letter of your xp setup drive. A real CD/DVD or a mounted iso image 2. A Primary partition (dark blue) on "Disk 0" with "(System)" in Status register 3. Can be any partition, even the one you selected under 2.

Great work If Pinning will work, this will be a perfect shell replacement. Enjoying a Metro free Win8 now.

Hi testplayer, sorry I can not make an update until weekend, but you can enable/disable that check with right-click on "VHD >>>" button.

The v2.3 versions have disk management (or if not available diskpart) link in system menu (ALT + SPACE) Can't really remember how to create fully hardware independent Windows XP sysprep images. But yes, this is indeed a great and fast way to install WinXP. Currently WinNTSetup is more or less a frozen project for the next months, but maybe I add full support for this way of installation.

Hi Escorpiom, You could do this indeed with the runafter parameter. But no need, I have added a check that will automatically write the right Bootsector. be careful installing that way, winntsetup don't understand that currently, so any GUI option will not work WinNTSetup2.3 beta3

Only 1 real advantage: the x64 version will always be a bit faster. my average time to apply an install.wim: x86 : 40 seconds x64 : 37 seconds So with SSD's or RAMDisk's one can noticed a slightly faster install, but with normal hard disk there won't be.

Had not expected someone would use the x86 in an x64 Winpe. Should be fixed now, no version change this time.

Hi exta, I have added an alignment option inside the system menu (right-click on title bar or ALT+SPACE) If you click WinXP it will set these 4 Dword's to 0. A click on Win7 will delete them. Hope that's what you wanted.

@Atari800XL Your right, is more stable then expected. I focused the buttons in Beta 1. @dksvertix I think the size of edit boxes is more personal taste, i like it that way. The ISO file handling have to be defined inside WinNTSetup2_iso.cmd. WinNTSetup only passes the iso filename to the batch an wait for newly arrived CD/DVD drives.

Yes it's just luck that the tools are in the first MB's of neutral.cab Get more stuff from the PETools folder would easily go up to 700+ MB download and won't make much sense. With the web-setup of the adk things will get better.

Well a used pagefile can't be deleted without reboot and during setup the new system will overwrite it. Existing pagefile should not be problem but it's preferable to format the partition before install. Was just about 30 lines of code, Alpha 5 uploaded.

Well no problem, I want WinNTSetup as perfect as possible Just noticed that the normal setup.exe also creates a pagefile: winpepge.sys I try to add similar next week.

Well, not sure if installing windows 8 on an old system with only 512MB RAM, will be much fun. But you right I should avoid this. Guess memory check and creating pagefile on installation drive will be the right solution. Just need to figure out how to use the API No, that's not possible.

I could reproduce it in a VM with 256 MB RAM Well Microsoft is to blame: wimgapi causes an appcrash instead of a nice and clear error message. Interesting: To apply the new release preview wim's much more RAM is required (~80MB vs. 49MB Consumer Preview) You maybe could solve your problem with a pagefile.

Indeed strange. "I/O error status of 0xc000007f" sounds more that something on your system is broken (RAM, DISK or even some system file)

I tried the release preview, works alright for me. Alpha 4 has no other changes. What version had this error the 2.2 or the 2.3 alpha ?

Thanks for the report. I have not loaded the release preview. Either the install.wim is corrupted or the MS guys changed their WIM format again. maybe alpha 4 can handle it: WinNTSetup2.3 alpha4

@Homes32 Thanks, looks much better now. Added more command line options, see: GetWaikTools -? Already done.

That's great work Thanks! I have integrated your code, cURL.exe is no longer needed but can be copied next to the tool, to be used. @Chris Thanks for the report, should be fixed now.

Thanks Homes32, it seems to work, but I only receive the first 8KB of Neutral.cab. And then get: "This handle value has been terminated."

Yes the version form click-click's link

Thanks guy, good to hear it works! Well it would properly be possible, but would need an CDFS expert to know how much form the beginning of the ISO is needed. If one of these ISO-tools receive the absolute/relative offset and filesize it could be passed to cURL.

Done. Hmm, I don't think that a 650 KB exe is big, but seriously your right the actual download is not more than that: curl -N -r 129740800-136032256 http://download.microsoft.com/download/8/E/9/8E9BBC64-E6F8-457C-9B8D-F6C9A16E6D6A/KB3AIK_EN.iso -o"Neutral.cab" 129740800 - 136032256 is the begin and end offset to download, easily to get with an good HexEditor The 500+ lines au3 code is used to decompress the broken cab file, rename and sort the files according their architecture. To avoid corrupt downloads, all files are hashed in the end. Should work now in WinXP, too