🚀 go-pugleaf

Jon, I'm sorry you felt disappointed in our support for you in these
questions. I have reported this to the appropriate person who will look into
it to see what needs to be addressed. Below are my responses to your
questions. I hope they give you the help you  need.

*** Comctl32.dll ***
Regarding comctl32.dll, you are right that you should not redistribute it.
If you look at Microsoft KB article Q186176, you will see that Microsoft has
strict guidelines on how you are allowed to redistribute this file, and
neither of them lend themselves to use in a setup -- who wants to package up
an IE4 setup in their setup and run it? Also, 401comupd.exe has/had some
problems and has too many qualifications attached to it to make it
practical.

I made a simple VB app with references to all the Microsoft Windows Common
Controls 6.0 components, then ran the IS5.5 VB wizard on it and the PDW. We
got the same files (except for some of the bootstrap and runtime files that
PDW does a bit differently than our wizard does, but that isn't important).

What you can do is determine which versions of the Common Controls your
application was built against, and then determine which versions of
Comctl32.dll and Shell32.dll are required to support them. You redistribute
the OCXs, but you will have to write some code to see if the proper versions
of Comctl32.dll and Shell32.dll are present. If not, your users will have to
install Internet Explorer, or a Windows Service Pack, or one of the items
referenced in Q186176 to prepre the system for setup. I also refer you to
the information on Common Controls and version compatibilities in MSDN under
Platform SDK --> User Interface Services --> Shell and Common Controls -->
Windows Common Controls --> General Introduction. This may help you
understand what you need.

*** Mswinsck.ocx ***
The Wsock32.dll files differ from Windows 95 to NT in both version and in
their dependencies. These files are present on clean/basic installs of
Windows, so they do not need to be redistributed. The VB Wizard in IS5.5
should filter/avoid this file, but does not. You can make it filter
WSOCK32.DLL and WS_32.DLL and WS2HELP.DLL by adding a FILE<n>= entry for
each to the Vbwizdep.ini file in your InstallShield's Program\Wizards\Vb
folder. Make sure you get the <n> numbers correct -- sequential one-up
values with no missing values in sequence; also make sure filename is in all
uppercase letters.

*** Riched32.dll ***
Windows 95, Windows 98, and Windows NT 4.0 each has its own version of
Riched32.dll that does not work properly on the other two operating systems.
To ensure that your application using Riched32.dll runs properly on each
operating system, you must do one of the following:

>> Include the version of Riched32.dll included with Visual Basic 6.0, which
works on all three operating systems.

>> Include all three OS-specific versions of Riched32.dll, and install the
one that is appropriate to the target operating system. To do the latter,
place each version of Riched32.dll in its own file group. Then set the
properties of each file group so it is installed only on the operating
system to which its version of Riched32.dll is appropriate.

*** Crystl32.ocx ***
Exactly what is the conflicting advice? File list differences? Remember that
PDW includes bootstrap and some other setup-related files that are specific
to how it/they (MS) do setups, so there will never be an exact file-for-file
correspondence when you compare the results of PDW versus VB wizard.

In <376a6b06.0@news.installshield.com>, news.installshield.com
<barry@installshield.com> wrote:
>*** Comctl32.dll ***
[...]
>Also, 401comupd.exe has/had some
>problems and has too many qualifications attached to it to make it
>practical.

Care to elaborate?

 - Katy