Doug,

When an application needs a DLL file, it will first look in it's own
directory.  If it can not find the DLL there, then it will look in the
Windows and/or Windows\System folders.

I __think__ that if you make sure the proper DLL is in the "owning"
application's folder, you can have both DLLs available -- each to it's own
app -- and they _should_ live in harmony.  At least it works with other
DLLs -- but I'm not so sure about twain and/or twunk files.


----- Original Message -----
From: "Doug Simmons" <>

> At 2/21/00 05:29 PM -0500, Jim Meagher wrote:
> =========
> >DLL files (of any variety) are not "built" (or rebuilt) at the
> >time of installation, they are simply replaced with newer or
> >customized versions.
> =========
>
> In that case, I think that I am seeing a newer DLL being replaced by and
> older one when I install a second device.  I have two parallel port
> scanners connected to one machine (3 parallel ports being used).  I know
> that I have to install one of them before the other or they don't work.
>
> Thanks for the clarification, Jim.
>

                Curious about the people moderating your
                   messages? Visit our staff web site:
                     http://nospin.com/pc/staff.html