I am working on a particular project (up and coming) which involves a couple
of external DLL files. Normally, I know they should be left alone so multiple
programs can access them, but in this particular case this is a one instance
installment with no follow ups.

Meat of the question is, since I dont need to have them external per se, can
these DLL files be built into the exe directly via the special file directive and
still be usable? I am thinking the answer is no, but I have found over time
that there is little you cannot do in assembly if you know how.
Posted on 2002-10-24 14:22:05 by Graebel
The answer is: you can do that. ;) Simply put your dlls as binary resources, then load and use them in almost usual way.
Posted on 2002-10-29 21:12:23 by Alex Smith

To get information about dll binding / embedding, you can check the thread:


Here is also my example converted to FASM.

The include file "Mydata.inc" contains the "binded" dll. This .inc file is an output of bin2db tool provided by Masm32 package.(Thanks Hutch!)


Posted on 2002-11-03 08:56:16 by Vortex