steve6375
Content Type
Profiles
Forums
Events
Posts posted by steve6375
-
-
hmmm, this is strange...
I have a USB fixed-disk drive with folder that has WinNTSetup_x86 and .\Tools\diskpart folder has ONLY enabled=1
Win 10 x64 OS - Ctrl+Shift+D works OK
Win10PE (boot from Win10 x86 ISO and press SHIFT+F10) - same USB drive - Ctrl+Shift+D does not work
but if I add enabled=1 and enabled=0 files are present - the Ctrl+Shift+D does work.Edit - Actually if I quit WinNTSetup in WinPE and then run it again it does work (with only enabled=1 file present).
So it seems that the first time you run it, it does not work...
I just retested it again.
- Fresh boot to WinPE from Win10 x86 ISO on a USB flash drive
- At Country\Language Select screen press SHIFT+F10
- In cmd console, run WinNTSetup_x86.exe -- Ctrl+Shift+D does not work
- Quit WinNTSetup and re-run it -- Ctrl+SHift+D now works!
0 -
I have WinNTSetup v3.9.0 and have renamed enabled=0 to enabled=1 but I cannot get ctrl+shift+D to work ??
Is it broken or is it me?
It seems to need both enabled=0 and enabled=1 files present now
0 -
Thanks JFX, the new GWT is smaller in size and does not trigger Windows Defender either.
Could you explain how one can work out the correct range to use for any given file please?
0 -
Thanks so much for the reply and the URL. That works great!
P.S. Unfortunately Windows Defender does not seem to like curl when I package it up though!
0 -
How would I go about downloading bootmgr from an official Windows 8.1 Install ISO (or any stable source) from a Windows command line?
The URL needs to be as stable as possible.
I have tried re7zip but it takes ages!
0 -
See http://www.msfn.org/board/topic/149612-winntsetup-v3871/?do=findComment&comment=1128738
ctrl-shift-D allows user to pick a diskpart script file and run it. It makes wiping, partitioning and formatting easy.
The file .\Tools\Diskpart\enabled=1 must be present for it to work (change enabled=0 to enabled=1)
0 -
Thanks!
P.S. Ctrl+Shift+D and enabled=1 is not documented in the F1 help though...
0 -
The .iso loading function seems to work OK for \sources\install.wim, but is does not work on ISOs containing .esd files.
Can it look for \sources\install.esd inside ISO files please?
Some Microsoft ISOs contain both 32-bit and 64-bit Install.esd files, so it also needs to look for \x86\sources\install.esd and \x64\sources\install.wim (and then ask which one you want to use)
Thanks!
1 -
What version of PE are you booting to?
How are you booting (from USB?)?
How did you make the USB drive (did you use the option: Rufus with Use Rufus MBR with BIOs IS and 0x80 as default)?
0 -
It does not matter what is in the XML file. I am using the XML files for Win10 that are included in Easy2Boot (I am the developer of Easy2Boot).
0 -
Personally, I also found the term 'Installation drive' confusing and had to double-check when I first saw those words.
MS refer to the volume containing the boot manager files as the 'system' drive and the volume containing the Windows OS files as the 'boot' drive - which is also really confusing (even the MS techs agree it is confusing!).
I think it would be clearer to say
'Select partition for boot files'
'Select partition for Windows files'
F1 help text could contain some text about 'The boot files and Windows files can both be placed on the same partition'
I don't know if it is possible, but when a drive letter is chosen and selected by the user, can the field say something like 'C: (disk0, partition 1)' instead of just C: - this would be helpful on multi-drive systems.
0 -
I prefer to manually reboot rather than tick the box to auto-reboot, so an option to reboot at the end of the Setup phase would be useful - also useful to reboot without needing to run setup successfully - or maybe add a hotkey to reboot and add help text. ;-)
I think if you warn the user before executing the diskpart script, then there is no need to disable it by default. Only advanced users (who know about SHIFT+CTRL+D) will use diskpart scripts anyway.
Some sort of tip or clue for the user about F1 should be present on the main forms somewhere - otherwise useful info is hidden from the new user.
P.S. If I accidentally set a .ISO file or some other random file as an Unattend file, it is accepted by the dialog box and the field is populated - could you check the extension is .XML ?
0 -
P.S. For backwards compatibility (videos, instructions on web sites, etc.) I think you should add back the right-click feature to select an ISO because it may confuse current users.
Also Help (F1) button would be useful for new users.
Exit button in Tweaks form would be more 'Windows' compatible.
Under Win10 x64 PE, ImDisk was not installed. How do you see users using ImDisk?
0 -
Thanks for Beta4. ISO selection is now much better.
re. diskpart - is ctrl+shift+D a secret key press? How would the user know to press this key (unless they read text inside the enabled=0 file) - not mentioned in F1 Help? Perhaps the 'F' button 'Show format dialog for this drive' Tool tips can also include the text 'Tip: Use Ctlr+Shift+D to run a diskpart script'.
What is harm in enabling it by default?
Also, after diskpart script .txt is selected, I think a warning would be best (in GUI mode) - e.g. 'WARNING: Diskpart can erase all data on a drive. OK to run this diskpart script now (xxxxxx.txt) - Yes/No/Edit' (Edit=Launch Notepad)
If diskpart script is run, Boot and Installation OS boxes should be cleared as drive letters will be changed.
P.S. another suggestion - a 'Reboot' option (perhaps after successful 'Setup' file copy has occurred), would be handy (e.g. wpeutil reboot or shutdown /t 3 /r depending on OS??)
0 -
P.S. Another useful addition would be a 'pick a diskpart script' option so we could pick a diskpart script text file and then run it
i.e.
Windows File Open dialog for *.txt, *.scr (??)
when file picked by user, run 'diskpart /s <file>' in command shell.
You could even provide some .scr files for standard situations with the download - e.g. disk0_MBR_1PTN_MAX.scr, disk0_MBR_20GB_plus_MAX.scr, disk0_GPT_MAX.scr, disk0_GPT_WinRE_Max_15GBRecovery.scr
0 -
sorry - double post!
0 -
sorry - double post!
0 -
sorry - double post!
0 -
I am using 3.8.6 and I find the ISO mount support confusing. I am booting to WinPE from a Windows 10 ISO. I spent about 30 minutes trying to discover if it could use an ISO file...
I was beginning to think that WinNTSetup could not mount ISOs because...
1. If I just left-click on the Search button, the 'Files of type' box lists 'Wim images (*.wim.*.swm,*.esd)' however the all files are listed in the file list (including .iso files)
2. The Files dialog has a title of 'Choose the install.wim file' - it does not mention .swm or .esd or .iso ?
3. If I left-click on the Search button and then right-click on an ISO file, I get a 'Mount' option - but this does not work and it says 'Sorry, there was a problem mounting the file' - I suspect that it only works under full Windows and not WinPE? Could it be suppressed if not supported by the OS?
If I manually install ImDisk under WinPE, then when I right-click on an ISO, I get a 'Mount as ImDisk virtual disk' option as well as the 'Mount' option. Could WinNTSetup automatically install ImDisk and give us this option?
4. If I left-click on the Search button and then right-click on an ISO file - why does WinNTSetup not mount the ISO in that same way that a right-click on the Search button does?
It would be much more logical if the Search button listed only *.wim, *.swm, *.esd and *.iso files - if a ISO file was selected, then mount and find the install.* file in the same way that a right-click on the Search button does.5. The help balloon for the Search button takes about 3 seconds to appear. This meant I did not see it because I always clicked on the button within 3 seconds. Could the help balloons appear immediately please?
Thanks for a great utility and I hope my comments help to improve it.
0 -
I am using an Unattend.xml file to install Windows 10.
My .cmd file requires internet access during the Specialize pass. Windows 8\10 contains the network driver for my ethernet adapter, so there is no problem there.
On Windows 8.1, this is no problem.
On Windows 10 TH2 (last third? version) this is no problem
On Windows 10 TH2 (first version) - there is no internet connectivity (e.g. ping www.bbc.co.uk does not work)
On Windows 10 Anniversary (first version) - there is no internet connectivity (e.g. ping does not work) - I did not test the second release of TH2.
In other words, Microsoft fixed the bug in TH2 but the bug is now back in the Anniversary build!
It seems that there is no host name set up in the 'bad' versions (e.g. ipconfig /all shows no host name).
I can 'fix' the problem by running msoobe for 10 seconds and then killing the task - I then get a host name and ping works.
Does anyone know a better way of getting internet connectivity to work during the Specialize phase?
0 -
AFAIK XP does not boot from UEFI systems. So why would you want to UEFI-boot to install XP?
0 -
-
You might like to also check out WinSetupFromUSB and Easy2Boot which can install 32-bit XP from an unmodified XP install ISO. It automatically adds the correct SRS Mass Storage Driver. No need to modify the ISO or add SRS drivers yourself.
Not as versatile as WinNTSetup, of course!
1 -
For installing from an ISO file (using a Removable USB Flash drive), for Win8 you need to specify a Product Key. E2B has a list of 'generic' keys and you just need to choose one of these. The generic keys won't activate, they just allow you to install. Once installed, you can enter your own correct key and activate Windows.
E2B also allows you to choose a 'NO KEY' option - this may work with some ISOs (it depends on how they were made and if they have more than one image in the install.wim file).
You can also choose the 0 - CHOOSE A PRODUCT KEY option and then the 0 Enter your own key option and manually enter your own key.
If you want MBR and UEFI installs, it is probably easier to just convert each ISO to a .imgPTN file using the MPI Tool Kit and MakePartImage. Your E2B USB drive can be formatted as NTFS and you can create FAT32 .imgPTN files using the MPI_FAT32 desktop shortcut. The video shows you how to do it. You won't need to enter a Product Key at an early stage and it will work from a USB HDD or a Removable USB drive.
Note that for UEFI-booting of Win7 64-bit, you will need to add an EFI boot file.
0
WinNTSetup v5.3.4
in Install Windows from USB
Posted
Thanks! That's fixed it.
P.S. Ctrl+Shift+D is still not mentioned in the F1 Help pop-up text.