Jump to content

wimb

Developer
  • Content Count

    873
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

27 Excellent

About wimb

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

5,802 profile views
  1. I don't think that VHD_WIMBOOT can reduce the build time on USB Flash Drive. I suggest to use Samsung Portable SSD T5 500 GB instead, so that your problem is gone ....
  2. Until now no problems found Tested with Fixed 2 partition VHD type MBR - BIOS / UEFI with Mini 7/8/10 x64 UsedSize 2 GB for booting with UEFI Grub4dos or UEFI Grub2 from RAMDISK. Menu entries for Mini 7/8/10 x64 in VHD as UEFI RAMOS \EFI\grub\menu.lst title Boot /2MU_10.vhd - UEFI Grub4dos SVBus RAMDISK - 3 GB find --set-root --ignore-floppies --ignore-cd /2MU_10.vhd map --mem --top /2MU_10.vhd (hd) chainloader (hd-1) title Boot /2MU_7.vhd - UEFI Grub4dos SVBus RAMDISK - 3 GB find --set-root --ignore-floppies --ignore-cd /2MU_7.vhd map --mem --top /2MU_7.vhd (hd) c
  3. You are right, indeed the GPT - UEFI type VHD has 2 partitions with hidden FAT32. My remark was wrong and is removed by strikethrough. Indeed the MBR - BIOS / UEFI type is booting in MBR BIOS mode from Windows Boot Manager as FILEDISK. My remark was not clear, but I meant to say that this type of VHD does not boot with MBR Grub4dos from RAMDISK. The MBR - BIOS / UEFI type VHD is bootable with Grub4dos from RAMDISK when the menu.lst entry takes into account that file bootmgr is on second partition. It is my fault and this boot problem can be solved easily
  4. Continued testing version 4.5.0 Beta 3 for booting Mini 10x64 in VHD as UEFI RAMOS MBR - BIOS Fixed and Dynamic VHD fail with UEFI Grub2 and UEFI Grub4dos as expected since VHD internal EFI folder is missing GPT - UEFI Fixed VHD booting OK with UEFI Grub2 and UEFI Grub4dos GPT- UEFI Dynamic VHD fail with UEFI Grub2, but booting OK with UEFI Grub4dos WinNTSetup GPT UEFI VHD's don't have internal EFI folder, but can boot UEFI RAMOS VHD_WIMBOOT GPT 1 Partition VHD have internal EFI folder which is required to boot UEFI RAMOS How come this difference ? GPT - UEFI type VHD has
  5. Did already some tests with VHD new type MBR - BIOS/UEFI and Mini 10x64 UsedSize 2.1 GB as UEFI RAMOS - Fixed VHD booting OK with UEFI Grub2 and with UEFI Grub4dos - Dynamic VHD booting fails for UEFI Grub2 (loading into RAM stops at 82%) and booting is OK for UEFI Grub4dos Your program is so powerful that Microsoft Defender decides to remove it immediately when VHD Create finishes. (Trojan etc ...) Until now no problem with 0x0 error ...
  6. Update VHD_WIMBOOT-50 Download: from wimb GitHub - VHD_WIMBOOT-50-E and SVBus-signed_2-E.zip Download File E = Encrypted PassWord = bootwimb and SVBus PassWord = reboot.pro Manual: VHD_WIMBOOT.pdf and More Info at reboot.pro USB_FORMAT Tool and UEFI_MULTI and VHD_WIMBOOT Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver !! otherwise wimlib and Boot errors will occur ..... - Update UEFI Grub2 and Grub2 FileManager - Update UEFI Grub4dos (= Grub4efi Or G4E) which adds support for GPT layout of VHD for
  7. Yes, indeed Fixed VHD with GPT layout as made with WinNTSetup works OK for all cases of UEFI RAMOS Booting of UEFI RAMOS tested with UEFI Grub2 or latest UEFI Grub4dos from internal SSD or from USB SSD. In this case there is no VHD internal EFI folder and this is working OK. GPT - UEFI type VHD has hidden FAT32 partition that contains EFI folder. VHD with GPT layout is not suitable for booting with MBR Grub4dos from RAMDISK using SVBus driver. Do you have a solution for the error that in some cases VHD Create fails to assign drive letter to the new Fixed type VHD ?
  8. New official release of UEFI Grub4dos available ....
  9. Thank you for the new version 4.5.0 Beta 2 In general one can say that WinNTSetup 4.5.0 Beta 2 in normal use is working OK now However in some cases VHD Create fails to assign drive letter to the new Fixed type VHD. Also I tried to use the New Created Fixed VHD's for booting in UEFI mode from RAMDISK using UEFI Grub2 Or UEFI Grub4dos and using signed SVBus driver. It turns out that the Fixed VHD's created and Applied with WinNTSetup are not compatible with UEFI RAMOS booting, probably since VHD internal EFI folder is missing ... For UEFI booting from RAMDISK the mo
  10. Fragmentatition does not matter with SSD, but fragmentation can matter for booting when VHD file itself is fragmented .... UEFI RAMOS requires Fixed VHD.
  11. I think Fixed VHD is preferred and should stay as recommended. - Dynamic VHD will as it grows gradually results in fragmentation of the VHD file itselves which is undesired behaviour. - Fixed VHD is needed for the very new UEFI booting from RAMDISK using UEFI Grub2 and UEFI Grub4dos
  12. That is not the point that my remark was about. My point is: (probably due to the fact that my normal OS is running in VHD instead of partition) Just when I start WinNTSetup then the hidden EFI drive of GPT partitioned disk is Not automounted anymore as drive Z: and the Boot Drive is not autoselected as that drive Z: anymore. This has nothing to do with creating VHD. In my case I have OS in existing VHD located on GPT SSD with Hidden EFI drive as Boot Drive Also In Create VHD the Fixed size (recommended) option is not preselected as default option anymore.
  13. Hidden EFI drive is not automounted anymore in 4.5.0 Beta 1 That means it is not easy to select the Boot Drive for install on GPT partitioned disk. Previous versions auto give Boot Drive is Z: as the automounted hidden EFI drive. In Create VHD the Fixed size (recommended) option is not preselected as default option anymore.
  14. Update VHD_WIMBOOT-47 Download: from wimb GitHub - VHD_WIMBOOT-47-E and SVBus-signed_2-E.zip Download File E = Encrypted PassWord = bootwimb and SVBus PassWord = reboot.pro Manual: VHD_WIMBOOT.pdf and More Info at reboot.pro USB_FORMAT Tool and UEFI_MULTI and VHD_WIMBOOT Always Shut-Off AntVirus Software and Disable Windows Defender when working with signed SVBus driver !! otherwise wimlib and Boot errors will occur ..... - Update Grub2 to latest version - Added Checkbox Update G - Forces Update of UEFI Grub2 and UEFI Grub4dos and MBR Grub4dos Boot f
  15. Done ! Update USB_FORMAT-52 and UEFI_MULTI-52 and VHD_WIMBOOT-44 Download: from wimb GitHub USB_FORMAT-52 and UEFI_MULTI-52 and VHD_WIMBOOT-44 Download File E = Encrypted Password = bootwimb Manual: VHD_WIMBOOT.pdf reboot.pro is alive again ....
×
×
  • Create New...