Jump to content











Photo
* * * * * 5 votes

Easy2Boot Development Discussion

grub4dos multiboot multipass usb boot iso

  • Please log in to reply
1396 replies to this topic

#1376 Guest_AnonVendetta_*

Guest_AnonVendetta_*
  • Guests

Posted 02 December 2019 - 11:13 PM

@War10ck: You are calling @steve6375 a "nooby"? I think everyone on this forum is laughing right about now. He *CREATED* E2B, and surely knows more about it than any of us, but you are not willing to listen.

#1377 War10ck

War10ck

    Newbie

  • Members
  • 19 posts
  •  
    France

Posted 03 December 2019 - 12:12 AM

NO !!!! I never told that.

you have misunderstood.

 

I'M nooby !!! saw that the previous answer of Steve was obvious but as I said on a post above :  I'm tired

Sorry if I misspoke...

And I KNOW that Steve is the creator of E2B, that's why I ask him all his questions! You only have to read the last 2 pages of the topic :P

 

I am willing to listen :)

Edited by War10ck, 03 December 2019 - 12:18 AM.


#1378 Guest_AnonVendetta_*

Guest_AnonVendetta_*
  • Guests

Posted 22 February 2020 - 12:28 AM

I have a few questions:

 

I am going to boot a Tails ISO from my iODD, install it to a USB flash drive, then make a disk image of that flash drive with RMPrepUSB. However, I plan to use persistence, so a 2nd partition will be needed, which the Tails installer creates. Can E2B boot this disk image containing multiple partitions? I think the iODD can do this on its' own, but I am not sure what file extension is needed.

 

When installing the latest beta E2B (as of last night) to a flash drive, the installer offers to create contig.iso in \_ISO\, but that file is nowhere to be found when I check for it. Maybe this is a bug?

 

Thanks!



#1379 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 22 February 2020 - 04:04 PM

see 'List of tested ISOs' page for details on any particular ISO.

The Contig.iso question asks you to enter an option, so it depends on what you entered.



#1380 Guest_AnonVendetta_*

Guest_AnonVendetta_*
  • Guests

Posted 25 February 2020 - 01:15 AM

Yes, I know you have to enter a # when the E2B installer wizard asks about contig.iso...and I did. This was a few days ago. But I tried again today with E2B9i beta, and a spare 8GB USB FDD. When it gets to the part about contig.iso, it doesnt matter whether i choose 0 (for none), 500, or any other # (naturally there must be enough free space so I account for that), contig.iso simply is not created. When I choose 500, I get the following:

 

Make \_ISO\CONTIG.ISO file?
===========================
 
\_ISO\CONTIG.ISO is a large empty file which is only used
                   when your linux ISO is not contiguous.
 
nnnn  = Size in MB
0     = No CONTIG.ISO
 
Set CONTIG.ISO size ([0]=None) (MB) [e.g. 500] : 500
 
CONTIG.ISO is not present.
Checking for agFM compatability (requires PTN2=FAT and 60MB+, Windows 10 or USB HDD, internet connectivity)
Pinging www.google.com...
Internet OK
Partition 2 is FAT
Partition 2 is J:
Partition 2 has 557MB free (must have over 60MB free)
 
I used the default options, same behavior no matter what # I choose. Clearly the issue is with the E2B installer itself, not my method (not that I'm doing any "special" or "different").


#1381 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 25 February 2020 - 06:23 AM

Hi - yes sorry. It's a bug in CONTIG.ISO code.

 

line near 653 in Make_E2B_USB_Drive.cmd  should be

set /a ask=!ask!+0

not

set /a ask=%ask%+0

will fix in next beta.



#1382 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 25 February 2020 - 06:27 AM

P.S. Found  bug in recent grub4dos releases.

File must be contiguous even for a map command.

Older versions could use non-contiguous files.

See https://github.com/c...4dos/issues/233



#1383 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 06 March 2020 - 07:45 AM

