[syslinux] [PXELINUX] menu.c32/vesamenu.c32 and MS Virtual PC 2007 --> Hang/crash

Bart van den Oetelaar oetelaar24 at zonnet.nl
Tue May 20 13:43:49 PDT 2008


Thanks, that is very useful information!!

However, recompiling the menu every time I change it is not really something I would like to do.

Is it possible to fix the hang/crash in menu.c32/vesamenu.c32 experienced during PXEboot of a MS Virtual PC 2007 machine?
That would make the menu a really great tool for selecting a memdisk, distro or winPE to boot from.

Is it possible to debug it somehow? VirtualPC is available for download @ Microsoft at no cost, you only need a Windows pc to be able to run it, so pretty much everyone could test it with menu.c32/vesamenu.c32.
Otherwise I could maybe do some debugging if I knew how to.

Getting this fixed would be very nice indeed.

-Bart

-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On Behalf Of Murali (????? ?????)
Sent: vrijdag 16 mei 2008 10:33
To: For discussion of SYSLINUX and tftp-hpa
Subject: Re: [syslinux] [PXELINUX] menu.c32/vesamenu.c32 and MS Virtual PC 2007 --> Hang/crash

On Wed, May 14, 2008 at 12:09 PM,  <oetelaar24 at zonnet.nl> wrote:
> Hi,
>
> I've recently did some extensive testing with PXELinux and I must say
> it's great!
>
> I've tested it with several pc's and VMware vm's at home, this works
> flawlessly.
>
> However at my work, we only use MS Virtual PC 2007 and so on.
>
> I've started today to testimplement pxelinux into wds/ris, this seems
> to work but when I want to display a menu eg: default menu.c32, then
> the vm hangs..
> The vesamenu.c32 does the same, although it does switch the resolution.
>
> I found another post by someone earlier on the archive, but no real
> solution other than "use VMware" was stated, unfortunately, that is no
> option for me.
> Post listed here: http://syslinux.zytor.com/archives/2007-March/008246.html
>
> FYI: I made a small mistake and copied simple.c32 from the latest
> tar.gz/menu and used that to try and display the menu.
> However it did not display MY menu because this is probably not used
> for it, it did display A menu, works like a charm! Maybe this gives
> some lead?

menu.c32/vesamenu.c32 use a different code base from
simple.c32/complex.c32. You can create your own "simple.c32" by
creating a .menu file like the others in tar.gz/menu. However, you
need to recompile your .c32 everytime you make a change to the menu.
simple.c32 and complex.c32 use exactly the same code base. Just that
complex.c32 excercises more portions of the code than simple.c32. IIRC
complex.c32 switches text modes while simple.c32 doesn't.

> O yeah, complex.c32 hangs/crashes to...
>
> Is this fixable? I've tried altering some settings in the BIOS of the
> MS Virtual PC vm (there are very few) but to no avail.
>
> Please help.
>
> Kind regards,
>
> Bart van den Oetelaar
>
>
> ----- Einde doorgestuurd bericht -----
>
> _______________________________________________
> SYSLINUX mailing list
> Submissions to SYSLINUX at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>



-- 
Murali

?????? ?? ??? ????, ???????? ??????
(What we know is only a handful, what we dont is the rest of the world)
_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.





More information about the Syslinux mailing list