Hello!

Venty has reached a maturity that allows to look beyond function and start polishing the usability. Thank you for the hard work! I wonder why nobody did that much sooner?

Here is one suggestion. Allow me to explain the background first.
Whether we throw our files all into one directory...

• rename the persistence file,
  
• rename the config file,
  
• and edit the names of persistence and config files in the global ventoy.jason.
  

1. Yentoy is enabled to automatically accept all files that belong to an image, if they are in the same folder with that image. That means its corresponding .dat, .cfg, .md5/.sha1/.sha256/.sha512 files.
   
2. And also, all image specific settings that are now in the global ventoy.json file could go into an image-specific config file in that folder.
   

• No corresponding files needs renaming. (Checksums have to be replaced anyway.)
  
• No edit necessary in global ventoy.json.
  
• No edit necessary in image-specific config file (if existent).
  

emoving an image now only requires that a directory is deleted. No editing ventoy.json necessary. (Of course, one could stay with the old way, and just leave ventoy.json untouched, if one loves the accumulating cruft. )

When installing Ventoy on USB with GPT and SecureBoot, upon first boot I need to install keys, just as explained on the website.
The second boot however does start up Ventoy correctly, but when selecting SystemRescue 9.01, and Grub starts, I get the following Grub error:

shim_lock protocol not found, you need to load the kernel first

Rebooting with secure boot disabled does not give the error, and boots SystemRescue successfully.
Booting with secureboot gives a black (?) grub screen, booting without secureboot gives a green (?) grub screen.

Does anyone know a solution on how to solve this that it will work under SecureBoot?

macbookpro 2017 13" 无touchbar

错误信息截图如附件

ventory1.0.73版本

Attached Files

Thumbnail(s)
   

• 2022/04/06 --- 1.0.73 release
  

1. Ventoy Subscription Service. Notes
   
   
2. A dialog will be popped up when you click install button if Ventoy already installed in the disk.
   Then you must enter YES in the text box manually to confirm the installation.
   
   
3. If the ISO file name is too long to displayed completely. You can press left or right arrow keys ← → to scroll the menu.
   
4. Add F5 Tools  --> Power --> Reboot to EFI setup  menu in UEFI mode, (reboot to UEFI BIOS Setup).
   
5. Add F5 Tools  --> Hardware Information  menu.
   
6. We can set menu tip position and color for per-theme. Notes
   
7. Prevent DLL search order hijacking for Ventoy2Disk.exe/VentoyPlugson.exe/VentoyVlnk.exe.
   
8. Fixed a bug that VTOY_LINUX_REMOUNT option does not take effect for Manjaro/Arch.
   
9. vtoyboot-1.0.21 release. Notes
   
10. languages.json update
    

In continuation of the topics: Backgrounds per backrest, Design ventoy mod_ventoy 1.0.70.

I imagine the modified  "Ventoy Menu Tip Plugin".
Except for the general parameters for all "tip": left, top и color.
Now you can set individual parameters for each hint: tipleft, tiptop и tipcolor.
Now the hint message can contain up to 7 lines: "tip1"...."tip7".

Пример:

I install and was able to run some games on a Manjaro and Linux Mint vDisk. It is in a VDI file and the computer I am using is powerful enough to run the game.

When I run the game it will freeze my computer after a minute, forcing me to reboot my computer. I am not sure if this is the limitations of using a Linux vDisk or if there is something more I need to do to make the game run smoothly.

I have used the Windows VHD plugin and was able to play high end games on the VHD with very little performance loss.

In this guide below, it is not clear for distros such as Kali Linux on when to install the DEB file. Do I install it before I install the distro into Virtualbox, after I install the distro into VirtualBox, After I run vtoyboot for the first time?

https://www.ventoy.net/en/plugin_vtoyboot.html

虽然Ventoy 1.0.70已经支持了Qubes OS 4.1.0,但在我实机测试时仅能显示启动选单，不论是选择直接安装还是检查镜像都会黑屏。
我在VMware中测试过，Qubes OS安装时也会检查镜像，但可以按Esc跳过。实机启动却没有任何提示。

设备为联想小新Air15 2021锐龙款，U盘为三星Earplus 256GB版本。
Qubes OS镜像于VMware中正常启动，虽然会提示虚拟化错误...

I have persistent working well with a Ubuntu 20.04.1 LTS liveCD in an Automation environment.
As of late; i've noticed that the persistent FS is growing by just booting the image. IE after 100s of boots; the file system fills up to be totally full and eventually I have to "replace" the persistant.dat with a backup copy to restore functionality.

Looking for advice how to debug this "growth" issue.
Can I mount the presistant.dat file in another liveCD and "clean up"?
If so; how would I do this?
What should i look for as far as files taking up space?
Is there a way to force a filesystem check on the .dat file while booting? Would that help "clean up"?

Is there a tunefs command which might help limit the writes to the persistant.dat ? IE turn off journaling or something?

Obviously; I'd prefer to not have to regularly restore the .dat file in automation as that kindof defeats the purpose of having the persistence in the first place. 

Looking for any advice or ideas someone might have.

There are ways to add shutdown/restart tasks to be executed before a linux machine is shutdown. This is useful for having the script running automatically before every shutdown to ensure you can boot back up into the Linux vDisk after updates that the user may not be aware of. Distros like Linux Mint allow for automatic updates to happen in the background and if an update break the booting into the vDisk without the user knowing, having the script execute before shutdown will prevent this.

I would suggest having the vtoyboot as a package which can be easily installed and updated within the vDisk distro. I would recommend maintaining it on the AUR and Pacstall to ensure users can get the latest versions installed and to be able to install it on most or any distribution. For other distros, the current vtoyboot script will be needed but having a package which on the AUR and Pacstall will allow for updates and to ensure it will run vtoyboot on every shutdown and restart.