search for: syslinux_di

> > I am trying to find out whether vesamenu.c32 was crashing or the code > that was loading/starting vesamenu.c32. I haven't found that out yet. For testing this case with vesamenu.c32 I would suggest a very simple cfg with 2 or 3 entries (not just one entry, as the behavior would be slightly different) as first step. For example: *** syslinux.cfg start *** # Note that

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, >