CD boot "vesamenu.c32 not a com32r image" Bug ! [SOLVED]

[Lassar]

I used remasterssys on a Pinguy Ubuntu install to make a live cd.

Found remasterssys on the install already.

I put the CD in the CD drive and rebooted.

I got this at start up.

"vesamenu.c32 not a com32r image" error

Then shows a boot prompt.


I did some googling, and it seems to be related to the version of syslinux.

Anyone has a solution to this problem ?

[lkjoel]

I don't get: "I put the CD in the CD drive and rebooted.". What CD? The remastered one? Could you give more details?

[Lassar]

I put the remaster CD in the cd drive.

I figured out the problem. There is a bug in the remastersys script.

It copies a different version of vesamenu.c32 to the home/remastersys/remastersys/ISOTMP/isolinux/ folder.

Code:

# check and see if they have a custom isolinux already setup. eg. they copied over the isolinux folder from their original livecd or made a custom one for their distro

if [ ! -f /etc/remastersys/customisolinux/isolinux.cfg ]; then

find /usr -name 'isolinux.bin' -exec cp {} $WORKDIR/ISOTMP/isolinux/ \;
find /usr -name 'vesamenu.c32' -exec cp {} $WORKDIR/ISOTMP/isolinux/ \;

# setup isolinux for the livecd

VERSION=`lsb_release -r | awk '{print $2}' | awk -F "." '{print $1}'`

sed -e 's/__LIVECDLABEL__/'"$LIVECDLABEL"'/g' /etc/remastersys/isolinux/isolinux.cfg.vesamenu > $WORKDIR/ISOTMP/isolinux/isolinux.cfg
cp /etc/remastersys/isolinux/splash.png $WORKDIR/ISOTMP/isolinux/splash.png

else

