Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 117 online users. » 0 Member(s) | 113 Guest(s) Applebot, Bing, Google, Yandex
|
Latest Threads |
Boot 32 bit Windows
Forum: Ventoy Plugin Forum
Last Post: Rootman
Yesterday, 11:15 AM
» Replies: 1
» Views: 49
|
Is it time to update Vent...
Forum: Ventoy Discussion Forum
Last Post: Epictetus
09-17-2024, 12:36 PM
» Replies: 4
» Views: 931
|
Ventoy 1.0.99 is the fina...
Forum: Ventoy Discussion Forum
Last Post: Rootman
09-17-2024, 11:01 AM
» Replies: 2
» Views: 606
|
WindowsPE - load necessar...
Forum: Ventoy Discussion Forum
Last Post: Nierewa
09-16-2024, 10:41 AM
» Replies: 5
» Views: 8,903
|
"shim_lock protocol not f...
Forum: Ventoy Plugin Forum
Last Post: AzJazz
09-13-2024, 08:19 PM
» Replies: 1
» Views: 177
|
iventoy安装debian12.6花屏
Forum: iVentoy Discussion Forum
Last Post: Tazimi
09-13-2024, 07:16 AM
» Replies: 0
» Views: 138
|
Installing SSL Certificat...
Forum: iVentoy Discussion Forum
Last Post: pleasehelp
09-10-2024, 11:49 PM
» Replies: 0
» Views: 158
|
Ventoy enroll key manager...
Forum: Ventoy Discussion Forum
Last Post: asheroto
09-10-2024, 10:46 PM
» Replies: 17
» Views: 6,434
|
ventoy可以引导我的系统,如何设置开机默认启动...
Forum: Ventoy Plugin Forum
Last Post: sevk
09-10-2024, 07:52 AM
» Replies: 0
» Views: 173
|
Something has gone seriou...
Forum: Ventoy Discussion Forum
Last Post: bigcid10
09-09-2024, 01:33 PM
» Replies: 7
» Views: 2,303
|
|
|
How to MBR-boot to Ventoy from grub2 |
Posted by: Steve2926 - 08-28-2020, 12:00 PM - Forum: Ventoy Discussion Forum
- Replies (4)
|
|
If ventoy grub2 boot code is not installed to the USB drive, how can I boot to Ventoy from another grub2 menu as there is no Ventoy core.img file present?
i.e.
- Prepare USB drive with partition 1 and partition 2
- standard grub2 is installed on USB drive
- copy ventoy files from a ventoy USB drive to partition 2
- MBR-boot to standard grub2 menu
- Choose a grub2 menu entry to boot to Ventoy MBR grub2 on the second partition
if I get core.img.xz and extract core.img and use
multiboot (hd0,2)/ventoy/core.img
it hangs.
|
|
|
VENTOY And ISO of MEDICAT USB 20.08 |
Posted by: haiphong - 08-27-2020, 10:45 AM - Forum: Ventoy Discussion Forum
- Replies (7)
|
|
Hello All,
VENTOY And ISO of MEDICAT USB 20.08 :
Directory Print - 2020/08/27 12:40 E:\Iso (*.*)
Directory of E:\Iso
Name Size Date/Time
! 00 à 03 = Programmes de MEDICAT.USB.20.08 <DIR> 2020/08/27 10:30
! 7=MB_UBP-MultiBoot-Pro-v0.8....1=OK,Password... <DIR> 2020/07/17 18:18
! Captures Ecran <DIR> 2020/07/17 18:18
! Medicat.20.07.Img Converti en ....Iso Avec Powe... <DIR> 2020/07/17 18:18
2=PE_Gandalfs_W10PE-x64-Redstone-6-AKA-19H2-Build... <DIR> 2020/07/23 19:55
0=Install_Win7-Ultimate-Sp1-Multilanguage-11-....iso 3 883 Mb 2020/01/06 12:15
0=Install_Win8.1-Pro_x64_10-2019_Multilangues....iso 4 093 Mb 2019/10/11 13:19
0=Install_Win-All-7-8.1-10-49In1-Multi-03-202....iso 12 Gb 2020/03/31 01:05
00_[UEFI]_Acronis_True_Image_v2020_Build_25700.iso 670 Mb 2020/04/08 04:51
00_[UEFI]_AOMEI_Backupper_v5.8.0.wim 278 Mb 2020/06/19 13:56
00_[UEFI]_EaseUS_Data_Recovery_Wizard_v13.5.wim 369 Mb 2020/07/06 22:34
00_[UEFI]_EaseUS_Todo_Backup_13.2.0.2.iso 494 Mb 2020/06/27 18:47
00_[UEFI]_Elcomsoft_System_Recovery_7.2.628.iso 330 Mb 2020/05/26 09:35
00_[UEFI]_Macrium_Reflect_v7.2.4971.wim 287 Mb 2020/06/16 15:16
00_[UEFI]_Malwarebytes_Antimalware_v20.08.iso 869 Mb 2020/08/02 17:46
00_[UEFI]_MiniTool_Power_Data_Recovery_v8.6.wim 337 Mb 2019/10/05 16:25
00_[UEFI]_O&O_BlueCon_v17.2.7202.wim 654 Mb 2020/07/31 08:13
00_[UEFI]_Rescuezilla-1.0.6.1.iso 757 Mb 2020/06/26 12:32
00_[UEFI]_Symantec_Ghost_x64_v12.0.0.11197.wim 432 Mb 2020/07/17 15:31
01_[UEFI]_Active@_Boot_Disk_v16.0.0.iso 424 Mb 2020/06/07 23:07
01_[UEFI]_Mini_Windows_10.iso 1 027 Mb 2020/07/13 09:08
01_[UEFI]_PlopLinux-19.4-x86_64.iso 2 660 Mb 2020/06/09 07:31
01_[UEFI]_SystemRescueCD_x64_v6.1.7.iso 693 Mb 2020/08/02 10:07
02_[BIOS]_Boot-Repair-Disk_v2020-6-13.iso 880 Mb 2020/06/14 11:40
02_[UEFI]_rescatux-0.73.iso 691 Mb 2020/07/28 08:26
02_[UEFI]_SuperGrub2-2.04s2-beta2-multiarch-CD.iso 15 Mb 2020/05/25 20:05
03_[UEFI]_AOMEI_Partition_Assistant_8.8.wim 258 Mb 2020/05/08 20:14
03_[UEFI]_EaseUS_Partition_Master_14.5.wim 519 Mb 2020/07/08 08:30
03_[UEFI]_MiniTool_Partition_Wizard_12.1.wim 409 Mb 2020/07/16 18:43
03_[UEFI]_NIUBI_Partition_Editor_v7.3.0.wim 533 Mb 2020/05/31 15:08
03_[UEFI]_Paragon_Hard_Disk_Manager_v17.13.1.wim 363 Mb 2003/02/01 03:05
03_[UEFI]_Parted_Magic_2020_05_20.iso 797 Mb 2020/05/21 08:47
1=PE_EE_W10xPE_Plus-de-100-Progs_14-03-19_V0_....ISO 1 764 Mb 2019/04/20 09:55
1=PE_EE_W8.1PE_Acronis-DD12_TI2017_06-09-17_V....ISO 1 231 Mb 2017/09/06 11:49
1=PE_Medicat.20.07_Medicat.20.07.Img_Converti....iso 26 Gb 2020/07/17 11:27
1=PE_Medicat.20.07_NON-DETECTE.img 26 Gb 2020/07/15 19:10
2=PE_Bob.Ombs.Modified.Win10PEx64.v4.11-Engli....ISO 2 805 Mb 2018/09/14 02:38
2=PE_Dium5.0.1807.B_Avec_AOMEI=OK.iso 1 444 Mb 2019/10/18 12:58
2=PE_EaseUS_Todo_Backup_13.2=OK.iso 494 Mb 2020/05/27 13:11
2=PE_EaseUS-Partition-Master-Technician-14.0_....iso 483 Mb 2020/04/22 13:39
2=PE_Gandalfs_W10PE-x64-Redstone-6-AKA-19H2-B....ISO 7 343 Mb 2020/07/22 10:25
2=PE_Gandalfs_Windows-10-PE_28-07-2019-Englis....iso 5 157 Mb 2020/06/03 16:20
2=PE_GHOST32_12.0.0.10695.iso 317 Mb 2020/03/08 19:54
2=PE_GHOST64_12.0.0.10695.iso 403 Mb 2020/03/08 18:12
2=PE_HBCD_PE_x64_Build-181211-English.iso 1 565 Mb 2018/12/27 15:01
2=PE_HBCD_PE_x64_Build-190103-English=OK.iso 1 552 Mb 2019/01/05 11:47
2=PE_Macrium_Reflect_Workstation_7.2.4971_(x64).iso 299 Mb 2020/06/16 15:09
2=PE_MultiBoot-2k10-7.25.3-Unofficial_04.2020....iso 4 092 Mb 2020/04/24 22:13
2=PE_MultiBoot-2k10-7.27-Unofficial_EN-RUSSE.iso 4 068 Mb 2020/07/07 07:00
2=PE_MultiBoot-2k10-WIN7-10-7.27-Unofficial_E....iso 803 Mb 2020/07/14 11:22
2=PE_WinPE_10_8_Sergei_Strelec_x86_x64_2020.0....iso 4 343 Mb 2020/04/26 18:49
2=PE_WinPE_10_8_Sergei_Strelec_x86_x64_2020.0....iso 4 225 Mb 2020/06/08 22:17
2=PE_WinPESE-x64_16.07.07_From_KYHI_10Forums=....iso 1 039 Mb 2020/07/09 14:13
3=PE_AOMEI_Backupper.5.8.0_Tech.Plus.WinPE.Le....iso 308 Mb 2020/06/19 14:19
3=PE_AOMEI_Backupper.5.8.0_Tech.Plus.WinPE.UEFI.iso 312 Mb 2020/06/19 14:20
3=PE_AOMEI-Backupper-Pro-WinPE_Boot-Legacy-v5....iso 468 Mb 2020/04/21 13:58
3=PE_AOMEI-Backupper-Pro-WinPE_Boot-UEFI-v5.7....iso 471 Mb 2020/04/21 14:18
3=PE_MediCat.v18.04.Stable=NON-OK_Mini-Window....iso 11 Gb 2018/08/31 09:51
3=PE_MiniTool.Partition.Wizard.Pro.Ultimate.1....iso 270 Mb 2020/06/11 10:38
3=PE_MiniTool_Partition_Wizard_12.0_Technicia....iso 311 Mb 2020/05/20 18:02
3=PE_NIUBI-Partition-Editor-7.3.0_PE_x64=OK.iso 555 Mb 2020/05/31 15:10
3=PE_Paragon.Hard.Disk.Manager.17.Business.WS....iso 400 Mb 2020/06/12 20:55
3=PE_Paragon-Hard-Disk-Manager-17-Suite-17.4.....iso 383 Mb 2019/12/25 10:13
3=PE_Parted.Magic.2020.05.20-English=OK.iso 797 Mb 2020/05/22 11:59
3=PE_Passcape.Reset.Windows.Password.9.0.0.90....iso 327 Mb 2018/11/13 18:01
3=PE_PCUnlocker_UEFI_x64=OK.iso 267 Mb 2019/12/27 13:15
3=PE_PCUnlockerPro_v52=OK.iso 203 Mb 2019/09/12 17:26
3=PE_QILING_Disk_Master-Technician_5.1_WinPE.iso 418 Mb 2020/06/18 15:57
3=PE_R-DriveImage_6.3.6304_OEMKit.iso 80 Mb 2020/06/19 07:03
3=PE_R-Drive-Image-6.2-Build-6302-Multilangua....iso 80 Mb 2020/04/21 10:14
3=PE_TeraByte.Drive.Image.Backup_Restore.Suit....ISO 310 Mb 2020/05/28 09:58
3=PE_Windows-Password-Recovery-Tool-Pro-6.4.5....iso 181 Mb 2018/12/05 09:53
4=LINUX_HDClone-PRO-Edition-9.0.11a-English=OK.iso 65 Mb 2019/04/14 16:50
4=LINUX_Kali-Linux-2019.4-AMD64=OK.iso 2 635 Mb 2019/11/26 03:33
4=LINUX_SystemRescueCD-x64-6.1.4=NON-OK.iso 688 Mb 2020/06/09 09:26
4=LINUX_SystemRescueCD-x64-6.1.6=NON-OK.iso 687 Mb 2020/07/04 15:52
4=LINUX_Tails-x64-4.7=OK.iso 1 129 Mb 2020/06/03 09:47
4=LINUX_Ultimate.Boot.CD.5.3.9.iso 803 Mb 2020/08/22 08:09
5=Install_et_Emulator_Android-10=NON-OK.iso 980 Mb 2020/01/27 16:40
5=Install_et_Emulator_Android-x86_64-9.0-RC1=....iso 909 Mb 2019/11/16 05:20
6=AV_12_AntiVirus_ComSS_Boot_USB-11-2019=NON-OK.iso 5 334 Mb 2019/11/25 08:23
6=ComSS_Boot_11-AV_Utils_USB_2020_06.iso 5 877 Mb 2020/06/25 18:04
7=MB_MultiBoot-2k10-DVD_USB_HDD-Unofficial-7.....iso 4 410 Mb 2018/04/29 23:02
7=MB_UBP-MultiBoot-Pro-v0.8.1=OK,Password=ubp....iso 4 032 Mb 2020/02/01 13:32
Directories-Print.txt 2 787 b 2020/06/09 13:04
Directories-Print_With-Length.txt 4 104 b 2020/06/09 15:30
86 files, 173 Gb
401 Gb available from 953 Gb.
Veriy Interessant !!!!!
|
|
|
Linux script - Bug? |
Posted by: GCMartin - 08-24-2020, 05:25 PM - Forum: Ventoy Discussion Forum
- Replies (2)
|
|
Ventoy Linux script help shows "-I" & "-i" for creating the bootable Ventoy disk.
The understand I get from the help and other documentation is that 1 will ask user confirmation, while the other will not. But, in both cases, -i and in -I, the scripts asks confirmation. Namely Code: Attention:
You will install Ventoy to /dev/sdb.
All the data on the disk /dev/sdb will be lost!!!
Continue? (y/n)y
All the data on the disk /dev/sdb will be lost!!!
Double-check. Continue? (y/n)y
The script does create a bootable Ventoy, so either one of the options is a bug or one of them should be removed.
Hope this helps
|
|
|
Looking for documentation on CreatePersistentImg.sh |
Posted by: GCMartin - 08-24-2020, 04:48 PM - Forum: Ventoy Discussion Forum
- Replies (3)
|
|
The Ventoy Linux version contains a file "CreatePersistentImg.sh" when the tar file is expanded into the Ventoy folder along with all the other Ventoy needs. In that folder, too, there is a README file.
Can someone steer me to any documentation on what this, "CreatePersistentImg.sh", is?
And how to use it when creating a Ventoy bootable disk?
The README file give NO clue to what it is nor when it is to be used. The following is the README
Code: ========== Ventoy2Disk.sh ===============
sudo sh Ventoy2Disk.sh { -i | -I | -u } /dev/XXX XXX is the USB device, for example /dev/sdb.
Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX
CMD:
-i install ventoy to sdX (fail if disk already installed with ventoy)
-I force install ventoy to sdX (no matter installed or not)
-u update ventoy in sdX
OPTION: (optional)
-r SIZE_MB preserve some space at the bottom of the disk (only for install)
-s enable secure boot support (default is disabled)
-g use GPT partition style, default is MBR style (only for install)
========== CreatePersistentImg.sh ===============
sudo sh CreatePersistentImg.sh
sh CreatePersistentImg.sh [ -s SIZE_IN_MB ] [ -t FSTYPE ] [ -l LABEL ] for example:
sh CreatePersistentImg.sh ----> persistence.img in 1GB size and ext4 filesystem and casper-rw label
sh CreatePersistentImg.sh -l MX-Persist ----> persistence.img in 1GB size and ext4 filesystem and MX-Persist label
sh CreatePersistentImg.sh -s 2048 ----> persistence.img in 2GB size and ext4 filesystem and casper-rw label
sh CreatePersistentImg.sh -s 4096 -t xfs ----> persistence.img in 4GB size and xfs filesystem (ext2/3/4 xfs are supported) and casper-rw label
If no documentation exist, could someone show a use case(s) of how this applies to the Ventoy bootable that is created, please?
Thanks in advance
|
|
|
Upgrade request for Ventoy |
Posted by: GCMartin - 08-23-2020, 01:52 AM - Forum: Ventoy Discussion Forum
- No Replies
|
|
Curious.
I do understand the very good benefit the script and EXE file do for us as it creates the Ventoy device.
But, the options when running these are NOT saved upon Ventoy device creation. And the user MUST REMEMBER those options whenever the user upgrades Ventoy from one release to the next.
Would the Ventoy developers consider saving a configuration/options file, either hidden or exposed, on Partition #2 of the Ventoy device?
If this is the case, on subsequent updates, there is no possibility that any user would get it wrong going from one release to another. Worst case in the Windows version, if Ventoy sees the 2nd partition, it could display the prior options that was used so a user would know what was done before...although I, personally, see little need for that. But, Ventoy could used the prior options as the default unless the user overrides some options from before.
If an implementation is forthcoming, all new upgrades would merely be:
Code: "Ventoy.sh - U /dev/ventoy-unit" and similar for a command-line .exe program
Thus the prior Ventoy bootable options would be read from the Ventoy unit. When the prior options are maintained, simply reading the configuration file from partition #2, the update to the new version will occur correctly, with nothing overlooked.
Hope this is helpful
|
|
|
|