OgO said:
In alt.comp.freeware, on 23 Feb 2004, Ranrad announced:
I noticed when I got to the download page however, that there are
two options - the program itself at 220k, or the program with the
windows installer installer at 3.6MB. I downloaded the 220k one
- why on earth would I want to download 3.6MB for a 200k program?
It of course didn't work because I don't have the latest version
of the windows installer installer, whatever useless rubbish that
is
It looks to me that there is an error in the 220k distribution. You can
work around it, though. Use your unzipper to extract d4time50.exe contents
to a folder. You will then have three files:
\D4Time50.msi
\Setup.Exe
\Setup.Ini
The setup.exe has the error. It complains that it cannot find instmsiA.exe.
InstmsiA.exe is the microsoft distributable for MSI (windows installer).
The setup the author used for the small download was evidently mixed up
with the big huge one, that installs MSI.
It's most likely you already have MSI. Look for msi.dll in your sysdir
(current ver is 2x, but this prog might only want ver 1x). In this case,
that you already have msi, you can launch that D4Time50.msi file directly
(delete the setup files), and run the install.
Additional note. I monitor those installs which use MSI, then immediately
discard everything that they have written, registry and disk. All freeware
programs have worked fine this way. The MSI is just a nasty step, before I
can get to use the program, release it from its wrapper. The only program
I have used that actually demands its MSI entries for running is MS Office
products (from ver2000, on). Might be a couple of other large commercial
apps who demand it, too. Yet with all the freeware programs, MSI just means
an enormous amount of crud, which I delete right away.
To have uninstall ability later, when not retaining the MSI installer
litterings, then monitor the program the first time you run it with
something like Total Uninstall (pricelessware.org).
I emailled the author, so hopefully he will fix this situation
soon as I am looking forward to the new version
Better than fixing his setup.exe would be for him to not use MSI in the
first place.