We are all aware of the various tools there are, there isn't a need to redistribute them into a huge file when all you can do is just post the links to them to the original source, or if there was a need to make them compatible with ventoy, all that needed was to post those links separately (host those files individually) and not make a giant mess just because you find it catered to your needs and think that you need every tool at your disposal. If I am correct her initial work/project started as a continuation of Hiren or Gandalf's, and continue to distribute the winpe. So is it necessary for everyone to download this huge file considering all that? Let's say, I'm only interested in her work Medicat Winpe. Yeah they can be useful, and are useful for a lot of people but not for everyone. Or would have heard of them or would ever use them. Contains a lot of tools not your everyday Joe might be needing. Which is all good and fine to an extent as an initial release.īut it's goddamn freaking big still. Now once all of that has been done, she decided to distribute her entire usb turning it into an image. Which is what Jayro has done, for herself first and foremost. Regardless, all of that work only consumes time. And I know, some of the various tools in this release need to be made after installing some software or the other or you could download a bootable from some not-so-shady site. If they want to add more to it, all they need to do is download more ventoy compatible distros or make them ventoy compatible themselves. Once an OS or tool is compatible with ventoy users can just download that image file in the form of wim or iso download ventoy and make their own USB. The aio bootloader, giving the ability to boot multiple types of OSes and tools, as long as they are ventoy compatible. This whole distro is based and made through ventoy. What's more versatile for everyone (and I mean everyone), both intermediate to advanced users into all this shmitz. Only the efi partition mounts correctly not the actual medicate (NTFS) partition. The previous bin file mounted correctly but this one doesn't. How does ventoy use ventoy_vhdboot.img if it isn't called by the *.Tried and tested multiple times. Do you use the boot conf replace & menu extention options? Right now when I press the F6 option at the Ventoy menu, the ventoy_grub.cfg menu setup only flashes briefly. I made a VHD of medicat (GPT, Ventoy 1.77, NTFS).Īre you using a ventoy_grub.cfg for booting vhd(x)s. How does ventoy use ventoy_vhdboot.img if it isn't called by the *.cfg file? I went back to using mbr, fat & exfat for the ventoy disk.Īre you using a ventoy_grub.cfg for booting vhd(x)s. data partition with NTFS the 1mb space after the efi partition is lost. How do you format a ventoy usb with NTFS and keep the correct ventoy partition layout? When I format the 1st. Tried the Windows 7 ventoy_vhdboot.img (different failure) Medicat installed directly onto the USB disk boots fine Ventoy (GPT) installed directly onto the USB disk boots fine The medicat VHD boots successfully in VirtualBox Info: The application or operating system couldn't be loaded because a required file is missing or contains erros. On boot the Ventoy menu appears, but when I select the medicat target I get an error and am unable to boot: I put the medicat.VHD on the Ventoy USB disk, created a /ventoy folder, and put the Windows 10 ventoy_vhdboot.img into the /ventoy folder. I then created a Ventoy 1.77 USB disk (GPT, NTFS). I made a VHD of medicat (GPT, Ventoy 1.77, NTFS).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |