Unable to load DLL: VER.DLL
Quote:
>When are users are installing our software on their systems, some of
>them get the error message, 'Unable to load DLL: VER.DLL', and some of
>them don't. Why is this? We had reports of VER.DLL files being 6k on
>one machine and 9k on another. Doesn't the setup.exe program
>automatically copy the ver.dll from the install diskettes? We have the
>latest version of the setupkit files, and I bypassed the setup wizard
>and did everything myself. By the way, what does SETUP.EXE do anyways,
>does it just bring down the files that are listed in SETUP.LST? Is
>there source code for SETUP.EXE out there somewhere. Thanks for the
>help!
When you create your install diskettes, you want to COPY ver.dll
on your machine to ver.dl_ on the diskette. I got this from MS Tech
Support. This will not fix the problem of it not loading the new
ver.dll from the install disk because there's already one running on the
machine doing the install, but that one's pretty much impossible to get
around when you're inside Windows. Microsoft knows all about this, they
just don't care very much. When I started writing installation
programs, I spent several hours on the phone with Tech Support trying to
get answers to these problems.
I'm not sure there's any source around for SETUP.EXE. As far as
I can tell, it decompresses and copies the files that are in SETUP.LST
from the floppy to your Windows directory (or maybe Windows/System.
Since I run Windows off a LAN, I have a private directory that is
effectively mapped to both of those for install purposes, so it's hard
for me to keep track.) Then it runs the first file given in SETUP.LST
(by default, SETUP1.EXE).
--
Adina Adler
My opinions, and
nothing but
