ms said:
I found at that site a 1.6 MB (or so) install at that site, did I miss something?
I went to the site to retrieve the original package tonight.
http://members.shaw.ca/fworsley/ftm201.zip
The download file is big, yes, 2.6mb. That's because it's including buncho
VB runtimes.
There is a ruling conspiracy which dictates that all avid freeware users
are required to download the same VB runtimes, over and over, thousands
of times in their life.
There is one relief. I believe that trend is finally, at long last, on the
downswing. I see it more often in circa 99-2002 software. More developers
now let you download their VB program without all the huge bulk, maybe
providing an optional link, or optional setup package, for those users
that are unsure about whether they already have updated runtimes.
In place of that older trend, however, I'm noticing that in recent software
I've been having to download the large C++ runtimes + MFC dlls (msv*.dll
msc*.dll) over and over....
Unzipping ftm201.zip gives a small setup.exe, a setup.lst, and then a
large .cab. So then I extract the .cab contents (7zip says "hi!"). I
pull out the unique files. That's the program's exe and its ocx. Also
some html help files (html jpg css) which I put into their own subfolder.
What I leave behind -- delete -- are the redundant libraries which I
already have: msvbvm60.dll, comdlg32.ocx, msvcrt.dll, etc.
When I want to make sure my versions of the files are equal or newer, or
if it's something less familiar than the VB etc stuff where I've forgotten
whether I have a particular library, then I run NodeSoft's FileVer. I
drag the download files onto its window, to have it compare versions
against those in my sysdir.
http://www.nodesoft.com/Filever/
I also delete from the extracted cab, and the original zip, the files
related to setup or uninstall: eg, vb6stkit.dll st6unst.exe setup1.exe.
Truer to say I ignore them (the setup related files) initially. Then I
delete them once the prog has run successfully and proven that it wasn't
one of those oddballs that lacks the ability to write all the regkeys it
might need when it is run.
Before launching the program for the first time, I make sure that I have
an installation logger prepped up. For my purposes InCtrl suits me. I also
have my system configured to always have a TUN pre snapshot available in the
background, for cleanup rescue if a prog creates a really serious mess.
Then I launch. Since the prog has an OCX, and same as if it came with
registering DLLs, I watch to see whether it knows how to find them itself
and register them when run. My rough estimate is that about 2/3 of the
programs are smart enough to do this. If they fail that, there is usually a
program error dialog, and that is my immediate clue that I need to register
the libraries myself (regsvr32 or similar). The installer for such programs
would have done the register thingy, of course, but ugh, installers indulge
in also writing all manner of debris that is not needed.
Anyway, in the case of this program, FTM, it does know how to register its
OCX, automatic.
So, in essence (long story short at last):
You'd just pull from the .CAB the two main program binaries, ftm2.exe and
tcol2.ocx, plus the html help files.