load the whole ISO.

The problem with this code is that it doesn’t boot into the ISO it loads, it just says Loading boot sector… booting… and then skips to windows:

initrd tftp://${fog-ip}/os/Sergei/Sergei.iso
chain tftp://${fog-ip}/os/memdisk iso raw

This code just crashes when loading the WinPE in the ISO (meaning it loaded the whole 4GB ISO, but I don’t know why it crashes. The PC has 16GB of RAM):

sanboot http://${fog-ip}/html/Sergei/Sergei.iso

This code just says input/output error 1d0c62 fix (on the ISO file):

initrd http://${fog-ip}/html/Sergei/Sergei.iso
kernel tftp://${fog-ip}/os/memdisk iso raw

There’s a file named “bootmenu.class.php” in /var/www/fog/lib/fog, in it there’s the following code:

self::$_exitTypes = array(
    'sanboot' => $sanboot,
    'grub' => $grub['basic'],
    'grub_first_hdd' => $grub['basic'],
    'grub_first_cdrom' => $grub['1cd'],
    'grub_first_found_windows' => $grub['1fw'],
    'refind_efi' => $refind,
    'exit' => 'exit',
);

Now as I said before when selecting grub_first_hdd it does recovery phase but does not load windows afterwards and when selecting grub_first_found_windows it skips recovery phase but windows loads.

If I chage the code that way (change is in the $grub['XXX']:

    'grub_first_hdd' => $grub['1fw'],
    'grub_first_cdrom' => $grub['1cd'],
    'grub_first_found_windows' => $grub['basic'],

The exact same thing is happening but the opposite, meaning now grub_first_found_windows it does recovery phase but does not load windows afterwards and when selecting grub_first_hdd it skips recovery phase but windows loads.

@george1421 Wow thanks a ton! It did bring me to the load screen, but it has a different error now. The thing about Sergei Strelec is that there are a lot of dependencies outside the wim file. I think I might need to take a different approach and load the whole ISO.

@george1421 On your tutorial you linked 2.6.0, but I managed to find myself 2.7.3 and it didn’t work either.

Here is the error (after I updated to 2.7.3):

It seems the WIM file lacks the folder PXE

@wayne-workman As far as my understanding goes I must use HTTP to load ISOs into RAM, correct?
Not assuming I have 8GB of RAM at all my PCs here, how do I load it? I followed every single guide and non worked for me.

I looked inside the “boot.wim\Windows\Boot” and there is no PXE folde, thus it doesn’t have bootmgr.exe.
What can I do to fix it? Can I just modify it and copy PXE folder from boot.wim who does have that folder (say, windows 10)?

@george1421

Update: I managed to get a connection with the fog server and it loads the files. Problem now is that it says “no bootmgr.exe”, do I need to extract the whole ISO file in the same folder with BCD, boot.wim and etc…?

@george1421 I know it’s for legacy, that’s what my boot is set here.

It seems like I am not able to connect to the fog server with ftfp or http (like: tftp://X.X.X.X/tftp/os/Sergei/BCD). And the thing about the reboot is that it is just rebooting and than not booting to the WinPE after that.

Hi there all,
I am trying to add an option to my fog server to boot PCs into Sergei Strelec (an ISO file). I have found some tutorials but no success.

Here is what I used:
https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/10
https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

Sergei Strelec is 4GB, hence I tried a 300MB WinPE but it didn’t work either.
This is the codes I tried, each with different problem (X.X.X.X is for my IP address):

set tftp-path X.X.X.X
set pe-path ${tftp-path}/tftpboot/os
kernel ${tftp-path}/wimboot gui
imgfetch --name BCD ${pe-path}/BCD BCD
imgfetch --name boot.sdi ${pe-path}/boot.sdi boot.sdi
imgfetch --name boot.wim ${pe-path}/boot.wim boot.wim
boot || goto MENU

This code shows it finds all files but instead of booting, it just restarts the computer

set tftp-path tftp://${X.X.X.X}

If I’m trying to do it like that (instead of the first line in the code) it says connection timeout.

chain memdisk iso raw

Adding this line before the boot shows MEMDISK: bootstrap too large to load when trying to boot to Sergei and WinPE (even though WinPE is only 300MB).

initrd X.X.X.X/os/Sergei/Sergei.iso
chain memdisk iso raw
boot || goto MENU

Same error with this code.

@george1421 Thanks a ton for your good will to help me! I really appreciate!!!

Doesn’t SANBOOT work as expected? The grub for dos implementation in FOG is a hold over from long ago.

Sadly no. Actually this is the worst option for me there as it is not even posting (As I said, With “Boot Exit” set at ‘grub_first_hdd’, Radix does it recovery phase but does not load windows afterwards.
With “Boot Exit” set at ‘grub_first_found_windows’ Radix doesn’t go into action but windows does shows up).
I think it might worked with windows 7, but it was too long ago so don’t relay on that.

Might you need to reinstall SmartRecovery again to resetup windows since the windows upgrade basically reinstalled windows all over again. It might have broken the chain in booting.

I tried to install it on a fresh install of windows 10.

But SmartRecovery is not chaining to windows after it does its recovery.

Something I noticed today is that when not connected to the fog server it’s booting smoothly. It loads first the SmartRecovery and than goes into windows as supposed, once conneted to fog it is only half working.
So how do I chain it? (Although it’s weird cause it seems like it is chained, just something with the GRUB is messing it up.)

Is your version of SmartRecovery compatible with the version of Windows you just upgraded to?

I’m able to install it on the windows, but they do have a newer version of this (which also doesn’t work well).

I have been using Radix SmartRecovery (It’s a protection application that does not let you make any saves on the computer, e.g: you saved a text file on desktop, after the restart it will be deleted.) on windows 10 with Grub_First_HDD Boot Exit settings on Fog.
Apparently it stopped working at some point (my guess at the recent windows update, but the corporation forces updates due to security reasons).

With “Boot Exit” set at ‘grub_first_hdd’, Radix does it recovery phase but does not load windows afterwards (PCs have M.2 if it matters).
With “Boot Exit” set at ‘grub_first_found_windows’ Radix doesn’t go into action but windows does shows up.
(Windows installed in legacy if matters).

It seems like I need to merge the two somehow. I’m lost, please help.
Thanks in advance!