Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

wimb

Developer
  • Posts

    883
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Netherlands

About wimb

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

6,369 profile views

wimb's Achievements

29

Reputation

  1. Thanks for version 4.6.0.1 WofCompress is running fine now in separate command window. Mouse Left click = Pause and Esc Or Right Click = Continue Ctrl + C = Stop Very useful for Offline Windows to Reduce Used Size
  2. Right click and select Compact Windows option and then with Comprimeren ... nothing happens Something wrong ?
  3. Thank you, Everything is working OK
  4. Thanks for New WinNTSetup 4.5.0 version Thanks for adding Hidden feature in VHD Partition style to adjust size of FAT32 Part (sorry, but at first sight I did not see it in RC3 ....) The VHD FAT32 Part Size can be initialized in WinNTSetup.ini file [vhd] section using value bootpartsize=100 An improvement of WinNTSetup program could be that Settings as used in VHD dialogue will be saved in WinNTSetup.ini file when using Save ini from menu. It would be interesting in that case to Save in [vhd] section the selected VHD Partition style (MBR BIOS/UEFI vs MBR - BIOS vs GPT - UEFI) and Save VHD hard disk format (Fixed vs Dynamically expanding) and bootpartsize (Size of VHD FAT32 Part)
  5. Ok, in my case Porteus sound is working fine. Just see that reboot.pro is on line again ....
  6. @alacran In your improved menu there is an error in MBR grub4dos menu where Slacko64-7.0 is used instead of Slacko64 See rule initrd /Slacko64-7.0/initrd.gz In my case Puppy Linux slacko64-7.0 fails to boot from a folder on USB and I finish with # command line .... Xorg Wizard For small size Linux then Porteus-x86_64 315 MB file Porteus-CINNAMON-v5.0rc1-x86_64.iso copied as Porteus.iso in folder images on FAT32 U-BOOT UEFI_MULTI supplies menu entries for this solution including persistence if desired ....
  7. I have no info on why reboot.pro is offline again .... Thanks for detailed and improved menu entries to boot Puppy Linux slacko64-7.0 from USB
  8. Update USB_FORMAT-57 and UEFI_MULTI-57 plus the Addon-agFM files Download: from GitHub USB_FORMAT-57 and UEFI_MULTI-57 Download File E = Encrypted Password = bootwimb Manual: VHD_WIMBOOT.pdf and Win10_Install.pdf - Update UEFI Grub2 - latest 2021-02-02 - Update UEFI Grub4dos (= Grub4efi Or G4E) - grub4dos-for_UEFI-2021-01-31.7z - Update Grub4dos - grub4dos-0.4.6a-2021-01-27.7z
  9. Update VHD_WIMBOOT-52 Download: from wimb GitHub - VHD_WIMBOOT-52-E and SVBus-signed_2-E.zip Download File E = Encrypted PassWord = bootwimb and SVBus PassWord = reboot.pro Manual: VHD_WIMBOOT.pdf 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 - latest 2021-02-02 - Update UEFI Grub4dos (= Grub4efi Or G4E) - grub4dos-for_UEFI-2021-01-31.7z - Update Grub4dos - grub4dos-0.4.6a-2021-01-27.7z - Update VHD_WIMBOOT - improved display of Drive Info
  10. May be Size of Hidden FAT32 drive can be reduced to 100 MB for MBR - BIOS/UEFI and GPT - UEFI types of VHD. Now it is 500 MB which is relatively large and a waste when loading e.g. a 3 GB VHD to RAMDISK for booting with UEFI Grub2 or UEFI Grub4dos.
  11. 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 ....
  12. 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) chainloader (hd-1) title Boot /2MU_8.vhd - UEFI Grub4dos SVBus RAMDISK - 3 GB find --set-root --ignore-floppies --ignore-cd /2MU_8.vhd map --mem --top /2MU_8.vhd (hd) chainloader (hd-1) \grub\grub.cfg menuentry "Boot /2MU_10.vhd - UEFI Grub2 SVBus RAMDISK - 3 GB" { search --file --set=vhd_drive --no-floppy /2MU_10.vhd map --mem --rt ($vhd_drive)/2MU_10.vhd boot } menuentry "Boot /2MU_7.vhd - UEFI Grub2 SVBus RAMDISK - 3 GB" { search --file --set=vhd_drive --no-floppy /2MU_7.vhd map --mem --rt ($vhd_drive)/2MU_7.vhd boot } menuentry "Boot /2MU_8.vhd - UEFI Grub2 SVBus RAMDISK - 3 GB" { search --file --set=vhd_drive --no-floppy /2MU_8.vhd map --mem --rt ($vhd_drive)/2MU_8.vhd boot }
  13. 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
  14. 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 hidden FAT32 partition that contains EFI folder. The main difference is the number of Hidden Sectors which is 2048 in case of WinNTSetup created VHD and 128 in case of VHD_WIMBOOT VHD created with diskpart. (wrong conclusion strikethrough) WinNTSetup New type MBR - BIOS / UEFI Fixed VHD are quite interesting for MBR and UEFI RAMOS as having 2 Partitions layout given by MBR (NTFS + Hidden Active FAT32) Problem is that this type of VHD does NOT boot in MBR BIOS mode probably since FAT32 has partition type EF which should be 0C to be compatible with MBR booting Changing partition type to 0C is not enough, this VHD still does NOT boot in MBR BIOS mode with Grub4dos from RAMDISK. EDIT: Added Grub4dos from RAMDISK in: VHD still does NOT boot in MBR BIOS mode with Grub4dos from RAMDISK Sure this VHD with MBR - BIOS / UEFI type is booting in MBR BIOS mode from Windows Boot Manager Menu EDIT2: The MBR - BIOS / UEFI type VHD is bootable with Grub4dos from RAMDISK when the menu.lst entry takes account that file bootmgr is on second partition. So this boot problem can be solved easily VHD_WIMBOOT Fixed 2 Partition VHD has layout MBR ( Active FAT32 + NTFS) that can be used for booting with MBR Grub4dos and UEFI Grub4dos and UEFI Grub2 from RAMDISK In case drive Y: is used already then Create VHD fails to assign drive letter to the created VHD May be this can be improved by using other drive letter in case of conflict. In any case WinNTSetup 4.5.0 Beta 3 is very good program to create various types of VHD that can be used for UEFI RAMOS
  15. 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 ...

×
×
  • Create New...