Hello,

I've been searching but can't find answers.

What's the difference between Ventoy in Package and Ventoy in Device?
What's Package and what's Device?
Why Package has exFAT/MBR and Device has exFAT/MBR (note that I already know what a filesystem and partition table is)?


If I understand Ventoy in Device is partition S: WORKSPACE, am I correct?
Is Ventoy in Package partition T: VTOYEFI ?
   

If so why Ventoy gui says exFAT and File Explorer says FAT as filesystem?

Hi

I noticed that, by booting with Ventoy the GParted Live iso, in the GParted boot menu, all its boot modes are not displayed. How come?

Thanks

Bye

Hi
I have an SSD I would like to install Ventoy on but it has a 4096 sector size.
I run Linux with no access to Windows.

sudo gdisk /dev/sdc gives:

Disk /dev/sdc1: 31256064 sectors, 119.2 GiB
Sector size (logical/physical): 4096/4096 bytes
Disk identifier (GUID): 38AAEDDA-2A84-4B23-B05A-57E99B87691B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 5
First usable sector is 6, last usable sector is 31256058
Partitions will be aligned on 256-sector boundaries
Total free space is 31256053 sectors (119.2 GiB)


sudo ./Ventoy2Disk.sh -i /dev/sdc
gives:
Create partitions on /dev/sdc by parted in MBR style ...
Error: The location 249987071 is outside of the device /dev/sdc.
Done
Wait for partitions ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
Wait for /dev/sdc1//dev/sdc2 ...
sed: can't read /sys/class/block/sdc1/dev: No such file or directory
mknod -m 0660 /dev/sdc1 b  ...
mknod: missing operand after ‘b’
Special files require major and minor device numbers.
Try 'mknod --help' for more information.
sed: can't read /sys/class/block/sdc2/dev: No such file or directory
mknod -m 0660 /dev/sdc2 b  ...
mknod: missing operand after ‘b’
Special files require major and minor device numbers.
Try 'mknod --help' for more information.
[FAIL] /dev/sdc1//dev/sdc2 does not exist



Is there a way to install Ventoy on such a drive?
Thank you
Chris

thanks for longpanda for ventoy word cup edtion 1.0.85 date 18.12.2022 word cup final Match Fra Vs Arg

Hello @longpanda @ventoy

I have designed my theme for 1024 x 768 resolution.



It looks good.
But in some computers 1024 x 768 resolution is not available. I don't know why.. So other bigger resolution is selected although I have set fixed 1024 x 768 in ventoy.json.
Like this

On Aomei Partition Assistant, I can create a Windows To Go based on my current Windows system. I can then use a LinuxOS > Gnome Disks to create a disk image .IMG file from the WinToGo. Then I put that .IMG file into a Ventoy, but it does not fully boot. I have made my Ventoy a NTFS, not an exFat, which helped it boot farther, but it does not fully boot, even if I use it on the same PC that I created the WinToGo on.

There are many ways to make a WintoGo, I am only asking about how to use Ventoy to boot a WintoGo that has been created specifically by Aomei Partition Assistant. Thank you.

Hi ventoy Team, can add Support for Holo iso (steam OS) its not working with latest version
I tryed holoiso 4.0 
 have good day  

Hello forum,

had to remove/delete (wiht the filemanger of the OS under Linux) a corrupt ISO. Afterwards I copied the ISO again to the Ventoy stick
 
But now "(Linuxmint-20.3-cinnamon-64bit.iso" is listed twice in the list of the ISO's.....


How can one of those entries be removed?


Thank you!

Harry

Hi


I formatted a stick with Ventoy 1.0.84 and inserted three iso files into it.

I tried booting from a computer with the UEFI but the message "Verification failed: (0X1A) Security violation" is displayed.

How come?


Thanks

Bye

Hello Master Longpanda; How to write theme.txt in order for some information about computer hardware to appear in the main menu. is it possible?

e.g.

theme.txt

+ vbox {
  left = 1%
  top = 1%
  + hbox {
  + label {text = "SecureBoot" color = "#ffff00"}
  + label {text = "@$grub_uefi_version@" color = "#ffff00"}
  }
  + hbox {
  + label {text = "Platform" color = "#ffff00"}
  + label {text = "@$grub_cpu-$grub_platform@" color = "#ffff00"}
  }
  + hbox {
  + label {text = "RAM" color = "#ffff00"}
  + label {text = "@$grub_total_ram MB@" color = "#ffff00"}
  }
  + hbox {
  + label {text = "Resolution" color = "#ffffff"}
  + label {text = "......." color = "#ffff00"}
  }
}