Hi. I have seen that the iso of wifislax64 2.1 is compatible with ventoy. However when starting the iso it does not work for me. Attached image of the error that gives me. I don't know if I have to do some kind of thing. Can you help me? Thank you

Attached Files

Thumbnail(s)
   

看到ventoy帮助手册里说，可以支持数据持久化。
请问有经验的朋友，ventoy的数据持久化，对应debian/ubuntu/deepin系统来说，使用apt update进行更新，或者apt install安装的软件是否会保存下来呢？
进行语言设置和输入法设置，是否会保存下来呢？

通过virtualbox安装的xubuntu20.04，安装的时候选择的是efi模式，安装后安装ventoy说明，复制到ventoy分区后，只能以efi模式启动ventoy，才能正常启动。

有没有办法，使安装的xubuntu的vdi文件，既支持legcy模式，又支持efi模式呢？

I've searched the board and tried all the options I could find. I tried F1 option as well as another one but I can't get this to work. Gandalf Redstone 5 and Redstone 6 will not load through Ventoy. Has anyone found a way to fix this or should I just move to a different PE and forget about Gandalf? I don't want to have to change the extension, then boot, then change the extension back each time I have to use it. What are my other options?

I need to install Windows10 to a USB device so I may update my BIOS. (I also have an external HDD to try but I've heard it doesn't work when you try it)

I don't have any current Windows installs on HDD or SSD to run the BIOS update from, and my internal HDD doesn't work anymore, just throws up I/O errors. I've tried swapping HDDs but they all fail with I/O errors, too.

I tried (without Ventoy) to use both Win7 and Vista official install media but it would not allow me to install to a USB device. I don't understand why Microsoft has to be so retarded with this.

I cannot perform the BIOS update from my Linux installs, my system is unsupported for this. Nor am I going to try booting from FreeDOS which is suggested on some websites as a possible alternative for a BIOS update.

The only workaround I've tried is booting a Windows Vista 32 bit installation CD (not with Ventoy) and going into repair mode and getting access to a terminal prompt. From there, I received an error message, "oledlg.dll not found" when I typed in the name of the BIOS updater program and pressed Enter. Trying this with 64bit media such as Vista/7 throws up the following error, "The subsystem needed to support the image type is not present." But at least I see a quick extraction animation when I use 32 bit media, prior to the dll not found message.

My BIOS is very limited and does not offer a boot to BIOS update section like some motherboards do, so I'm screwed there. It is legacy bios from several years ago, prior to the UEFI.

I have separate rescue media DVDs but they will not install to a HDD which does not work. I haven't tried running the 1st recovery media to try and install to USB, I imagine that it won't.

So, my only option, I suppose, is trying to install Win10 to USB or external HDD using Ventoy. The only reason I haven't tried it yet is because I wanted feedback from the community prior to downloading several gigs of data.

Any advice?

版主好，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