Latest grub4dos fixes the map/chainloader bug when booting non-contiguous files

http://grub4dos.chenall.net/

http://dl.grub4dos.c...a-2020-02-29.7z


  • alacran likes this

#1384 alacran

alacran

    Platinum Member

  • .script developer
  • 2710 posts
  •  
    Mexico

Posted 06 March 2020 - 10:43 AM

Good news steve thanks for the info.

 

Your friend

 

alacran



#1385 Peter80

Peter80

    Frequent Member

  • Advanced user
  • 124 posts

Posted 15 October 2020 - 10:26 AM

I have problem with Pop OS iso. I downloaded the nvidia iso, copy the iso to my easy2boot flash drive and booted. It booted successfully and when i selected Pop OS menu entry it started loading the system components and when it reached 'starting gnome display manager', or something like that, it showed black screen. I couldn't drop to tty, or do anything else. I don't know if this is easy2boot issue or Pop Os iso issue, but i am unable to install Pop OS distro on my laptop.



#1386 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 15 October 2020 - 10:54 AM

Presumably your PC has nvidia graphics?

Are you MBR or UEFI-booting?

What is your PC?

Did you try the non-nvidia ISO?

Which ISO EXACTLY did you try?

How many other systems have you tested?

Did you try a Google search for known issues with your PC and  Pop OS/nvidia?



#1387 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 15 October 2020 - 11:51 AM

I have reproduced issue using UEFI64 boot and pop-os_20.04_amd64_intel_13.iso

Ventoy shows same problem.



#1388 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 15 October 2020 - 12:20 PM

I just tested on a real system and it worked.

Maybe it looks for a USB drive and does not work in VBox which treats it as a HDD?



#1389 Peter80

Peter80

    Frequent Member

  • Advanced user
  • 124 posts

Posted 15 October 2020 - 02:14 PM

My laptop is HP Elitebook 8560W with video card NVIDIA Quadro 1000M and it using MBR booting. I downloaded pop-os_20.04_amd64_nvidia_13.iso and i have installed successfully other linux distros using the same easy2boot flash drive. This is the first .iso that i have problem.



#1390 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 15 October 2020 - 02:19 PM

OK. Then it is probably an incompatibility between that ISO and your hardware. Try the  Intel version of the ISO. Or maybe add a cheat code to the kernel parameters - e.g.  noapic  noacpi nomodeset  vga=ask  ..



#1391 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 22 October 2020 - 06:54 PM

New E2B video on how to semi-automate the Utilman hack to gain full access to a Windows system without needing to know an account password.

http://rmprepusb.blo...o-uploaded.html



#1392 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 14 August 2021 - 02:10 PM

I have been working on a grub4dos for UEFI (I call it grub4efi) version of the E2B menu system and boot loader.

There have been quite a few bugs which yaya (the developer) has fixed, but there are also still some bugs which are unfixed - see https://github.com/c...grub4dos/issues

 

 

The menu configuration commands, etc. seems to work quite well and STAMPS and animation are working.

I have managed to make it compatible with the legacy E2B meu system, however grub4efi does not support the wimboot mechanism which is used by a1ive grub2\grubfm, Ventoy, etc. and allows the booting of WIndows Install ISOs.

And so, at the moment, I use grub4efi to detect if the USB drive is a Removable type or a Fixed Disk type.

If USB=Removable, I allow Windows Setup to detect the \AutoUnattend.xml file in the root of the USB drive and this will load the ISO as a virtual DVD when WinPE loads.

If the USB=Fixed, then I 'call'  agFM (grubfm) which is on partition 2 of the E2B USB drive and this then used wimboot to load the Windows ISO and load the ISO as a virtual DVD in WInPE.

 

So far I have these working in a similar manner to the grub4dos Legacy menu system:

 

Windows 10/11 Install ISOs Removable and Fixed USB drives

WinToGo WIn8 VHD  fixed 25GB  (fat+ntfs)

