LEXAR Très Très Lent et Livrable en 1 Mois : ==> Voir Fichier Joint = BenchMarks
Chez AMAZONE :
AXE Speedy Très Rapide et Livrable en 24 heures : Voir Fichier Joint = BenchMarks
Chez ALI-Express :
STMagic Très Très Rapide et Livrable en 3 Semaine : Voir Fichier Joint = BenchMarks
Comme vous voyez, il y a énormément de Différences de Vitesses. Donc, méfiez-vous de "WISH", dont le Service Assistance est très très difficile à joindre.
Celui de ALI-Express est correct.
Celui d'Amazone est Super Super Rapide !!!!!
Okay, lets face it...VENTOY is a image file generator, where the file/options is used to create a bootable USB Ventoy drive!
That bootable USB drive is to be populated by the user with their choice of ISO files. After population with ISO files, the Ventoy USB is booted and Ventoy will show the populated ISOs as choice(s) for booting.
VENTOY’s generator come is 3 different choices
A Windows program which creates the VENTOY USB
A Linux program which creates the VENTOY USB
An ISO which, when it is built upon a CD or DVD or USB or..., it, when booted will run the Linux program to create the VENTOY USB
VENTOY’s current problem is that its Windows creator UI and its Linux creator program are VERY different in any user’s eyes.
I wonder if anyone has come to the rescue to create a user-interface (UI) that looks and operates the same no matter which VENTOY choice is used. That would have the advantage where, from a user’s perspective, no matter which platform the VENTOY program is launched from, it looks the same.
There are several choices which development can make to do this. I rule out WINE for obvious reasons that “under the hood” (so to speak), the system generations utilities are different. Yet there are other choices where the UI can detect its environment and use the proper systems functions for USB generation.
So the UI could take the user selection input via a screen (like Ventoy’s Windows UI) to get the configuration requests from the user and use the proper system environmental commands to generate the USB.
Detecting whether it Windows or Linux is as simple as looking at the PSW or their are other simple commands which will do this no matter which, Linux/Windows/MAC, the running program is on.
This is, maybe, a simple way for VENTOY to go forward where it looks the same no matter which choice the user makes; namely ISO, Windows, MAC, or Linux.
There would become a secondary advantage to such a step. Reduction of webpages since the user perspective would reduce to a single UI. Right now, there are 3 very differently worded sections depending on the choice. This would confuse any user who happens to have Linux, MACs and Windows in their home.
A further benefit is that development ONLY needs to address 1 UI!!! The background programs would handle the rest. Lastly, it would allow the generated options to be included in the 2nd partition of the Ventoy USB so that it become easy to ID a Ventoy that has different options to another, when someone is trying to debug findings and isolate them without getting mixed up. That file could be nameed "Ventoy.conf" or Ventoy.options or Ventoy.built or anything development feels comfortable to be named that shows which options were used to generate the Ventoy USB.
Also, development will ONLY have 1 UI to debug when problems occur vs as it is done today: problem in one, then fixed, then having to go to the other to fix it, then go to the ISO and ... (you get the picture)
Thus simplicity for both development and users, alike.
Thoughts, anyone.
BTW: I have not developed in decades, but I do know that for cross-platform UIs, several choices exist. There exist better people than myself to aid in this for Ventoy.
Question
I already have a ventoy device that has Linux installed on its reserved partition and it works fine. Unfortunately, the installed linux will die if I upgrade the ventoy system with a newer version. Can this bug be fixed in later versions? I know it can't be right now because the reserved partition should be kept unchanged and the EFI/ubuntu folder of the VTOYEFI partition should be left unchanged. Also, the ventoy/ventoy/ventoy_grub.cfg file should be left unchanged (I think this already works).
???
I am having problems when starting Linux Distros that allow the use of the system in live, the installation of Linux operating systems and the execution of windows PE through Hiren's.
In the case of live system startup (Linux's distributions) it seems to me that the error has to do with the loading of the modules related to the video driver (nouveau or nvidia) according to the images that I will attach to the post. As for installing SOs, such as Debian 14 LXQT, an error appears saying that it was not possible to locate the installation ISO (in this case, the Debian graphical installation interface loaded). In the case of Hiren's CD, the error consists of an infinite looping on the loading screen, where the blue Windows logo appears and is frozen.
Note: I read in the documentation the possible limitation that exists in BIOS Legacy of being able to read USB drives of maximum 127 GB, but I did not use USB drives larger than 64 GB, and I even used a 4 GB pen drive and put that package file installation of Ventoy on partition 1, but without success. I tried to use the Memdisk mode, which in the documentation said it was recommended for WindowsPE and several Linux distributions, but as I have a 2GB DDR2 RAM, ISOs larger than 2GB have errors when loading the system in RAM and those that are smaller than 2GB seems to take a long time to load or else there is a freeze in the middle of the process.
Bearing in mind that Ventoy boots normally at the System Boot, the problem is time to load Linux system modules in Live and files present within the ISOs for installation Linux SOs. I used both the MBR and GPT partition table. I formatted the Pen Drive in different formats, NTFS, EXFAT, FAT32 and EXT4.
Systems used and which presented the same video error when loading modules from live systems: Manjaro, Debian, Fedora and Linux Mint, all of which are already tested versions and apparently working without problems according to the site list, and I myself tested these pen drives that I created with Ventoy on VM QEMU / KVM and they run perfectly the graphic part of the lives systems, I just tested whether installations can access ISO files on the pen drive and work well, the problem for me is really in the boot of the pendrive by the BIOS, I would like a solution because I really liked the program.
Could anyone possibly help me resolve a problem with the Menu screen resolution? I have a 4k screen on my HP Spectre x360. When the laptop boots into the menu, the icons & text are so small i really struggle making out what is what. I have looked in the Grub config, but to be honest i'm not really sure what i would need to change?
Within the last few weeks, I had posted a question asking how to download and decompress Ventoy onto a flash drive. Unfortunately, I did not save or copy that information. The response was thorough with screenshots for clarity. I would like someone to help me locate that response, or post the information a second time. Thank you for your help.
I've asked before, but did not get a reply. Ventoy2Disk.sh -i /dev/sdX ... does it have to be the whole disk? Is there a way to make/specify the partitions myself?
Because, if I could Ventoy2Disk.sh -i /dev/sdXn (like sda4), well, I wouldn't have to use a whole disk for it, right?
Now, if this could be done, it would have very interesting possibilities, not just for Ventoy, but for the future of Linux distributions in general , so please tell me it can be done
