![]() ![]() ![]() This is the structure of my USB-Stick (first partition): I shut the system down and restart it from the stick, again I'm asked about using persistence and I agree: But all modifications are gone, no persistence. ![]() The systems start and I apply some modifications on the desktop (arrangement of icons, clock settings). Booting kUBUNTU or KDEneon from the stick, I'm asked about using persistence and I agree. below) was checked and after booting the stick, F5 Debug > Persistince reports OK. The USB-Stick was created with ventoy 1.0.14 from an kUBUNTU (18.04)-PC. It is a method intended to upgrade "ventoy" on a MEDICAT key created according to the recommendations of JAYRO (with PassMark ImageUSB 1.5 Build 1003).I have no success to get persistence for some actual UBUNTU-based distribution. Only some files differ.ħ/ Update the files in the "VTOYEFI" partition with the files different from "ventoy.disk".ġ/ Launch RMPrepUSB (or MobiliveCD or other virtualization program).Ģ/ Check that the main MEDICAT partition is detected.ģ/ Click on the button on the right "Test using QEMU Emulator (F11)".ĥ/ Check the Ventoy version in the top left corner. 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 the "boot", "plugin", "ventoy" and the "ventoy2disk" file.Ĥ/ Decompress the file "" with Winrar (or other). I propose a method that I have just applied and that works well.ġ/ Download the latest version of Ventoy "ventoy-1.0.25-windows.zip" at: Ģ/ Decompact the archive. To update Ventoy in MEDICAT, under Windows 10 : Une fois que tu as créé ta clé de mise à jour, démarre dessus, branches ta clé Medicat, et suis les instructions pour mettre à jour. Like this Theme gets spoiled when resolution is changed. So other bigger resolution is selected although I have set fixed 1024 x 768 in ventoy.json. But in some computers 1024 x 768 resolution is not available. Si ton ordinateur ne peut pas démarrer en UEFI, alors flashes l'image ISO avec Rufus en mode DD. 12-18-2022, 06:52 PM Hello longpanda ventoy I have designed my theme for 1024 x 768 resolution. Si ton ordinateur peut démarrer en UEFI, alors tu formates une clé (pas celle de Ventoy !) en FAT32, et tu extraies le contenu de l'ISO sur la clé. Les instructions sont à cette adresse : (tu peux ignorer la section « Usage 2 » si tu ne veux pas faire la mise à jour via VMWare).Įn résumé, tu télécharges l'image ISO, puis tu as deux options pour créer la clé qui va te servir à faire la mise à jour : Dans ce cas, le plus simple c'est de mettre à jour Ventoy via l'ISO live que le dév' met à disposition ici : Windows peut parfois être capricieux avec Ventoy, visiblement. ![]() The latest version of the program changes that, as you do get an option now to keep the data on the device. Up until now, Ventoy deleted all data on the USB device when you selected the install option in the application interface. In this case, the easiest way to update it is via the live ISO provided by the developer here: Īnd here are the instructions: (you can skip the "Usage 2" section if you don't want to update via VMWare) Ventoy is a popular open source tool to create bootable media. Windows can be capricious with Ventoy apparently. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |