JFX

Just use a fully unattended setup, so there will not be an OOBE screen.

You can right click on the VHD button, to disable VHD checks.

Yes, this is a limitation made by MS, the driver does not support ESD files.

All files from the WIM file are applied using the compact mode you choose. Expect the files that are need at early boot state. New files will not be compressed and files open with write access will be instantly decompressed by the WOF driver. Only Windows 10 version of compact.exe has the "/compactos:always" option it will start compression the OS and properly using maintenance task to compress new files once in a while. I consider adding a "Recompress Compact OS" option.

Don't know, to me it looks like a successful driver install. If you curious enough, you can set verbose logging: Setting SetupAPI Logging Levels

Hmm, maybe the setupapi.log created during setup has some information about it.

You can disable driversigning in winnt.sif [Unattended] DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore

WinNTSetup_x64.exe NT6 /cfg:"D:\WINSETUP\Win7x64Pro\Win7x64Pro.ini" /setup

No, you will need to use the 2 command line options -cfg and -setup.

Yes, the ini can be used to load/save GUI options, it does not push the setup button.

I have uploaded a new beta version, that should be able to save and load all option form ini. This break exiting ini files, as tweaks options are now saves as in a new [WinNT?\TWEAKS] ini section.

Have you used the generalize option in sysprep? If not this would be an explanation. WinNTsetup does support self created WIM images.

HI stasys44, Thanks for the report about win7 CompactOS and USB boot. Will be fixed in next version. About v2, no it was never updated to use wim install of xp. You can translate v3, to your language by right click on title bar and select "Create Lanuguage File". The new dll can be edited with ResHacker. Or if you prefer, you can rename "Lang\1049.dll" to "Lang\language.dll" than you will have always a Russian interface.

@AlexCeed 1) Well, you the only one, how uses 1 instance for multiple installations. The ini file isn't very useful that way and by far has not all the option cmdline has. It would require quite some code changes and I'm almost certain I'll break something else doing that. 2) What you mean with "result is strange and unstable"? The winnt.sif you choose will be copied in the $WIN_NT$.~BT folder on boot drive. The one in i386 should have no effect on setup.

Yeah, I remember you requested that. I will properly implement that, if I will be in the right mood to do so. You the only one who use the ini file like that. And currently I have no time for this project, so don't expect a fix anytime soon.

That's easy, because I'll have all the work to do. Means, to investigate and fully understand these tools. Than to write all the code and test it on all supported Windows version including WinPE. Not to mention finding solution for the limitations, like the 128GB FAT32 limit diskpart has. In the end, it will increase the support needed.

Why not simply use these 3 tools. I don't think it's good idea adding all this to WinNTSetup.

1) Yes /NoBootSect and also /BCD:none. However if you do an XP/2003 installlation, it will still create some boot files 2) No, not posible, one can not even install Windows Vista and later on an NTFS compressed drive. Also double compression usually don't result in any spaced saving. 3) I will take a look at it.

I have update the first page now, it should list all parameters. You can also push F1 on WinNTSetup to show the help.

Hi Hunter, that was the command line for the old version 2. Seams I have not updated the first page for over 2 years Just remove the "VHD" from the switches: WinNTSetup_x86.exe VHD-create -File:"D:\my.vhd" -Size:25GB -Type:expandable

@commiethebeastie Your wim has all the same DISPLAYNAME, so they all look same. You can use imagex.exe -info, to correct your XML data.

Remove the -Sysletter:T, than the installed system will be on C:. after you booted it.

@Atari800XL Yes, the new version of wimlib adds all needed information. WinNTSetup only needs version, arch and edition ID. And these seems to be okay with Beta7. @Guimenez I have no idea how to avoid this, product key issue.

No idea why there should be a difference. Is this QLogic driver really the the correct driver? I mean can you see it in device manager in your correctly installed XP Home?

Yes, the MSSTMake tool will scan the complete folder tree for Sata drivers and WinNTSetup will merge it's output into the new install. There are only a few sata drivers that doesn't work with that method. I plan to address these in Version 4.