版主好，ventoy 我使用的是最新版，经过测试 CentOS 7.6 采用 MBR 引导，就报错，报错如图1 和 2 ，一个是物理机测试拍照图片，一个是 vmware workstation 截图；在物理机用 UEFI 启动就正常，CentOS 6.5 MBR 引导没问题
   
   

At the end of copiing the iso files I get a message "can not change attributes of file XXX.iso". How to overcome?
Thamk You.

斑竹好

     这边使用最新1.0.31~1.0.20进行测试安装在如下平台，
server：dl360gen9
boot：legacy
u disk：MBR (8g) 
OS: RHEL7.7
（该版本中1.0.31 GPT方式，方案1无法规避，不知是不是版本更替里面的兼容性问题。）

关于无法完全引导进入安装提示dracut如下所示：

1 引导iso进入dracut界面（图1，2）
2 对比采用dd方式ventoy查看legacy引导时设备加载提示只有u disk分区，无dm-0（图3）
3 对比采用dd方式cd引导legacy时设备加载有sr0指向iso镜像挂载（图4）
4 对比采用dd方式ventoy引导uefi时设备加载有dm-0的指向iso镜像挂载（图5）

还是麻烦看下，谢谢。

Attached Files

Thumbnail(s)
                   

Before version 31, by pressing the F5 key, I could check the consistency of scripts Since I installed version 31, I have an error imessage:

Hello everybody,

first of all, thank you very much for this great tool!
I have a few questions about Secure Boot support - maybe someone can help me:

If I understand correctly, the "enrolled" key is saved in the EFI.
How can this be reversed?
I have reset the keys and all settings to default in the BIOS and even reflashed the BIOS - but the key remained.
With a Live Linux and mokutil --delete or --reset with subsequent confirmation in the "MOK Manager" worked - is that the right way?
An option for this in Ventoy might come in handy.

A Ventoy Stick with Secure Boot support also works perfectly on a device without (or with deactivated) Secure Boot.
Why then Secure Boot support is optional at all and not always automatically activated?

How do other Live CDs such as PartedMagic does this?
These boot with Secure Boot without having to import a key.

Thanks and happy holidays!
Martin

I successfully had persistence working with an earlier version of ventoy and Mint 20 but now with Ventoy 1.29 it does not seem to work .
Here is my json file. If I check under tools using the F5 key on boot it says persistence is working but files do not seem to persist after a reboot

Will Ventoy support Memtest86 8.4?
I tried to boot it using Memdisk but it wouldn't boot.

hello

About this discussion https://github.com/ventoy/Ventoy/issues/660


For me

......   For the libraray

----------- SCAN SUMMARY -----------
Known viruses: 8903510
Engine version: 0.102.4
Scanned directories: 11
Scanned files: 63
Infected files: 3
Data scanned: 15.27 MB
Data read: 4011.18 MB (ratio 0.00:1)
Time: 39.144 sec (0 m 39 s)
.......
clamscan -r ventoy-1.0.30 | grep Trojan
LibClamAV Warning: cli_scanxz: decompress file size exceeds limits - only scanning 27262976 bytes
/home/a/ventoy-1.0.30/tool/x86_64/xzcat: Unix.Trojan.Mirai-7640640-0 FOUND
/home/a/ventoy-1.0.30/tool/x86_64/hexdump: Unix.Trojan.Mirai-7640640-0 FOUND
/home/a/ventoy-1.0.30/tool/x86_64/ash: Unix.Trojan.Mirai-7640640-0 FOUND

and for the USB KEY
clamscan -r /mnt | grep Trojan
/mnt/ventoy/ventoy.cpio: Unix.Trojan.Mirai-7640640-0 FOUND




what to decide ?

ventoy-1.0.30 版本制作
配置选项  没勾选安全启动支持提示下图 安全引导

 用其他PE工具EasyU 制作U盘PE进入没提示 
想知道这个和其他工具制作的 区别。

Hello,
I have a total of 3 external hard drives:  2x 3,5" (2TB resp. 1TB) and 1x 2,5" (4TB). I use Ventoy 1.0.30.  On the two 3.5" hard drives I can install Ventoy normally. It doesn't matter whether I use the MBR or the GPT partition style.  I can boot from both hard drives without any problems.
When I install Ventoy on the 2.5" hard drive, I can only do it in GPT partition style (because MBR only supports hard drives up to 2TB). However, when I boot from this drive, I only get a black screen with "VT" in the upper left corner. is displayed.  I had the same problem with the old version 1.0.27, but then it was not "VT", but "GR". is displayed at boot time.  Why won't Ventoy boot from this hard drive ?