Winntsetup exe8/20/2023 ![]() ![]() Be on the lookout for bloated stuff, keep it small, keep it simple, and focus on deployment only.ini rather than batch, and other way around ini configuration as well as in the command-line. make available the same options in the.All of them, because on some computers, the latest PE does not work, so try to maintain a PE2 (Windows Vista) To PE10 and beyond always make it compatible with WinPE, cause that is where it will be used the most.Some points to look out for, and my humble two cents: If this is a normal behaviour, a suggestion might be to exclude the file in i386 if an external one is applied.Īlso, I would like to say that your application is the best and does not need any kind of change. It only worked when there is no winNT.sif in i386. I've tried it 3 times, and it is the same. ![]() Sometimes it applies the file in i386, otherwise the external one. ![]() ![]() If I already have a winNT.sif in XPDir\i386\, and trying to add an external winNT.sif or winNT.txt, the result is strange and unstable. I think something is wrong withour XP deployment. If I do this 10 times a day, should I do it manually? I'm the only one who requested because I am the only one that actually uses it every day, and some times more than once a day. same instance of winntsetup.exe, load 10-user.ini which contains image, unattend and OEM paths different than the 7-admin.ini.insert new HDD for windows 10 deployment.open winntsetup.exe, load 7-admin.ini for virtual machine testing. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |