GOOGLE got a point.
I didn't have the slightest idea on the initial "/boot/vesamenu.c32: not a COM32 image" , but I was spectical on your statement "I tried to google the message, but could not find a relevant solution." , so I googled .
The link given was the six or seven from the list shown.
Try google and read thru at least the first page of the results.
Sorry, my bad! :-) I googled for the "/boot/vesamenu.c32 ...." (without quotes) again. This time I got the solution in the very first result. Probably I should not have used the quotes. When I added quotes Google Instant threw this message at me -
No results found for "/boot/vesamenu.c32: not COM32 image".
After getting the
Fatal error occurred - Can't find executable chroot command
I rebooted into Ubuntu and formatted the pendrive. Thereafter, I downloaded the tarball from Slax, untarred it to my freshly VFAT formatted pendrive and tried to run .bootinst.sh with the following command -
$ sudo bash .bootinst.sh
from within the pendrive's boot folder.
However, I got the following error -
boot/bootinst.sh: line 53: ./boot/syslinux/lilo: Permission denied
I tried to change permissions to boot/syslinux/lilo , without success. Then I realised that the filesystem was VFAT. So I unmounted the pendrive and manually mounted it back. This time I was able to change the permissions.
Then I executed bootinst.sh from the pendrive boot folder.
This time I succeeded in making the pendrive bootable.
But when I tried to boot from the pendrive, the booting process abruptly halted with the following message -
Buffer I/O error on device ram0, logical block 93...
Kernel panic - not syncing: No init found. Try passing init = option to kernel.
Now I am going through some of the results thrown at me by good old Google.com. I'll keep you posted. If in the meanwhile, you have any idea about what is going on, I humbly request you to help me out.
Thanking in advance,