How to recover mysql db from .myd, .myi, .frm files

One thing to note:
The .FRM file: Regardless of the storage engine you choose, every MySQL table you create is represented, on disk, by a .frm file, which describes the table's format (i.e. the table definition). The file bears the same name as the table, with a .frm extension. MySQL stores .frm files in datadir/database_name (If u don't know where is located your datadir then see your <mysql_install_dir>/my.ini file's #Path to the database root) .frm file is specific to your MySQL version.
The .MYD file is NOT specific to version, at least not minor versions.
The .MYI file is specific, but can be left out and regenerated with REPAIR TABLE.
Recover MySQL DB:
1. Create a dummy database (say vmdb)
2. Copy all these .myd, .myi, .frm files to mysql\data\abc wherein mysql\data\ is the place where .myd, .myi, .frm for all databases are stored.
3. Then go to phpMyadmin, go to db vmdb and you find your database!

Do Before Publish Your Android Application

Preparing and packaging an application for publication is called the release process. The release process is an exciting time: The application is stable and working as expected, all those troublesome bugs have been resolved (within reason, at least), and you feel that you’re ready to put your app in front of users.

The final build you perform - the build you expect to deliver to users - is called the release candidate build. The release candidate build should be rigorously tested and verified before it reaches users’ hands. If the release candidate build passes every test, it becomes the release build - the official build for publication.

An unhandled win32 exception occured in emulator-arm.exe

An Android Virtual Device (AVD) is an emulator configuration that lets you model an actual device by defining hardware and software options to be emulated by the Android Emulator. For more information u can read from developer.android.com


When u debug your Android application in eclipse on win32 u may be see exception as following:

An unhandled win32 exception occured in emulator-arm.exe [xxxx]