ODD boot process on my HP Compaq DC7700 CMT desktop (it is dual or multi boot)

Leap is on it’s own HDD,
and Win10 and Win7 on the main HDD.
this is what I get for initial boot(I assume due to EasyBCD)

Then it goes to this odd Grub4DOS thing that I don’t know how it got there, nor can I find it on my HDD’s.

Then FINALLY to the Leap 15 boot menu.

Is there anyway someone here can point me to where to find Grub4DOS,
And more importantly is it even possible to get to a ‘normal’ Grub2 screen that will recognize Win10 in addition to Leap 15
and bypass that Grub4DOS thing?
Would really hate to do a complete reinstall to get things right.

I don’t really know, because I have never done things quite that way.

Your first screen image is the Windows Boot Manager screen. I see a similar screen on in Win7 system.

I’ve never used Grub4DOS. I am guessing that was installed by EasyBCD, in which case it would be somewhere on your Windows disk. On my Win7 system, Leap 15.0 is on the same hard drive as Windows. You have it on a different hard drive. And I’m guessing that EasyBCD installed Grub4DOS to handle the use of a different drive for linux. I’ll note that I could be completely wrong about that.

When in openSUSE Leap you can use the Yast Bootloader module to install Grub2 to the MBR, and you can have openSUSE on a 2nd HD, but it has been so long since I have done that, I cannot remember exactly what options should be used in the bootloader module to get it to work that way.

I hope someone with more recent (or less foggy) experience spots this thread with the answer.

In the meantime, I will try to recall how it is done for certain.

EasyBCD is on my Windows drive, and as far as it installing Grub4DOS I can’t find out where it is in the EasyBCD routine(s).
I have looked up Grub4DOS and all I find are downloads and project articles, but nothing so far(over a few months of searching) that tels me EasyBCD uses it or used it.

I really don’t like that intermediate step, and IIRC it wasn’t there after the first install of 42.3, nor the second full reinstall of 42.3. I truly don’t know when it came into being. I can live with it if I have to, it is irksome, but if I take Leap out of EasyBCD, I’m afraid I will never find it again.

You are honest anyway;)

Me too!

Thank you, I have looked the options in YaST Bootloader more than a few times, but being the novice I am, I fear screwing something up.

… yes, and I am not particularly that eager to screw it up for you, either.:shame:

OK, I ‘checked’ the YaST (1st panel) Boot Loader Location option item labeled ‘Boot From Master Boot Record’, and restarted.
It didn’t bypass that 2nd ODD Grub4DOS screen,
BUT>>> It did add Win10 the the Grub2 boot menu (3rd image) I consider that ‘some progress’,
So If I want to go to Win10 from there I can.Why I would I don’t know…

This option installs grub2 boot code in MBR of disk with /boot. Which is most likely not your BIOS boot disk.

Most likely in


Yep, that is where it is. Thanks.

It looks as if I have to line with this. Not that much of a problem, just irksome as I said before.
I tried renaming the NST folder just to see what would happen and ion reboot t gave me an error screen indicating it could not find the ‘AutoNeoGrub0.mbr’ file in the NST directory.

Oh well. worse things in life have happened(and very recently too!).

EasyBCD uses that directory for important config files…

Thanks deano; I will go through that wiki.
I was sorta hoping I could EASILY get rid of Win7 and easyBCD, and get back to just a Grub2 ‘green screen’ menu without having to strip it down to Win10, and reinstall Leap 15. Having Leap on a separate drive was not the best thing I have done.

But, like I said, it is an irritant I can live with.
I’m old, I’m tired, I’m not going anywhere in a hurry.

You can

  1. Change boot disk in BIOS. It will give you GRUB menu, but Windows 7 may have issues
  2. You may select “Custom Boot Partition” in YaST bootloader module and explicitly enter path to Windows 7 disk MBR. Make sure you have Windows recovery disk in case something goes wrong.

Thanks for the tip(s)

I do wish that were so.

For #1 - this old machines Bios does not allow me to change the boot order in the BIOS. Apparently it would need to be changed where the SATA connectors connect to the motherboard(I will need to look into that).

For #1 and #2, I’m not sure I really care about Win7 anymore.
OR> maybe it is Win10 I should be not caring about.:wink:

Win10 and Win7 are on the same hard drive. /dev/sdb2/ has Win10 and /dev/sdb4/ holds Win7

**Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors**
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000001

**Device****Boot****    Start****      End****  Sectors****  Size****Id****Type**
/dev/sdb1  *           64    204863    204800   100M  7 HPFS/NTFS/exFAT
/dev/sdb2          208845 660242866 660034022 314.7G  7 HPFS/NTFS/exFAT
/dev/sdb3       660244480 661202943    958464   468M 27 Hidden NTFS WinRE
/dev/sdb4       661203270 976769071 315565802 150.5G  7 HPFS/NTFS/exFAT

**Disk /dev/sdc: 149 GiB, 160000000000 bytes, 312500000 sectors**
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd0f4738c

**Device****Boot****    Start****      End****  Sectors****Size****Id****Type**
/dev/sdc1            2048  16771071  16769024   8G 82 Linux swap / Solaris
/dev/sdc2  *     16771072 100663295  83892224  40G 83 Linux
/dev/sdc3       100663296 205518847 104855552  50G 83 Linux
/dev/sdc4       205518848 312498175 106979328  51G 83 Linux