Make a binary comparison that compares the contents of the files and not the creation dates. You get a folder "ventoy.disk".Ħ/ With a file comparison application (filesync, Syncovery.), compare the contents of the "ventoy.disk" folder with the contents of the "VTOYEFI" partition of MEDICAT. you get a file "".ĥ/ Extract the contents of the file """" with 7-Zip or WinZip. You get a folder containing 3 folders "boot", "plugin", "ventoy" and the "ventoy2disk" file.Ĥ/ Decompress the file "" with Winrar (or other). To update Ventoy in MEDICAT, under Windows 10 :ġ/ Download the latest version of Ventoy "ventoy-1.0.25-windows.zip" at: Ģ/ Decompact the archive. It is a method intended to upgrade "ventoy" on a MEDICAT usb key created according to the recommendations of JAYRO (with PassMark ImageUSB 1.5 Build 1003). I propose a method that I have just applied and that works well. In this case, you have to copy the SSTR folder to the root of the MEDICAT partition. but clicking on "Install" would destroy the structure of MEDICAT.Īs far as Sergei Strelec's ISO is concerned, I find it excellent and I added it on my MEDICAT USB key. The "update" option is therefore not available. MEDICAT partitions are not recognized by Ventoy2Disk.exe as "Ventoy" partitions. I find Sergei Strelec's implementation more than enough for my use Thank you for taking the time to answer me. this is just a guess on my part since I have no plans to download a 25gB USB installation like Medicat. If the developer has all his software on Partition #1, the upgrade should go smoothly since all his visual customization will be located at the ROOT of his DATA partition (Part#1) which does not get affected during an upgrade.īe forewarned. I would copy your "master" Medicat USB and try a standard VENTOY upgrade on the copy, if it's offered. How does ventoy use ventoy_vhdboot.img if it isn't called by the *.(10-11-2020, 01:42 PM)FroggieTheGremlin Wrote: From viewing Medicat's screen shots, it looks like a "standard" VENTOY installation. 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 |