Doug (et al),

As you pointed out, chances are very good that the
scanner is a USB device or the PC has dual printer ports
(very rare).

DLL files (of any variety) are not "built" (or rebuilt) at the
time of installation, they are simply replaced with newer or
customized versions.

And this could be the original posters problem -- a compatibility
issue not a corruption problem.  A customized version of the twain
or twunk DLLs was loaded by a second device and the new DLL
is not compatible with the older device.

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

>
> Most PC's don't have two parallel ports that I work with.  Since both the
> devices plug into the computer, wouldn't that mean that the scanner is
> probably *not* parallel port?
>
> Carol, I have three scanners, various varieties and connection types, and
> the biggest problem that I have encountered with them is corrupting the
> Twain.dll, Twunk_16.exe and Twunk_32.exe and several other variations of
> these two files.  I *think* that the Twain* and Twunk* files are rebuilt
> each time you add a twain compliant device to your machine.  For example I
> use both the scanner and a Quickcam on my machine and it looks like it
> rebuilt "some" of these files when I installed the second device.  This
> leads me to believe that more info is added to them (or they are initially
> built if they don't exist) when the software drivers are installed.  I
have
> fixed them by renaming (to recover later if it doesn't work!) all the
Twain
> and Twunk files, then reinstalling the scanner software.  Maybe you could
> give this a try.

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