Bug 872 - Installation of DIRSIG on PC does not complete
Summary: Installation of DIRSIG on PC does not complete
Alias: None
Product: DIRSIG4
Classification: Unclassified
Component: Installation (show other bugs)
Version: 4.4.1-beta
Hardware: Other Windows 32-bit
: P5 normal
Assignee: Scott D. Brown
Depends on:
Reported: 2011-02-10 01:02 EST by David A Bennett
Modified: 2011-09-16 11:57 EDT (History)
0 users

See Also:

Screen snap. (323.28 KB, image/png)
2011-02-10 01:02 EST, David A Bennett

Note You need to log in before you can comment on or make changes to this bug.
Description David A Bennett 2011-02-10 01:02:48 EST
Created attachment 240 [details]
Screen snap.

During the installation process, i get a message saying that the make_weather.exe binary cannot be installed because of directory permissions.  However, within this directory, there are already other executables that have already been coppied to this directory.  I have attached a screen shot to illustrate the issue.
Comment 1 Scott D. Brown 2011-02-14 12:28:36 EST
The LM virus software thinks that make_weather.exe is a virus.  I don't know how people are getting around it, but I had the same issue with LMCT, Orlando, etc.
Comment 2 Scott D. Brown 2011-02-16 15:38:58 EST
Using the command line MSI installer tool with verbose logging turned on is best next step.  The Microsoft page link I sent has all of the options on it, but here is a simple syntax to try (substitute for the .msi installer you have):

msiexec /i dirsig- /L*v "C:\temp\install_log.txt"

Terry at LMCT said that when they manually installed this way they caught the custom version of McAfee that LM deploys was stepping in and stealing the make_weather.exe file.  Apparently it somehow matches a signature of a "bad file" in McAfee land.  Only LM McAfee users complain of this problem.  I poked Terry and he said that the "disabled McAfee" to get the installer to run.
Comment 3 Scott D. Brown 2011-09-16 11:57:49 EDT
I didn't hear back form you Dave, but I am marking this as "resolved" because I suspect it is that funky LM virus scanner issue again.