Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Donations


JFX last won the day on August 18 2020

JFX had the most liked content!

Community Reputation

171 Excellent

About JFX

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

10,064 profile views
  1. WinNTSetup 4.5.0 RC1 - ini option BootMountExclude supports Vendor name - fixed VHD drive letter assignment - fixed Windows 7/8 compatiblity
  2. They have an EFI folder on the second partition. Hidden Sectors should be equal to diskpart now. Both use the offsets from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vds\Alignment I guess this is a Grub problem, they booting attach to VMWare in BIOS and UEFI mode.
  3. WinNTSetup 4.5.0 Beta 3 - fixed VHD Creation system default partition alignment - increased VHD creation volume arival timeout - set errorcode in case hitting volume arival timeout - fixed instant VHD creation cylinder bug - new default VHD creation type MBR - BIOS/UEFI - added VHD command line options /gpt and /mbr
  4. It's properly the timeout I set. It's currently waiting only 500 ms for the newly created volumes be recognized by the OS. I really should do something about error 0x0 message.
  5. You could try the fixed VHD with GPT layout for your UEFI RAMOS. Indeed, with the new VHD function the "system default" for alignment currently don't work and uses biggest value of 4096 hidden sectors.
  6. WinNTSetup 4.5.0 Beta 2 - removed NT5 uxtheme patch - fixed mounting boot partition regression - improved bootice darkmode
  7. Replace these 2 in C:\Windows\System32\drivers VMware-workstation-full-16.1.0-17198959.exe\VmciSockets.cab\vmci.sys_Vista.20BE52C5_0815_4F26_9816_FB06A9A9F012 VMware-workstation-full-16.1.0-17198959.exe\USB.cab\_driver_hcmon_sys_win7_x64.AB568CC9_1F06_4225_B985_9531B0D3BB56
  8. Fragmentation does not matter with SSD and recommending something that writes multiple GB on a flash disk would be wrong.
  9. Ah, found it. It's about structure alignment for 1 call it needs a 4 byte padding at the end and for the other it don't. For VHD creation, yes the default type has changed. I'll remove the recommend.
  10. @graphixillusion I don't think there will be much use of it. If anyone really wants this there is diskpart or bootice. @wimb Yes, as 4.5 now always creates the VHD internal boot files depending on partition style, I thought it would not be necessary to give it a drive letter. Do you need one?
  11. VMware-workstation-full-16.1.0-17198959.exe\Workstation.cab\_driver_vmx86_sys_Win8 --> C:\Windows\System32\drivers\vmx86.sys
  12. Download links are shared folder that include older version. If I have some time I'll make an XP special version with delta patch for the lost ADK files.
  13. WinNTSetup 4.5.0 Beta 1 - Dropped 32-Bit version, system requirements are now Windows 7x64 + - VHD functions no longer uses diskpart.exe - VHD Attach / Detach supports ISO files - VHD Creation supports GPT Partitionsttyle - VHD Install will always create internal boot files depending on partition style - Fixed open file dialog pattern not working on default WinPE 3.x + - Fixed wimgapi capture build number on H2 Systems (19041 instead 19042) - Support multiple "-regtweaks" cmdline switches - DPI-Awareness for Imdisk - Darkmode and DPI-Awareness for Bootice - Workaround
  14. RemoveObsoleteDosDevices will not remove existing mounted boot partitions. It thought for removable USB or VHD disks. For the mounted ImDisk ISO files, by default they should be removed in v425. (KeepISOAlive=0) Not sure why it doesn't work for you. If you do not have imdisk installed try WinNTSetup's system menu --> imdisk and see if you can unmount them there.
  15. Yes, when v421 exit it did scan for mount points that have no valid target anymore. But this caused trouble with VMWare mounted drives. I have improved that function, but it's still disabled by default. You can set it in the ini file: [Options] RemoveObsoleteDosDevices=1
  • Create New...