Skip to main content

vesamenu.c32 Not a COM32R image on booting from USB Flash - Linux Mint

I have been recently faced with "vesamenu.c32 Not a COM32R image" error lot of time while booting Linux Mint bootable USB flash made using "Startup Disk Creator" and had no clue what to do. I was thinking that this is due to USB drive space issue or physical problem itself. Then I jumped on to the Google surf board and found a single word correction to solve the issue. Thank you for all you guys who relentlessly try to solve these kind of trivial issues for us.

The procedure follows. Once you finish making a USB flash bootable via the "Startup Disk Creator".

go into the "syslinux" folder.
edit the "syslinux.cfg" file.

change "default vesamenu.c32" to "default live" and everything should be working fine now.


Quinn said…
This worked perfectly for me, too. Thank you!

Popular posts from this blog

Create Great looking diagrams -

I was looking for an online diagram creating tool. Came across where I could create actually great looking diagrams without much of learning curve. The tool is 1. Very easy to use 2. Has drag and drop of elements to your diagram 3. Collaboration (which I have not tested). 4. Works from anywhere on a browser with Internet connection (I used it in Google Chrome on Linux Mint 10) When you click on the "Try it now" a new screen will open as below. You can either create a blank page to create a diagram from scratch or select from a bunch of samples and work on them to create one for your requirement. There are options to export the diagrams you created to SVG, JPEG, PNG and XML format once you register for free on the website. Once you register you can save the diagrams that you created in the site itself and retrieve it at a later time by logging into the website. I made three diagrams and it was real easy and simple. The site has two kind of pa

Kerio Connect - SQLLite journal.db error

Today I noted that the Keio Connect mail server had thousands of error.log files with 75MB size filled up in the server. As always Google gave the answer. The error looks some what like below. [10/Aug/2011 10:49:35] SQLiteDbWriteCache.h: write_thread - file '/path/to/file/<user>/.journal.db', SQLite error: code 1, error SQLITE_ERROR[1]: no such table: journal_temp The solution is as below 1. Delete the cache from the client's workstation 2. Delete the profile 3. Stop the server 4. Go to the server and navigate through the user's store folder 5. Delete the .journal.db (for Linux it is  find . -name "FILE-TO-FIND"-exec rm -rf {} \; ) 6. Start the server 7. Create a new profile for the clients workstation With help from Kerio Forum Cyberciti