![]() 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.The same script could install the WinPE drivers from the extracted folders in the X: drive if WinPE did not automatically use them from the DriverStore folder. You can load an XML file using Ventoy and the XML file could contain a RunSychronous entry to start the install script or use the VentoyAutoRun.bat file which is inside your zip file. Or you could use WinntSetup.exe to do the (scripted or GUI) install with drivers. cmd file to install from one of the images in the install.wim (after partitioning and formatting the disk) and then copy over the drivers or use a DISM command to add in offline drivers. zip file would have the same folder structure.Īs for the installed OS - you would need to avoid running Setup.exe and use the WinPE environment and a. ![]() ![]() I am not sure but I think they would need to be in DriverStore folders so your. ![]() Well, you can inject the drivers into the winPE OS by adding a zip file which contains the drivers so that they appear in the correct folder. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |