SteveSi Posted January 28, 2019 Share Posted January 28, 2019 Hi I can successfully specify an ISO (Dual architecture) and an XML file like this: "%wpath%\WinNTSetup%pp%.exe" NT6 -source:"%MYISO%" -wimindex:"2" -unattend:"ZZDANGER_Auto_WipeDisk0_Win10ProUK_with_SDI_CHOCO.xml" however, I am trying to load an ISO and use a cfg (.ini) file like this: "%wpath%\WinNTSetup%pp%.exe" NT6 -source:"%MYISO%" -cfg:"WinNTSetupHome.ini" but it seems to always select Pro even though if I manually use ctrl+L to load the ini file, it selects Home. Is this combination supported? Link to comment Share on other sites More sharing options...
click-click Posted January 28, 2019 Share Posted January 28, 2019 (edited) I noticed up to 3.9.1 the enabled=0 in the diskpart directory was the default and now it is enabled=1. What happens if you accidentally do a CTRL+SHIFT+D when the GUI is active? Edited January 28, 2019 by click-click Link to comment Share on other sites More sharing options...
SteveSi Posted January 28, 2019 Share Posted January 28, 2019 It prompts you nicely - there is little danger. Try it! Link to comment Share on other sites More sharing options...
JFX Posted January 28, 2019 Author Share Posted January 28, 2019 1 hour ago, SteveSi said: Is this combination supported? No, if you set source in command line you must set wimindex there too. Link to comment Share on other sites More sharing options...
SteveSi Posted January 28, 2019 Share Posted January 28, 2019 (edited) OK, but I still cannot get it to work. I want to specify an ISO and a cfg file. How can I do it? You see, using the iPXE wimboot utility, it is possible to use grub2 or grub4dos to boot from an unmodified Windows Install ISO, and automatically run WinNTSetup by injecting a winpeshl.ini and batch file. So we can specify an XML and ISO and other parameters . I am trying to also specify a .cfg file as well as the ISO source file. Edited January 28, 2019 by SteveSi Link to comment Share on other sites More sharing options...
JFX Posted January 28, 2019 Author Share Posted January 28, 2019 WinNTSetup_x64.exe NT6 -source:%MYISO% -wimindex:1 -cfg:WinNTSetupHome.ini should do exactly that. Link to comment Share on other sites More sharing options...
SteveSi Posted January 28, 2019 Share Posted January 28, 2019 That's odd! It is working now! Is the order of the parameters important? I am sure I tried that before many times! Link to comment Share on other sites More sharing options...
JFX Posted January 28, 2019 Author Share Posted January 28, 2019 No order does not matter, expect NT6 must be first one. 1 Link to comment Share on other sites More sharing options...
SteveSi Posted January 28, 2019 Share Posted January 28, 2019 (edited) Sorry, one more Q. You say if a WinNTSetup.ini file exists it will be used by default. Does that apply even if specifying the NT6 parameters on the command line but without a -cfg parameter? Edited January 28, 2019 by SteveSi Link to comment Share on other sites More sharing options...
JFX Posted January 28, 2019 Author Share Posted January 28, 2019 Yes, a ini is always loaded if found. Either Winntsetup.ini or the one specified by -cfg parameter. Link to comment Share on other sites More sharing options...
click-click Posted February 28, 2019 Share Posted February 28, 2019 I would like to use WinNTSetup to install Win7 on a VHD that was defined for a VM in Oracle's VirtualBox. Is there a way to do this? If I mount the vhd on my local system, WinNTSeup wont' let me use the same drive letter for the boot drive. Seems like VBOX supports booting from a VHD. Link to comment Share on other sites More sharing options...
JFX Posted February 28, 2019 Author Share Posted February 28, 2019 What you mean with "won't let you"? It should display a warning, but let you continue. Link to comment Share on other sites More sharing options...
click-click Posted February 28, 2019 Share Posted February 28, 2019 Oooops. I didn't bother to hit OK and kept using Cancel. Link to comment Share on other sites More sharing options...
yaschir Posted April 11, 2019 Share Posted April 11, 2019 Please, can you add this Turkish language prepared by me for WinNTSetup v3.9.3.1? Best regards. Link: https://yadi.sk/d/R1F6qdjW3QtE8g 2 Link to comment Share on other sites More sharing options...
alacran Posted April 23, 2019 Share Posted April 23, 2019 On 5/4/2016 at 6:45 AM, JFX said: 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. Hi JFX: I think I saw a single file download for "Recompress Compact OS" for 7 and 8.x, some time ago, but I can't find it, maybe it was lost during server crash, do you still have it? alacran Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now