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 !!

AOMEI Partition Assistant Techn. 8.8  UEFI OK Legacy OK  virtual UEFI OK BIOS doesn't bot
Hard Disk Manager 15 Suite  UEFI OK Legacy BIOS OK virtual UEFI OK BIOS OK
lenovo ThinkPad T430

Lazesoft Recovery Suite Professional 4.3.2 UEFI OK , Legacy BIOS OK ,virtual machine
UEFI doesn't bot, Legacy BIOS OK
AOMEI Backupper Technician Plus 5.1.0 WinPE legacy BIOS OK UEFI doesn't bot
virtual machine legacy BIOS OK UEFI doesn't bot

Hello, I would like to ask that, in the next update, you have the option to change the image of the main menu of Ventoy, because I don't know how to use source code, and I believe that most don't know how to use it.

dmg格式的镜像文件好像不可以用Ventoy这个软件进行装系统啊，这个需要怎么解决

Hi!
Thanx a lot for a good job!!!!
I succesfully tested and add LinuxFX 10 WXS LTS to Multiboot USB by Ventoy
ISO: linuxfx10-wx-lts-beta2.ISO
ISO: http://www.linuxfx.org/index.php/sistema...nuxfx-10-w
Boot: Legacy
Processor: Intel i5-5220U (Broadwell)
Laptop: Lenovo Z51-70

BR. from Poland!

Attached Files

Thumbnail(s)
       

Hello, I wanted to set custom theme by Ventoy Plugin but ventoy is still using own theme. Here is my configuration: On first partition (where are iso's) I have folder named ventoy, inside of it there is ventoy.json with content: