r. mccarty

of writing lots of the same things from scratch you use a DLL (Dynamic
Link Library). It's also done so that programs can be smaller in size. So
if your code needs 100 routines, you use 50 from DLLs and only have
to write the 50 specific to your application. This way your program will
execute it's internal routines and then "Call" the other routines from Dll modules.
"Nehmo" <nehmo54@hotmail.com> wrote in message news:jZ1qf.12938$Dk.5145@tornado.rdc-kc.rr.com...

s.sengupta

http://www.webopedia.com/TERM/D/DLL.html
http://www.maxpc.co.uk/tips/default.asp?pagetypeid=2&articleid=32283&subsectionid=719

regards,
S.Sengupta[MS-MVP]

measekite

Today we call them methods and they can consist of a pure method in that
they do something or a function where they return something.

r. mccarty

Appreciate the info, I guess it show my age. At least I didn't refer
to them as Subroutines.

zakezuke

<Humor - your question has already been answered>

DLL files come in two flavors. Those who hang out resident in memory
and those that are are loaded as needed. What they do? The ones that
stay resident in memory flood your physical memory making sure that
programs, things you actually are using, have to swap to disk ruining
your efficency, and ones that are loaded dynamicly cause conflicts and
result in a crash.

That's what they do... fill up your ram and crash your computer. They
do that very well.

paul w

what machine are you running. I have yet to have these problems.....

Maybe you should get a pro to look at your machine!!

nicolaas hawkins

You really should seek professional attention for that broken funnybone.

--
Talpus Grumpus

bxf

Yes, and we don't need to link them as OVERLAYs either!

tim slattery

DLL = Dynamic Load Library. A DLL is indeed a collection of
subroutines, callable from any Windows program. They are used for all
kinds of functionality. Core Windows functions like creating windows,
menus, minimizing, maximizing, allocating and freeing memory,
thousands more are packaged in system DLLs, and *all* windows programs
call them.

A driver is a special type of DLL, its functions interface between the
way that the Windows OS sees and operates a particular type of
hardware and one manufacturers implementation of that hardware.

I'm not exactly sure what a "printer DLL" would be. My best guess
would be a driver for a particular printer. In that case it would be
for the operating system, not for a particular application.

--
Tim Slattery
MS MVP(DTS)
Slattery_T@bls.gov

zakezuke

Or get a pro to look at his machine and figure out why it's not
operating properly. That blue screen of death is a sign of *Microsoft
Quality*.

Microsoft - "Where the hell did my do***ent go today?!?! ahhh... blue"