cp /etc/remastersys/customisolinux/* $WORKDIR/ISOTMP/isolinux/

fi

The bug in this line "find /usr -name 'vesamenu.c32' -exec cp {} $WORKDIR/ISOTMP/isolinux/ \;"


There are three "vesamenu.c32" on my ubuntu system.

This line finds the wrong "vesamenu.c32" on my ubuntu system.

The fix would be to find isolinux.bin directory, and copy "vesamenu.c32" from that directory.


I found a work around.


You will have to do a search in the file manager for isolinux.bin. vesamenu.c32 is in the same folder.

Splash.png is found in /etc/remastersys/isolinux

Copy your isolinux.bin, vesamenu.c32, and splash.png to /etc/remastersys/customisolinux/

copy /etc/remastersys/isolinux/isolinux.cfg.vesamenu  to /etc/remastersys/customisolinux/  and
rename it to isolinux.cfg

[fragadelic]

I put the remaster CD in the cd drive.

I figured out the problem. There is a bug in the remastersys script.

It copies a different version of vesamenu.c32 to the home/remastersys/remastersys/ISOTMP/isolinux/ folder.

Code:

# check and see if they have a custom isolinux already setup. eg. they copied over the isolinux folder from their original livecd or made a custom one for their distro

if [ ! -f /etc/remastersys/customisolinux/isolinux.cfg ]; then

find /usr -name 'isolinux.bin' -exec cp {} $WORKDIR/ISOTMP/isolinux/ \;
find /usr -name 'vesamenu.c32' -exec cp {} $WORKDIR/ISOTMP/isolinux/ \;

# setup isolinux for the livecd

VERSION=`lsb_release -r | awk '{print $2}' | awk -F "." '{print $1}'`

sed -e 's/__LIVECDLABEL__/'"$LIVECDLABEL"'/g' /etc/remastersys/isolinux/isolinux.cfg.vesamenu > $WORKDIR/ISOTMP/isolinux/isolinux.cfg
cp /etc/remastersys/isolinux/splash.png $WORKDIR/ISOTMP/isolinux/splash.png

else

cp /etc/remastersys/customisolinux/* $WORKDIR/ISOTMP/isolinux/

fi

The bug in this line "find /usr -name 'vesamenu.c32' -exec cp {} $WORKDIR/ISOTMP/isolinux/ \;"


There are three "vesamenu.c32" on my ubuntu system.

This line finds the wrong "vesamenu.c32" on my ubuntu system.

The fix would be to find isolinux.bin directory, and copy "vesamenu.c32" from that directory.


I found a work around.


You will have to do a search in the file manager for isolinux.bin. vesamenu.c32 is in the same folder.

Splash.png is found in /etc/remastersys/isolinux

Copy your isolinux.bin, vesamenu.c32, and splash.png to /etc/remastersys/customisolinux/

copy /etc/remastersys/isolinux/isolinux.cfg.vesamenu  to /etc/remastersys/customisolinux/  and
rename it to isolinux.cfg

That is not a bug in remastersys.  That is a bug in PinguyOS.  You should let them know so they can fix it.  Why on earth would there be more than 1 instance of any application?  Maybe it was overlooked on their part.

[lkjoel]

That is not a bug in remastersys.  That is a bug in PinguyOS.  You should let them know so they can fix it.  Why on earth would there be more than 1 instance of any application?  Maybe it was overlooked on their part.

I'm sorry for reviving this thread, but I'll tell you that I have the same thing. For some reason, some programs have their own version of it (some virtual machines, which I forgot the name of).
I don't get it either, but it's not Pinguy OS's fault.

Hope this helps to clarify things!

[fragadelic]

Here we go again Joel.  This issue was fixed in remastersys 3.0.0.

I'm really beginning to think you just want to make remastersys look bad to promote your own project.

[lkjoel]

It was solved? I just wanted to give a +1 to this question, saying that it's actually true, and it's not a problem with Pinguy, but rather with those programs that make their own copy of ISOlinux (btw, relinux has the same problem, so you can't say that I'm advertising about it).

[fragadelic]

I've asked you before to check the current code before posting and you haven't done that.

The actual solution was provided by Krasimir the guy who made the current gui for remastersys.

[fragadelic]

It was solved? I just wanted to give a +1 to this question, saying that it's actually true, and it's not a problem with Pinguy, but rather with those programs that make their own copy of ISOlinux (btw, relinux has the same problem, so you can't say that I'm advertising about it).

What is the purpose of having more than 1  instance of vesamenu.c32 on a system especially when the others don't work.  This IS a bug on the system or with some packages on the system that provide invalid versions of the file.  That's like saying you have 3 instances of bash on the system and have to figure out on your own which one to use.

In either case it was fixed even though it hasn't been an issue on any system I've built ever.  What you need to do is figure out where the other ones come from and then decide if that package is really needed since it provides a non-working version of syslinux.

[lkjoel]

Exactly. I think that the only reason why programs do that is because they need a customized version of it. I've seen a few virtual machine emulators do this. I don't get it either.
I recommend you use the one from /usr/lib/syslinux. I think that one is the good one.

[fragadelic]

And if you do that you will not support one of the most popular offshoots of Ubuntu which is why I had to search for it in the first place.

Don't you think that after 5 years of doing this I have reasons for why they are done the way they are?

[lkjoel]

uh, what? Isn't the correct isolinux.bin at /usr/lib/syslinux? I don't get what you mean.

[fragadelic]

The most popular offshoot of Ubuntu used(uses) a different setup that works and when I only looked in /usr/lib/syslinux it failed.

[lkjoel]

oh ok. So what is the offshot? Sorry, I don't exactly understand what you mean.

[fragadelic]

Linux Mint

[lkjoel]

Oh ok. Maybe a check then? The reason is that some programs make their own version of isolinux, screwing it up.

[fragadelic]

lol - the new check I put in 3.0.0 works fine even for mint.

[lkjoel]

Oh, so a check would be needed then.

[Kit Carson]

L'errore "vesamenu.c32  attempted Dos system call", durante il boot da DVD non dipende dalla versione di Linux ma dalla Mainboard che si possiede. Io ho il problema di fare il boot di tutte le edizioni di Linux dalla Mia MainBoard PCChips M810 mentre su altre MainBoard  il problema non esiste. Qualcuno sa se l'errore sta nel bios e per quale motivo? Sulla stessa MainBoard PcChips M810 il Boot da DVD con systemi Microsoft avviene regolarmente.