JFX

@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.

The driverpacks need to decompressed to let's say D:\Drivers. %usb%\WinntSetup\WinNTSetup_x86.exe NT5 -source:l:\ -syspart:C: -tempdrive:c: -setup -reboot -drivers:D:\Drivers

Good to hear it works now. I'm no expert about GPT, but maybe this diskpart options should hide the volume if it still not helps, maybe also use this on your recovery volume

2GB sounds good. Just wonder, I'm no really friend of deleting files in WinSxS folder. But wouldn't it be much safer to simple replace all superseded components with hardlink to the newest version?

Could you give more detail about what error is shown. You diskpart option are correct. In WinNTSetup the boot partition should be auto selected to S: and all icons should be green.

Sounds very interesting! How much space does it saves with the default recommended updates provided by Windows Updates (~ 209 updates if I recall correct)?

A made a program to add all needed information: https://wimlib.net/forums/viewtopic.php?f=1&t=248&p=324#p324 About the speed, well you will need to check it out.

A similar problem also appeared in WinXP. I doubt that it could be server issue. I would say WU simply isn't designed for so many updates.

WU saves it's information in database: \Windows\SoftwareDistribution\DataStore\DataStore.edb. Sysprep will delete the complete \Windows\SoftwareDistribution folder, so the next time that huge database needs to regenerated again. This huge database can on a low RAM PC (< 4GB) cause a lot slow pagefile usage.

I have absolutely no idea were this "26" is coming from, but good it's working now.

Hirens BCD is Warez and we don't discuss nor support this here. With vague, I mean what the exact error text that shown? Direct install from CD is very different from the setup WinNTSetup does.

@Atari800XL Yeah, you not alone with this problem. The Windows Update Service is besides Windows Installer, WMI, .Net Framework, Component System and Driver Store, one of the most pathetic implementations in Windows, one I can think of. However after installing KB3083710 and KB3102810 the initial search takes less than an 30 minutes here, what's okay for me, creating new sysprep images every couple of month. @Affiliate60 First, don't don't use Hirens BCD! Second, msgbox with "26", it to vague For your recovery DVD: if it detects the edition wrong it's certainly not good sign.

In this case it should be better you launch it with a cmd file. WinNTSetup_x64.exe NT6 -silentshutdown -r -t 0rem wpeutil reboot

Yeah, 30 seconds is the quite long default timeout that MS choosed. Next version will add an option for that.