Jump to content

steve6375

Member
  • Posts

    95
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

About steve6375

Contact Methods

  • Website URL
    http://www.rmprepusb.com

Profile Information

  • OS
    Windows 7 x64

Recent Profile Visitors

2,944 profile views

steve6375's Achievements

2

Reputation

  1. Thanks! That's fixed it. P.S. Ctrl+Shift+D is still not mentioned in the F1 Help pop-up text.
  2. 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!
  3. 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
  4. 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?
  5. 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!
  6. 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!
  7. 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)
  8. Thanks! P.S. Ctrl+Shift+D and enabled=1 is not documented in the F1 help though...
  9. 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!
  10. 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)?
  11. 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).
  12. 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.
  13. 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 ?
  14. 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?
  15. 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??)
×
×
  • Create New...