Joe,
The .exe file self-extractor was supposed to be fool proof but maybe its
not working right in the case of your particular machines. Please give
this a try:
1. You must have the FULL install of WL63 NOT the .exe file with "upg" in
its name. If that is not the case, then talk to Ron, get the right
download, and ignore the rest of this message.
2. When you run the .exe, in the dialog that comes up, turn OFF the "when
done unzipping...setup.exe" button.
3. change the "unzip to folder" to the name of an empty or a new folder on
your machine.
4. Click OK, and that empty folder will now have 4 files in it (Setup.exe,
SetupWLFull.exe, WlFull01.cab, and writelog.setup_msi
5. now run that setup.exe using your favorite way to launch a program. You
can use Windows explorer, or type its full path into the Start Menu Run
command, or whatever. Does the setup fail again?
6. If it fails again--one last shot. If step (5) did not rename that last
file to "writelog.msi", then rename it manually. Then double click on
writelog.msi and it should attempt an install. Does this one fail, too?
Wayne
> Hi guys. I just received our new Writelog 10.63H key last week for our
> club station at 'The Boeing Company' here in St. Louis for W0MA.
>
> I went to our club trailer and started to install this version over our
> previous version. The installation started OK and deleted the old
> version. It stopped and gave the following error message:
>
> "Writelog Version 10.63 Setup
>
> There is a problem with this Windows Installer package. A DLL required
> for this install to complete could not be run. Contact your support
> personnel or package vendor."
>
> Let me tell you the setup. We have four (4) IBM PC's with Windows2000
> SP3 on a LAN. I guess we received them about 2 years ago from the
> company. Writelog has worked perfectly on all machines.
>
> So you can imagine my disappointment when the installation did not
> complete as we are getting ready for CQWWRTTY. I got the same error on
> two machines. I did not try the other two as since it uninstalls the
> version that is working, I did not want to have reinstall on all the
> machines.
>
> I know this is a W2K problem. I just wonder if anyone else had this
> problem and what DLL is missing?? The MFC dll is installled an is the
> latest version. I been searching the WL Archives for any answers but
> was not able to find any.
>
> Again, it is Windows2000 and not XP.
>
> Joe K0BX
> for W0MA (McDonnell Douglas home of the F18)
>
>
>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|