winbuilder isos, e.g.  WIN10_PESEx64.iso

HBCD v1.0.2 uses .isoPE01 file extension

.imgPTN, .imgPTN23, .imgPTNREP3 file extensions

.WIM files

Linux isos...

.isopersist file extension

.isopersistdebian

.isopup

ParrotOS

ArchLinux install 5.12.8

Debian Live

FedoraKnoppix 8.6.1

PopOS Gorilla

SCRE - storage recovery

puppy slacko64 7

FatDog

Ubuntu21

Supergrubdisk iso - need to load efi.img as fd9 and then chainload /efi/boot/efi.img

PartedMagic

rescatux

LinuxMint xfce 20.1

 

I have found that because the E2B menu system is in 800x600 mode, it can actually cause some Windows .efi files to fail to boot (0xc00000f error), so it is best to issue the 'graphicsmode -1 1024 768' command just before allowing it to boot to the ISO/payload.

 

A1ive's ntloader utility is used in grub4efi to boot to VHD and WIM files.

 

At the moment, because agFM is required for Windows Install ISOs when using a Fixed disk USB, agFM must be present on FAT32 Partition 2 and you first boot to agFM and then to E2B/grub4efi.

 

I hope to be uploading an early Beta soon which allows you to update an existing E2B USB drive.

Meanwhile, it would help if you could look at the remaining issues with grub4efi on the issues list and maybe test/confirm them?


  • alacran and devdevadev like this

#1393 VendettaReborn

VendettaReborn
  • Members
  • 9 posts
  •  
    United States

Posted 19 October 2022 - 11:37 PM

Getting this error when making a new E2B drive onto the SSD installed into my iODD:

 

https://imgur.com/a/PbJQrMK

 

My 2nd partition is 32GB FAT32. It did populate with files. It's not an issue of free space, so what's the problem?

 

I didnt let the installer create a 3rd data partition to fill the rest of the drive, I don't need it.

 

Kind of strange that there are no posts in this thread since last year.

 

This also happens if i install with default settings. Since only Ventoy is failing, maybe i can just skip it.


Edited by VendettaReborn, 20 October 2022 - 12:22 AM.


#1394 VendettaReborn

VendettaReborn
  • Members
  • 9 posts
  •  
    United States

Posted 20 October 2022 - 01:43 AM

Ignore, solved. I completely disabled UAC in Group Policy, disabled NTFS compression for my user's Temp folder, and made sure Defender was disabled. Not sure which one did it, but Ventoy installed fine now.

#1395 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 20 October 2022 - 08:36 AM

I tested using a compressed TEMP folder and got the same issue!!!

 

It seems xcopy had a problem copying from a compressed folder to the root of the FAT32 volume

L:\e2b\Update agFM>xcopy C:\temp\compressed\ventoy l:\
File creation error - The parameter is incorrect.
Unable to create directory - L:\
0 File(s) copied

L: is the E2B USB FAT32 volume (partition 2)

copying to L:\ fails

copying to L:\junk\  works

copying to the NTFS partition root of the USB drive works

 

 

so issue seems to be copying only when copying files to the root of a FAT32 volume from an NTFS compressed folder

The file should be uncompressed by Windows as the destination does not support compressed files

 

Is this a bug in Xcopy or Windows?

 

 

 

 

 

Attached Thumbnails

  • xcopyfat32bug.JPG


#1396 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 20 October 2022 - 09:01 AM

I managed to make it work  by adding a \ to the source path

 

so

xcopy /herky C:\temp\compressed\ventoy\ L:\

works



#1397 VendettaReborn

VendettaReborn
  • Members
  • 9 posts
  •  
    United States

Posted 20 October 2022 - 07:47 PM

Maybe robocopy would be a better alt to xcopy? It too is built into Windows.





Also tagged with one or more of these keywords: grub4dos, multiboot, multipass, usb boot, iso

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users