JFX

Yes, it will be added as an ini option. But after reviewing the code I think I'll change that function. I guess v5 is Beta ready at the end of this month...

What you type in the input box will be passed to a hidden cmd.exe. cmd /c "%input%"

For GPT formatted disks, it will only show 1 icon.

I'm not so sure that it's iaStor that causes the BSOD. I mean if you boot from USB, the internal AHCI controller is not needed for successful boot.

Looks like you inject x64 drivers to an x86 Windows.

Well, your log files only show that you integrate intel usb3 drivers, not the generic win 8 ones. Yes, you can use the add drivers option, in case you have an updated Windows 7 WIM file.

Starting with Windows 8 there is a generic driver for USB3.x. IF you add modded windows 8 driver as described in Tools\Win7USB3\ReadMe.txt, then there will be another checkbox on Ready page.

Well you mount the VHD, let's say the driveletter is X: Run this from admin Comment Prompt to load the offline system registry reg load HKLM\sys X:\Windows\system32\config\system than use regedit.exe and check "Start" dword value, it should be 0 HKEY_LOCAL_MACHINE\sys\ControlSet***\services\iusb3hub HKEY_LOCAL_MACHINE\sys\ControlSet***\services\iusb3xhc and finally unload offline registry with: reg unload HKLM\sys or use WinNTSetup on the mounted VHD, check the native USB3 checkbox on Ready page. BTW: If you don't select a source in WinNTSetup, but an installation drive with existing Windows Installation, all tweaks and setting will be applied to the offline system.

That's properly happens because setup has set the start type of your usb driver to manuell (3) try set them to boot (0).

Ah, yes thanks. Sure a USB flash drive without partition table will have alignment of 0.

Problem was the hook in the dialog that let you play wav files. OFN_ENABLEHOOK= 0x20 OFN_ENABLETEMPLATE = 0x40 So replacing the 2 values with 0 removes this customization from the dialog.

There is a folder XP-Users should look at: _DeltaPatchWinXP. @click-click This is common error, try a different PC. Or place vhd on locale disk, finish setup and than copy VHD to USB. BTW: the partition alignment of your device is unknown to WinNTSetup, what's the starting sector of the partition?

Nope, that's a feature! Besides the last 6 are directly coming from windows.

"drive letter preassignment" does nothing if you only have 2 drives and want both to be changed. If you select C: as boot and B: as installation drive than: - you will be able to multi boot both - your NT6 system will be see it self as C: but your NT5 partition will properly get a D: as drive letter

Yes, NoPageFile has effect on VHD, too. Windows does not like to put the pagefile.sys inside a VHD so it would just use another drive. As for the ini file simply use WinNTSetup to set the options. Everything you can't set in the GUI is explained inside WinNTSetup.ini.txt.

I wouldn't actually call that a fork, but it means you have selected the wrong boot partition. Or this partition is just not marked as EFI System part.

[CommonVcPh.dll] 43596: 20 00 435C2: 40 00

Guess I placed the imdisk folder directly under tools to make it easier to update it. Some guys may confuse with the different architecture names (x64 == amd64) && (x86 == i386). The x86 subfolder is still there for 32-bit wofadk.sys, if you want to setup a 32-bit windows with WOF support.

WinNTSetup is fully compatible with WinPE/WinRE. Just run it once to download needed files and than copy it to your ISO || WIM.

With DPI setting of 200% the German strings for "store and display recently opened programs" don't fit before the "Clear list" button. As for DarkRun, dialog 1005 (shell is running as admin) is ignored.

WinNTSetup 4.6.3 - "Disable the new taskbar icons of windows 10" tweak removes the new "Feeds" - fixed crash with differencing VHD - fixed vhd icon right click - vhd icon tooltip shows VHD chain

WinNTSetup 4.6.2 - fixed a crash on Windows 7 with MSDM key in BIOS/UEFI - WinRE driver integration uses fallback \Recovery\WindowsRE\WinRe.wim - WinRE option for Windows 7 USB 3 driver integration - CAPTURE command line did not respect "-min" switch - CAPTURE command line may not set taskbar progress to indeterminate while scanning - some fixes for custom WinPE

It was accessing the wrong array index in 1 check routine for online Windows 7 systems. Here it was checking the path for the first entry in listview, but the BIOS/MSDM has not folder so it was crashing.

Thanks, think I found the reason: testversion2.7z

Hmm, please try these 2 exe files: testversion.7z