Topic: Win10XPE and Grub4DOS  (Read 389 times)

Win10XPE and Grub4DOS
« on: February 25, 2020, 04:08:54 PM »

revo1059

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 12
Does anybody use Grub4DOS to boot the image? When I try to boot the ISO using Grub4DOS I'm getting an error 13 unsupported executable format.

Below is the option I set in menu.lst

title Windows 10X 64bit PE menu.lst v2.0
   map --mem /Win10xpe.iso (0xFF)
   map --hook
   root (0xFF)
   chainloader (0xFF)

Re: Win10XPE and Grub4DOS
« Reply #1 on: February 25, 2020, 04:35:29 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Title Windows PE
find --set-root /WinPE.iso
map /WinPE.iso (hd32)
map --hook
root (hd32)
chainloader /BOOTMGR

Re: Win10XPE and Grub4DOS
« Reply #2 on: February 25, 2020, 04:46:59 PM »

revo1059

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 12
I got an error 5 file not found. The ISO is in the folder and the name matches.

Re: Win10XPE and Grub4DOS
« Reply #3 on: February 25, 2020, 05:04:35 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
In the previous example iso is in root of USB drive. If it's located elsewhere
You need to give complete path and name. And BOOTMGR must be in CAP

Title Windows PE
find --set-root /FOLDER/WinPE.iso
map /FOLDER/WinPE.iso (hd32)
map --hook
root (hd32)
chainloader /BOOTMGR

Re: Win10XPE and Grub4DOS
« Reply #4 on: February 25, 2020, 05:09:50 PM »

revo1059

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 12
It is in the root of the drive. Below is my menu.lst. Option #2 works.

This is what I currently have in menu.lst. The second option works.

title Windows 10XPE
   find --set-root /Win10xpe.iso
   map /Win10xpe.iso (hd32)
   map --hook
   root (hd32)
   chainloader /BOOTMGR

title Windows 10 64bit PE menu.lst v1.0
   map --mem /Win10PESE_x64.iso (0xFF)
   map --hook
   root (0xFF)
   chainloader (0xFF)

Re: Win10XPE and Grub4DOS
« Reply #5 on: February 25, 2020, 05:14:36 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
 :confused: Your iso name is incorrect buddy.

Re: Win10XPE and Grub4DOS
« Reply #6 on: February 25, 2020, 05:20:25 PM »

revo1059

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 12
Sorry, should have clarified, there are two different ISOs. The ISO in the 2nd option works, the ISO in the first option doesn't. If I use Rufus to create a flash drive with just the contents of the first ISO it works.

 

Re: Win10XPE and Grub4DOS
« Reply #7 on: February 25, 2020, 06:37:14 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Hi Revo,

I just created a USB Boot disk with Rufus 3.8 and used Grub4dos 0.4.6a in creation options.
copied over my XPE... WinPE.iso created a menu.lst and booted all the way to destop, with the code I provided in the first place.

Code: [Select]
Title Windows PE
find --set-root /WinPE.iso
map /WinPE.iso (hd32)
map --hook
root (hd32)
chainloader /BOOTMGR

I don't know what to add that could help  :sad:



Re: Win10XPE and Grub4DOS
« Reply #8 on: February 25, 2020, 08:21:01 PM »

revo1059

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 12
Well, I reformatted my portable. Recreated the 2 partitions (1 FAT32 and 1 NTFS). Installed Grub4DOS on the FAT32 and edited the menu.lst with what you provided and still no luck. Maybe it has to do with multiple partitions?\

If I try what I originally had it loads the image then gets the error 13 right after it's done.

If I try the menu config you provided it gets an error 15 file not found right away. The paths and name are set properly.

Re: Win10XPE and Grub4DOS
« Reply #9 on: February 25, 2020, 08:56:21 PM »

revo1059

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 12
Ok, so I again scrapped it all. Reformatted my drive using Rufus (single partition) and had it install GRUB. copied the files over (menu.lst and my .iso file to the root of the drive. Made sure the menu was right (kept both load options, because my original load option works for previous ISOs using older WinPE builds)

title Windows 10 64bit PE menu.lst v1.0
   map --mem /Win10xpe.iso (0xFF)
   map --hook
   root (0xFF)
   chainloader (0xFF)

title Windows PE
   find --set-root /Win10xpe.iso
   map /Win10xpe.iso (hd32)
   map --hook
   root (hd32)
   chainloader /BOOTMGR

Looking in the drive there are 3 files in the root:

 grldr
 menu.lst
win10xpe.iso

Still the same errors

« Last Edit: February 25, 2020, 08:57:17 PM by revo1059 »

Re: Win10XPE and Grub4DOS
« Reply #10 on: February 25, 2020, 10:20:07 PM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
Yes,

Your last setup is exactly like mine  :sad:

I Don't understand why, you get "file not found"...

What kind of USB drive is it ?

Re: Win10XPE and Grub4DOS
« Reply #11 on: February 26, 2020, 01:38:35 AM »

Malok

  • Chef
  • ***
  • Location: Canada
  • Date Registered: Aug 2016
  • Posts: 202
If You want to try an alternate method.
I don't know what you plan to do with this, but if it's a small build.
You can try to Start the boot.wim directly from Grub4dos

First you need to make an all in ram build... see build core in Winbuilder.
Second grab the following files from your compilation install grub4dos on your drive.
And create the following arch in your usb Drive. With the provided files attached to this post,
and the files from your build... Newer versions of Wimboot struggles to boot from Grub4dos

\Wimboot
\BOOTMGR
\bootmgr.exe
\Boot\bcd
\Boot\boot.sdi
\Sources\boot.wim

Then use this in your Menu.lst

Code: [Select]
title Windows PE - wimboot
kernel /wimboot
initrd @BOOTMGR=/BOOTMGR @bootmgr.exe=/bootmgr.exe @bcd=/boot/bcd @boot.sdi=/boot/boot.sdi @boot.wim=/sources/boot.wim

If you want to change the arch of folders and rename files on your usb,
you need to create a custom BCD with the correct configuration inside to have a successful boot.
This way you can have multiple winPE on the same USB drive, also there is no Y: drive mounting
Problems to cope with, using this method.

Hope this will help.

 

Powered by EzPortal