Hi.
I tested with Ventoy 1.0.09 BackBox Linux 7 amd64 - preview 05.2020 (backbox-7-desktop-amd64.iso).
"Backbox Linux is a an Ubuntu-based distribution, it is designed to be fast and easy to use (...)".
Download:
https://www.backbox.org/download/

Boot with Legacy BIOS on laptop Lenovo Z51.        

It's only THE BEST software that can do the JOB very well as it's supposed to be.
I knew one Hardware that does the same job but it costs money.
https://www.amazon.co.uk/Zalman-ZM-VE350...B016K7699M

And this Ventoy Software gave us soooooo much of relief!!!

Only one request to make, is it possible to BOOT from WIM file likewise it does for ISO?

If not then what could be the best & easiest way to CONVERT from WIM to ISO?

If this gets done, then this Software would be a Huge revolution in the Live-OS segment.

我发现自己常用的几个WinPE ISO都是要开启Memdisk模式才能正常启动的，而Memdisk模式默认是关闭的。

建议增加一个小功能：对于任意ISO比如A.iso，如果同目录下同时存在特定的标识文件例如A.iso.mem，则在A.iso被选中时自动开启Memdisk模式，不用手工按F1切换。

主板华擎Z390太极，BIOS版本4.30（官网最新），安全启动开启，CSM关闭。
ventory版本1.0.09-windows，制作时勾选了"配置选项" > "安全启动"。

参考《UEFI模式安全启动操作说明》进行到Perform MOK management这步，选Enroll key from disk回车后，不能显示预期的Select Key画面，电脑不再响应任何键盘输入，键盘大小写切换键和数字锁定键都不能切换相应LED指示灯状态。疑似死机或陷入死循环。

使用两个不同型号的U盘制作和测试了多次，100%重现。

hi!
thanks for this great tool.
i've noticed that it runs a lot smoother, when i disable the theme (comment in grub.cfg)
is there an "official" way to disable theming?
a "ventoy.json" with the follwing content:

Hello,
I'm trying to boot "manjaro-lxqt-20.0-minimal-200423-linux56.iso" on a HP8570p in BIOS mode with "ventoy 1.0.9"
I can select the iso and I got the manjaro screen.
Then I just pressed enter to start the manjaro live cd. After a while I got this message:

I tested boot with Ventoy:
1. Manjaro Linux_KDE -20.0-200426_linux56 (x64)
2. Manjaro Linux-xfce-20.0.1-200511-linux56 (x64)
Download:
https://manjaro.org/downloads/official/xfce/
Boot with Legacy BIOS at laptop Lenovo Z51.

Hi.

Today I tested with Ventoy Medicat v19.10 stable Mini Windows 10 x64.

Boot with Legacy mode at laptop Lenovo Z51.

Download new version 20.06 - only img, not ISO , 19.10 not avaiable from this links.
DL:
https://drive.google.com/drive/folders/0...2NKbVJNWjg
https://mega.nz/#F!mV0hhSDb!T1sP1z8nSkDOzFpWmAgjrA

A Mac OS machine leaves dot files such as “.DS_Store” and “._Linux-Mint.iso” when any file is copied, moved or renamed via the Finder. Normally on Linux or Mac OS (and Windows?) these dot files are hidden by file browsers and even command line tools like “ls”. 

I had used a Mac to copy about a dozen ISOs to the ExFAT partition, sorted into folders. Ventoy displayed something like this on its boot menu: 

._dos-7.iso
._freebsd-12.iso
._freenas-11.3.iso
._linux-mint-x64.iso
._windows10-1909.iso
dos-7.iso
freebsd-12.iso
freenas-11.3.iso
linux-mint-x64.iso
windows10-1909.iso


Since there were more ISOs than this on my drive I had to scroll down to the next page of the boot menu just to see any of the real ISO entries. 

These AppleDouble dot-underscore files contain metadata incompatible with non-Mac filesystems, that would normally be stored in a “resource fork” on an HFS/HFS+ or APFS formatted partition, completely hidden to the user. These files can be cleaned manually from a drive with a tool like Onyx, but that would need to be done every single time any ISO file was modified (moved, copied, renamed) on any Mac. 

Ideally the solution to this is for Ventoy to ignore and hide any dot files it encounters, regardless of whether or not they end in “.iso”. Just like “ls” does unless you do “ls -a”. 

Tested Acronis True Image - default Linux-based bootable media
Tested Macrium Reflect - WinPE 10 based rescue media
Vention: v1.0.09 
Test PC: Lenovo Yoga S730, UEFI, SecureBoot disabled

AcronisTrueImage2017_8058.iso
AcronisTrueImage2018_15470.iso
AcronisTrueImage2019_17750.iso 
AcronisTrueImage2020_25700.iso OK
MacriumRescue64bit.7.2.4859.iso OK

Acronis - after selecting from menu => Loading protected mode kernel..., only v2020 with success, others silently die with black screen. In 2020 they changed backup format to tibx, not liked that !!