3 votes
Platinum Member
Posted 17 June 2020 - 04:00 AM
@ Ventoy
PartedMagic-2020-05-20.iso does not boot fine in Bios mode on version 1.0.13 , can't find PMAGIC_2020_05_20.SQFS
PartedMagic-2020-05-20.iso boots fine in UEFI mode on version 1.0.13
PartedMagic-2020-05-20.iso was previously booting fine on Bios or UEFI on version 1.0.12
alacran
Platinum Member
Posted 17 June 2020 - 06:58 AM
I had to resize the small Ventoy partition because 32mb was too small for fat32, I resized it to 64, still no go. 64mb efi partition btw works fine for E2B. Right now, I resized the 1st partition and created a new 500mb fat32 partition with the Ventoy files. Still no go. I also tried using grubfm installer from here, https://github.com/Q...rubfm-installer, nothing even shows up when booting.Would you consider making a minimalist version of E2B using agfm? Does agfm require any file to be contiguous?
The only thing a BIOS should be looking at is the MBR, PBRs - and for UEFI the \EFI\BOOT folder.
So a minimal agFM would just be the file \grubfmx64.efi which has been copied to the FAT partition as the file \EFI\BOOT\BOOTX64.efi.
Just the one file is all that is needed to boot to agFM.
Member
Posted 26 June 2020 - 01:48 PM
@ Ventoy
PartedMagic-2020-05-20.iso does not boot fine in Bios mode on version 1.0.13 , can't find PMAGIC_2020_05_20.SQFS
PartedMagic-2020-05-20.iso boots fine in UEFI mode on version 1.0.13
PartedMagic-2020-05-20.iso was previously booting fine on Bios or UEFI on version 1.0.12
alacran
What about Ventoy-1.0.14? I test it on my laptop and it works fine with 1.0.14.
Platinum Member
Posted 27 June 2020 - 11:37 PM
What about Ventoy-1.0.14? I test it on my laptop and it works fine with 1.0.14.
It is good to know there is a new version and the issue is fixed, thanks.
alacran
Member
Posted 28 June 2020 - 01:35 AM
Edited by ventoy, 28 June 2020 - 01:36 AM.
Platinum Member
Posted 30 June 2020 - 07:29 AM
What about Ventoy-1.0.14? I test it on my laptop and it works fine with 1.0.14.
Just tested on v1.0.14 on Bios mode.
PartedMagic-2020-05-20.iso does not boot fine in Bios mode on version 1.0.13, and also on 1.0.14, same message:
can't find PMAGIC_2020_05_20.SQFS
I had to go back to v1.012 wich boots fine on Bios or UEFI.
Best Regards
alacran
Silver Member
Posted 03 July 2020 - 05:33 AM
Posted 05 July 2020 - 10:10 AM
There is a problem when running parted magics secure erase feature for ATA drives when booting PM from a ventoy usb.
Parted Magic will boot just fine, it will allow you to secure erase NVMe drives, Sanitize ATA Devices, but when you click on Secure Erase ATA drives nothing happens and the menu to select which drive does not appear.
So to test PM I made a PM usb using rufus, ATA secure erase works fine.
Then made a E2B with alives grub2 file manger booted PM with default iso extension and secure erase worked fine, rebooted with alives grub2 file manger and selected the ventoy boot option and secure erase on ATA drives would not work.
So I rebooted the ventoy usb and selected the grubfm_multiarch.iso, selected PM with partnew option and all worked good.
It is only the secure erase of ATA drives that does not work, I can see the drives and their contents with PM file manager.
Tested with
Ventoy 1.14, 1.13
2 different USB drives
pmagic_2020_02_23.iso
pmagic_2019_09_03.iso
Any ideal when this is happening.
Member
Posted 10 July 2020 - 01:35 AM
There is a problem when running parted magics secure erase feature for ATA drives when booting PM from a ventoy usb.
Parted Magic will boot just fine, it will allow you to secure erase NVMe drives, Sanitize ATA Devices, but when you click on Secure Erase ATA drives nothing happens and the menu to select which drive does not appear.
So to test PM I made a PM usb using rufus, ATA secure erase works fine.
Then made a E2B with alives grub2 file manger booted PM with default iso extension and secure erase worked fine, rebooted with alives grub2 file manger and selected the ventoy boot option and secure erase on ATA drives would not work.
So I rebooted the ventoy usb and selected the grubfm_multiarch.iso, selected PM with partnew option and all worked good.
It is only the secure erase of ATA drives that does not work, I can see the drives and their contents with PM file manager.
Tested with
Ventoy 1.14, 1.13
2 different USB drives
pmagic_2020_02_23.iso
pmagic_2019_09_03.iso
Any ideal when this is happening.
Fixed in Ventoy-1.0.15
Member
Posted 10 July 2020 - 01:38 AM
Silver Member
Posted 10 July 2020 - 02:38 AM
It's looking Ventoy currently not like PTN3 ? Will be nice if we can keep Ventoy files in pre existing FAT32 PTN3....
PTN1- NTFS - ISOs, Payloads etc...
PTN2- FAT32 - agFM
PTN3- FAT32 - VENTOY
Please provide an option in Ventoy tool so that we will be able to extract Ventoy files directly in PTN3 of existing Multi Partitioned USB Drive without formatting it....Does latest version of Ventoy support PTN1 as NTFS ?
Regards...
Member
Posted 10 July 2020 - 02:42 AM
Is there any hope to use Vendor within from FAT32 Partition 3 ?
NO, Ventoy must in PART2.
Silver Member
Posted 10 July 2020 - 02:47 AM
NO, Ventoy must in PART2.
Member
Posted 23 July 2020 - 02:45 PM
Is it not possible so that Vendor will support both PTN2 and PTN3 ?
NO
Member
Posted 23 July 2020 - 02:46 PM
Silver Member
Posted 23 July 2020 - 03:06 PM
Member
Posted 23 July 2020 - 03:10 PM
Hi..Ventoy
I run my own 'SMART_INSTALL.cmd' within 'boot.wim' environment in order to pickup 'SMART_INSTALL.xml' to make Installation Autounattended. I change UNAME, PCNAME and MYINDEX strings in XML. I also Backup User Files to Free Drive and then Auto Format Windows Partition using my 'SMART_INSTALL.cmd'.
So it will be very useful if Ventoy inject custom 'winpeshl_ventoy.ini' and 'start_ventoy.bat' within from EFI Partition to X:/Windows/System32 folder if 'winpeshl_ventoy.ini' and 'start_ventoy.bat' exist in EFI Partition. OR Maybe any better solution to allow user to user their own 'start.bat' within WinPE environment to do some extra/Special work before starting Installation..
a1ive agFM allow us to set 'grubfm_startbat' variable so that we can use custom 'start.bat' within WinPE environment. Similiar Approach will be very useful if Ventoy also provide ?
Thanks & Regards....
Maybe the injection plugin can be helpful.
https://www.ventoy.n..._injection.html
Silver Member
Posted 23 July 2020 - 03:37 PM
Member
Posted 24 July 2020 - 02:13 AM
Will ventoy_startbat.7z be decompressed at X: as follows and replace Ventoy .ini and .bat files ?
X:/Windows/System3/winpeshl.ini
X:/Windows/System3/start.bat
Will it extract within 'X:/ventoy_startbat' folder ?
X:/ventoy_startbat/Windows/System3/winpeshl.ini
X:/ventoy_startbat/Windows/System3/start.bat
In injection approach I also have to update filenames of Windows ISOs in configuration file again and again when updating ISOs. It will be very handy if ventoy_startbat variable can be predefined and will work for all Windows ISOs without specifying names of Win ISOs...
Regards
Ventoy just run command like 7za.exe x -y -aoa -oX: ventoy_startbat.7z
You can test it in your local PC and see the directory structure.
For example, you can run 7za.exe x -y -aoa -oD: ventoy_startbat.7z and check the decompress output in D:
Edited by ventoy, 24 July 2020 - 02:13 AM.
Silver Member
Posted 24 July 2020 - 02:49 AM
Member
Posted 24 July 2020 - 04:47 AM
Is there any way so that injection of ventoy_startbat.7z will apply for all Windows ISOs without specifying images filenames ?
NO. You must specify for each ISO file.
Silver Member
Posted 24 July 2020 - 05:20 AM
OK....Which file in Ventoy Package is responsible for injecting 'winpeshl.ini' and 'start.bat' into X:/Windows/System32 folder when Windows ISO is selected and booted to WinPE environment ? Maybe I can modify that file to use my own 'winpeshl_ventoy.ini' and 'start_ventoy.bat' in exactly the same way I use grubfm_startbat variable in E2B and a1ive grubfm ?
The Finder
Posted 24 July 2020 - 07:54 AM
{
"injection": [
{
"image": "/cn_windows_10_enterprise_ltsc_2019_x64_dvd_9c09ff24.iso",
"source": "/driver/win10-driver.zip"
"destination":"/mypath/"
"command":"7za.exe x -y -aoa -oX:%destination% %archive%"
}
],
{
"image": "/cn_windows_10_enterprise_ltsc_2019_x64_dvd_9c09ff24.iso",
"source": "/driver/win10-driver.zip"
"destination":"/mypath/"
"command":"copy %archive% %destination%"
}
]
Posted 03 August 2020 - 04:31 PM
The Finder
Posted 03 August 2020 - 05:15 PM
However, my old PC can only boot to USB as long as it's a single partition.
Maybe, or maybe not.
It is possible that what your BIOS does is slightly different:
1) it can only boot from floppy (or superfloppy), i.e. a device whose first sector is a (FAT) bootsector (and not a MBR)
2) it detects the presence of a bootsector (as opposed to a MBR) by looking (usually) at the so-called "jump bytes"
In those (good ol' 
) times a possibility (with a number of limitations) was to use the makebootfat which creates something that is at the same time a bootsector AND a MBR.
http://www.advancema...doc-makebootfat
Some references:
http://reboot.pro/to...tcmd-alpha-001/
http://reboot.pro/to...or-usb-booting/
http://reboot.pro/to...fat-fat32msdos/
You'll probably need to use the Wayback Machine for most pages, i.e.:
https://web.archive....pic=13784&st=44
https://web.archive....showtopic=18873
https://web.archive....ows-pentium.zip
EDIT: file is still on sourceforge:
https://sourceforge....dvanceboot/1.4/
https://sourceforge....um.zip/download
(the old links redirected to advancemame.it)
If you want to experiment with this approach and need assistance, it would be better if you started a new, dedicated thread.
Wonko
0 members, 0 guests, 0 anonymous users
