• Content count

  • Joined

  • Last visited

  • Days Won


JFX last won the day on June 6 2015

JFX had the most liked content!

Community Reputation

58 Excellent

About JFX

  • Birthday

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

3,153 profile views
  1. Yes, you can use a VHDX. But I don't know about about trim support. Microsoft is only talking about the new Hyper-V Generation 2 emulation that supports it. They did not mentioned native VHD(X) boot. VHD and VHDX use the same driver and it's the drivers job to tell the OS that VHD(X) is located inside a SSD. It should than pass through the trim command. So I would guess both or neither formats support trim.
  2. It are just the offset inside the ISO like jaclaz explained. I've made tool for that: ISO2Offset.7z
  3. Have added command line support for range downloads. GWT -range:8808448-9236127 -out:"X:\bootmgr" -title:"Download Win8.1 Bootmgr" -link:/download/B/9/9/B999286E-0A47-406D-8B3D-5B5AD7373A4A/9600.16384.WINBLUE_RTM.130821-1623_X86FRE_ENTERPRISE_EVAL_EN-US-IRM_CENA_X86FREE_EN-US_DV5.ISOGetWaikTools.zip
  4. I would use curl and a Win8.1 Enterprise ISO. curl -o"bootmgr" -r 8808448-9236127 http://care.dlservice.microsoft.com/dl/download/B/9/9/B999286E-0A47-406D-8B3D-5B5AD7373A4A/9600.16384.WINBLUE_RTM.130821-1623_X86FRE_ENTERPRISE_EVAL_EN-US-IRM_CENA_X86FREE_EN-US_DV5.ISO
  5. Yes, registry permissions are no problem. For me the SearchOrderConfig tweak Atari800XL mentioned is enough, but maybe that has changed once again.
  6. Yes, the folder you select will be recrusively scanned for *.inf files. However Dism will create a driver package for every inf file, so don't add too many.
  7. Hi ilkertezcan, 1) It's no bug, I'm going to remove support for WinNTSetup_x86.exe running on x64 OS. Reason: There are some API's that can not work in WoW64 emulation, I though i could find a good solution, but it would just makes thinks to complicated. Also there is an faster x64 version available, don't know why sp many people want to run the x86 version. 2) Good, will add it to help. 4) Not so sure I like to add that.
  8. Hi Sergei, The name comes from the XML of the WIM file. <DISPLAYNAME> is used. If this does not exists than <Name> is used. See: imagex -info wimfile.wim
  9. Good, the ini option would be: [WinNT6\READY] BootSect=0 But better you set all GUI options and create a new ini file.
  10. Your log file is from version, the bug should be already be fixed in the current version.
  11. Log file is in the ?:\Windows\WinNTSetup.log. How you disable the bootsector update, command line or ini file?
  12. During setup or during WinNTSetup ? In case WinNTSetup update the bootsector, it will be logged in the logfile. I tried with Terabyle MBR.exe utlility, that add Press F?? Key boot option. Works with NT6.x installs.
  13. @click-click Tweaks are now read and save from the new ini sections [WinNT5\TWEAKS] and [WinNT6\TWEAKS] Same with bootsector and BCD stuff [WinNT5\READY] Yes, it breaks old ini files, but makes it easier to edit then with an editor.
  14. Any chance to get the new context menu option of SIB 2.0 also for ONE?
  15. Seems to happen whenever one clicks on a transparent pixel of the startbutton.