Kermit 95 requires that the Telephony API (TAPI) be configured
for the machine for all users of the machine. The Telephony
subsystem is configured using the Phone and Modems Options
control panel. If TAPI has not been configured, TAPI will
attempt to prompt the user for configuration data the first time
the subsystem is activated by an application. If the user
account under which the application is started does not have the
necessary privileges to make changes to the local machine
configuration (they are not Administrator), the application which
uses TAPI will fail to start properly. In the case of Kermit 95,
this means that while the Kermit 95 GUI Window (or console
window) may open properly, the application will be unusable for
about two minutes until the TAPI subsystem fails. The fact that
the TAPI subsystem is left unconfigured after the Kermit 95
installation should be considered a bug in the Kermit 95
installer. The installer really should query TAPI to force the
configuration of the machine.
As we've discarded the original installer and yet to build something new, any bugs related to the old installer don't really apply. So this issue is really a reminder to avoid recreating this bug in whatever new installers come along.
From the K95 bugs list:
As we've discarded the original installer and yet to build something new, any bugs related to the old installer don't really apply. So this issue is really a reminder to avoid recreating this bug in whatever new installers come along.