You should upgrade to 4.4.3. The build system was totally redone to generate solutions with cmake. But to answer your question if it is asking to have alld42.dll then you are linking to a debugging version of allegro. You have to change your linker settings for your project in release mode. There were also numerous bug fixes and a few necessary fixes in the gfx_mode_select* dialogs.

Every dll (dynamic link library) is associated with a *.a archived symbol library or in your case *.lib. That means you are linking to the wrong *.lib (ie, not the one associated with alleg42.dll. You link to a lib file and then run with a dll alongside your exe.

Which lib files did your binary distribution come with? There should be 4 main kinds - dynamic, dynamic debug, static, and static debug.

Okay he made profiling versions too.

The one you want for release mode is alleg.lib. The _s is for static. The d is for debug and the p is for profile.

If you're running it from the IDE, your working directory might not be what you want it to be when the program runs, corrupting relative paths to files. That would make them fail to load. You can also make a debug build now, with alld.lib. If your program is crashing, you need to debug it. Post your code if that is the case.

No. alleg.lib is the dynamic archive library for allegro 4. When you link to alleg.lib your program becomes dependent on alleg44.dll or whatever its called.

Welcome. The paths I was speaking of are the paths to your resources that you are loading in your code. You may find that you have all your resources in place, but it still doesn't load. If that happens the current working directory is most likely wrong, and you would have to change it with :

ALLEGRO_PATH* p = al_get_standard_path(ALLEGRO_RESOURCES_PATH);
if (!p) {Fail();}
al_change_directory(al_path_cstr(p , ALLEGRO_NATIVE_PATH_SEP));
al_destroy_path(p);

And the message box won't show up unless you code it to.