Jump to content











Photo
- - - - -

a1ive's grub2 and File Manager has great UEFI support!


  • Please log in to reply
181 replies to this topic

#176 steve6375

steve6375

    Platinum Member

  • Developer
  • 7290 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 28 May 2020 - 07:46 AM

grubfm_multiarch.iso + Ventoy on real  Intel system?



#177 ms1304

ms1304
  • Members
  • 6 posts
  •  
    Germany

Posted 28 May 2020 - 08:03 AM

grubfm_multiarch.iso + Ventoy on real  Intel system?

No, I don't have a UEFI Intel system

grubfm_multiarch.iso + Ventoy on real AMD system.



#178 alacran

alacran

    Gold Member

  • .script developer
  • 1445 posts
  •  
    Mexico

Posted 02 June 2020 - 02:32 AM

I don't know if all of you are aware that agFM is capable to Ramboot  your Wimboot VHDs, (see attached picture), unfortunately so far this is possible only if the coupled Wimboot VHD + the source WIM file are located on a internal HD.

In my CSM/MBR PC having grubfm.iso on the root of the boot partition where all booting files and folders are, I can call grub4dos from Windows boot manager and from grub4dos load/boot on Ram grubfm.iso, with following entrie:

iftitle [if exist (hd0,0)/grubfm.iso] Grub2 File Manager of a1ive - (hd0,0)/grubfm.iso
map --mem (hd0,0)/grubfm.iso (0xff)
map --hook
chainloader (0xff)

You can do this manualy or by means of UEFI_MULTI from wimb.

Then from grubfm.iso loaded on Ram it is possible to select from our internal or external HD all the same kind of files we use to boot from our USB device.

But it is also possible to Ramboot our Wimboot VHD files located on the internal HD.  

NOTES:

1 .- If booting from internal HD and the coupled Wimboot VHD + the source WIM file are located on a internal HD, it boots fine.

 2.- If booting from internal HD and the coupled Wimboot VHD + the source WIM file are located on a USB device it do not work this way.

3.- If booting from a USB device and the coupled Wimboot VHD + the source WIM file are located on same USB device, some times the VHD boots (fine) directly and immediately as filedisk without giving us the booting options like on the attached picture, in some other cases it is allowed to select load the VHD to Ram but it fails during boot. Then for all practical effects Rambooting a VHD do not work this way.

 

4.- If booting from a USB device and the coupled Wimboot VHD + the source WIM file are located on a internal HD, it boots fine. See: http://reboot.pro/to...e-8#entry214948

 

I know we can live without a fix to this feature on agFM, and even Ramboot our Wimboot VHDs directly from grub4dos (wich is more direct and faster), but it will be good if Rambooting the Wimboot VHDs could be implemented on agFM also when booting from and having files on the USB device (as on No. 3).

In order to Ramboot a VHD using grub4dos we have two different sets of commands:

- When the VHD + the source WIM file are located on a internal HD and booting from internal HD:

title 10x64-WB.vhd - SVBus  RAMDISK  - 1536 MB - map for WIMBOOT as next to last hd KARYONIX
find --set-root --ignore-floppies /10x64-WB.vhd
map --top --mem /10x64-WB.vhd (hd)
map --hook
root (hd-1,0)
chainloader /bootmgr

Which has been already implemented and is working fine.

 

- When the VHD + the source WIM file are located on a external (USB)device and booting from that external (USB) device:

iftitle [if exist (hd0,0)/10x64-WB.vhd] (hd0,0)/10x64-WB.vhd - SVBus  RAMDISK  - 2048 MB - map for WIMBOOT
map --top --mem (hd0,0)/10x64-WB.vhd (hd-1)
map --hook
root (hd-1,0)
chainloader /bootmgr

Which is not implemented and not working.

The key difference is on the map --top --mem line where we are forced to use (hd) when VHD is on internal HD or (hd-1) when VHD is on external USB device. 

 

If not done as said on previous sentence there is no way to make it work in both cases when dealing with Wimboot VHDs, as the VHD is coupled to a WIM file it is the only way to let the VHD after loaded on RAM, to find its coupled WIM's location on the physical device during booting.

alacran

Attached Thumbnails

  • VHD.jpg

Edited by alacran, 03 June 2020 - 11:16 AM.

  • wimb and devdevadev like this

#179 alacran

alacran

    Gold Member

  • .script developer
  • 1445 posts
  •  
    Mexico

Posted 02 June 2020 - 03:10 PM

JFYI

 

Booting again grubfm.iso from the USB device, tried booting other VHDs (+ the source WIM) located into internal HD, and they booted fine, strange thing is the first tested VHD that did not boot this way, booted fine when loading grubfm.iso from internal HD.

Previous post section Notes No. 4 was edited with new info, (to avoid confusion to future readers).

 

 

4.- If booting from a USB device and the coupled Wimboot VHD + the source WIM file are located on a internal HD it boots fine.

 

So with this new info we can say only when the VHD + his couple WIM file are on an external device the VHD can't boot from RAM.

 

alacran



#180 steve6375

steve6375

    Platinum Member

  • Developer
  • 7290 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 02 June 2020 - 03:21 PM

map --top --mem /10x64-WB.vhd (hd) - creates a new BIOS hd device and increments the number BIOS hard disks by one

map --top --mem (hd0,0)/10x64-WB.vhd (hd-1) - maps the last hard disk in the list as the vhd file - the number of hard disks stays the same.



#181 alacran

alacran

    Gold Member

  • .script developer
  • 1445 posts
  •  
    Mexico

Posted 02 June 2020 - 05:12 PM

After testing with other VHDs I can confirm:

 

If booting from a USB device and the coupled Wimboot VHD + the source WIM file are located on same USB device, some times the VHD boots (fine) directly and immediately as filedisk without giving us the booting options like on the attached picture, in some other cases it is allowed to select load the VHD to Ram but it fails during boot. Then for all practical effects Rambooting a VHD do not work this way.

 

Then previous Post No. 178 on Notes section 3 was edited in acordance with this, (to avoid confusion to future readers).


 

alacran



#182 alacran

alacran

    Gold Member

  • .script developer
  • 1445 posts
  •  
    Mexico

Posted 03 June 2020 - 11:05 AM

For all those that may not care about agFM capability to boot "standard" or Wimboot VHDs:

  • We all know best, easy and faster way to Fileboot a VHD is just by means of Windows bootmanager, (on CSM/MBR and UEFI/GPT).
  • Also we all know best, easy and faster way to Ramboot a VHD is just by means of grub4dos, (on CSM/MBR only).

And of course if we have some VHDs on our machine it is reasonable to think we allready made the respective entries on our BCDs and/or menu.lst files, to have them ready when booting from the PC.

But when booting from a USB device, agFM capability to boot "standard" or Wimboot VHDs from a internal HD, is very useful, since thanks to its graphycal interface we do not need to know in advance the VHDs files names and locations and also previously have the respective entries on our BCDs or menu.lst files.  It is only a matter of browse into our internal HD to find a VHD and select it to boot.

alacran






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users