Dual-Boot Windows 10+ Syslinux - Can't Get Syslinux Partition To Boot Properly

G

gibbon_tech

Member
Hey Folks - Well I'm looking for some advice:
I've been working on this a few days now, but success has been limited.
On an external drive, I have 3 partitions - a small system reserved at the beginning of the drive that holds the windows boot files, the 2nd partition holds windows, and a 3rd holds YUMI, which is a multiboot utility (it runs off syslinux).

The bcd files are on the small system reserved partition which is set to active. I have added the respective boot entries for windows & yumi (for yumi I used lilo to create the entry).

The windows always boots properly, but when I try to boot yumi(syslinux) I get a boot error.
The menu entry points to the correct partition, and the nst_linux.mbr file is present at the root of this partition.
I don't know where i'm going wrong, advice is appreciated

Also, a couple things i've noticed:
1- When I add a menu entry, though I select the correct partition, I find that after it's been added, it points to the c: drive, I have to go to advanced settings and change the path for the entry (which sticks)
2- In the menu overview, it reads: easybcd boot device:c\
Since I am editing a bcd file I pulled out of my external drive, shouldn't it say easybcd boot device:g\ ? or maybe it's just a quirk

Here's my overview:

There are a total of 2 entries listed in the bootloader.
Path: C:\Users\Administrator\Desktop\BCD

Default: Microsoft Windows
Timeout: 5 seconds
EasyBCD Boot Device: C:\

Entry #1
Name: Microsoft Windows
BCD ID: {default}
Drive: H:\
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: testing12
BCD ID: {aa66d4a4-2027-11ea-8456-dc0ea10b4cfe}
Drive: U:\
Bootloader Path: \NST\nst_linux.mbr

Thoughts appreciated
 
gibbon_tech said:
1- When I add a menu entry, though I select the correct partition, I find that after it's been added, it points to the c: drive, I have to go to advanced settings and change the path for the entry (which sticks)
Click to expand...
There's your problem.
Don't change what EasyBCD sets up, it knows what it needs and where it must be.
That's the chain to Linux not the OS itself.
 
Terry - thanks for thoughts - I tried what you said, it didn't work:
I made a new bcd, added the lilo boot entry, and selected u: partition (syslinux)
After adding, in overview, the lilo partition was set to c: , like so:

Entry #2
Name: NeoSmart Linux
BCD ID: {b488a44c-203a-11ea-8457-dc0ea10b4cfe}
Drive: C:\
Bootloader Path: \NST\nst_linux.mbr

As per your instruction, I left it alone, but at boot I just got a boot error
C: drive has nothing to do with it anyway, since the active partition with the bcd is G:

Question: for linux, does the easybcd file nst_linux.mbr need to be on the active partition with the bcd, or should it be on the root of the linux partition?



By the way, I am working on this bcd setup with the external drive plugged in on an active os, I am not actually running the os from usb right now.




thank you
 
I did a bit of an experiment (success)
I formatted the syslinux partition, and installed ubuntu to it
I then created a boot entry for it with easy bcd (grub 2)
I put easybcd's AutoNeoGrub0.mbr file and ang0 file on the small active g: partition, booted it up, and it found ubuntu no problem

Now to experiment more with the syslinux
 
Back
Top