The following is from Mike,
KH6ND, who spent countless hours resolving
a problem installing the
MMTTY Plug-in for WriteLog. Mike found the
problem was caused by having
McAfee VirusScan 4.02 or 4.03 installed on
the computers he was having the problems with.
This is what Mike writes:
When installing the MMTTY Plug-in for WriteLog, I received the following
error message.
One or more files did not
properly self-register.
Following files did not
self-register:
1.
c:\ham\programs\MmTtyTnc.dll
One of the library files needed to run this application
cannot
be found.
I initially went through all
of the steps talked about on the WriteLog
reflector to solve a
somewhat similar problem listed at:
http://support.installshield.com/kb/view.asp?articleid=Q104985
but these were of no help,
as I suspected they would not be, due to the
last line of our particular
error message. It didn't sound like one of
the other install shield
related problems, but was worth a try.
I loaded the plugin on the
Win 2000 laptop that I have been forced to
use for RTTY during the past
month with no problem. But I have two
desktop machines that were
generating this same error message. One runs
Win98SE, and the other
Win95, which I upgraded to Win95a via the Win95
service pack (1) recently,
as I tried to solve this puzzle on that
machine. I also tried
reinstalling earlier versions of WriteLog, MmTty,
and the plugin as per
Steve's suggestion, in many, many different
combinations without
success. And I tried re-installing the Win98SE
upgrade on the 98 machine
several times, hoping that the missing .dll
file would show up, but
that, and a lot of other things that I tried
were dead ends.
One week ago, a good friend,
KH7U, came to the station to operate the
Hawaii QSO party while I was
doing the SCC RTTY. We loaded WriteLog,
MmTty, and the MmTty plugin
on his Win98SE laptop without a hitch.
Seeing is believing! Now I
was more motivated than ever to figure this
out.
I went to the Google search
engine this week, and started my search with
"self-registration
error". Here I started to make some headway, bits and
pieces here and there, I
created a new bookmark folder and saved every
site I found with any info
at all as I proceeded. Then I ran across the
following web site:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q268113&
This site contained the
following:
"These issues can occur
if you are using McAfee VirusScan 4.02 or 4.03.
These versions of McAfee
VirusScan add an incorrect version of the
Windows Imagehlp.dll
file."
Bingo! It seemed like I had
found a common thread, as both of my
machines have had McAfee
VirusScan 4.02 on them in the past. But I don't
use it any more because of
another problem with a log file that it runs
that eventually bogs down
and crashes many systems. Anyway, this seemed
to be a very likely
commonality. Shortly after this, I surfed my way to
what ultimately provided the
solution. Be sure to check this site out:
http://www.dependencywalker.com/
Here you can download a
great free utility that will show you all of the
file dependencies of any
file that you open in it, and very detailed
information about all of
them. Once I plugged MmTtyTnc.dll into this,
the path seemed pretty
clear. Not only does this guy tell you what files
are being used, it also
tells you which are needed, but not resident on
your system, and it does it
in red ink! The rest was a matter of
locating the correct
versions of the missing .dll files, some via
Internet search, and some by
examining the contents of each of the cab
files on the windows
installation CD's.
The fix for the 98 machine
was a simple matter of finding and installing
only one .dll file to the
windows/system folder. Yep, Imagehlp.dll. The
95 machine was more
complicated due to a system crash along the way, but
consisted of adding the
Win95 version of the missing Imagehlp.dll
(thanks again, McAfee), and
replacing the Comctl32.dll Win95 file, with
the same file from Win95b,
which is considerably larger in size. My
original Comctl32.dll was
showing partial "red ink" when examined in the
Depends.exe utility. Be sure
to make copies of any files that you
attempt to overwrite as I
did this one, and put them in a place easy to
access from DOS (like a
floppy drive) BEFORE you overwrite, in case of a
system crash. You can then
manually copy the original back to the
windows/system folder if
necessary with the copy command in DOS.
So... now I FINALLY have two
real RTTY computers, and a laptop for
backup.
Thanks Mike for all your
hard work in resolving this problem and providing
The solution to WriteLog
users. For specific questions
concerning the
Solution, contact Mike at kh6nd@lava.net.