1. Support for relative paths
   InstallFromTheWeb 3.1 supports relative paths from the installation Web page to the run-time reference file. This feature allows you to configure your Web site in a way that is easier to maintain, and does not require you to change the location of your installation files whenever you change the design of your site. This feature allows you to have your installation files hosted by a third party server and separate your actual installation files from your Web site content. Doing so greatly increases the bandwidth necessary for facilitating numerous users attempting simultaneous downloads.

2. InstallFromTheWeb 3.1 features an enhanced installation Web page.
   The installation Web page produced by the design-time wizard installs the appropriate client file for end users who do not have them installed. For Internet Explorer and Netscape 4.x and higher browsers, the installation Web page installs the client and then refreshes the browser window so that installation from the Web may occur. For Netscape 3.x users, a popup window is displayed that provides a link to the location of the client files as well as instructions for installation. After the client has been installed, a link on this popup window refreshes the initial installation Web page so that installation can occur. The new Installation Web page does not redirect the end user to numerous Internet URLs, and makes the process of installing the latest client version seamless with the Web installation.

3. Building Web Installations in Silent Mode
   You can use the InstallFromTheWeb's -a -s command line switches together to rebuild a Web installation without viewing the Design-time Wizard. You may use this method to update your installation as part of batch process.

   If you rebuild a Web installation in silent mode, a log file will be generated in the same directory as your project file. This log file is named <projectname>.log.

   This log file contains all the information that is displayed in the Build Panel of the Design Time Wizard. For example, errors that have occurred during the build, files that are included in your project, and when the build started and ended are contained in this file.

4. Smaller Netscape Client
   In an effort to reduce download times required by end-users, the Netscape client for InstallFromTheWeb has been drastically reduced in size. In previous versions the Netscape client was approximately one megabyte in size, compared to 616k in InstallFromTheWeb 3.1.

5. Improved Support for Secure Web Servers
   InstallFromTheWeb 3.1 features improved support for secure Web servers. If a request for a file is unable to be processed due to an error with the certificate, the end user is alerted of the problem and given the option to continue. In previous versions of InstallFromTheWeb, an error message was displayed that terminated the installation.

6. Improved Timeout Handling
   InstallFromTheWeb attempts to retry a connection three times after a timeout interval has elapsed. Timeout occurs more quickly than in previous releases.

7. Choosing Wizard Styles
   In an effort to optimize InstallFromTheWeb 3.1 for InstallShield Professional 6.x installations, a choice between two different end-user wizard styles is offered. Choosing an end-user wizard style allows you to create a seamless transition between the dialogs shown prior to and during the download of the installation files, and those displayed by the setup program. For example, if you are using InstallFromTheWeb to rebuild projects that Web enable InstallShield Professional 5.5 installations, the dialogs that are displayed to the end-user appear very much the same. However, if a new Web installation is created using InstallFromTheWeb 3.1, Wizard 97 style dialogs are displayed to the end-user that closely resemble those used during InstallShield Professional 6.x installations.

8. Improved Handling of Web sites that Require Authentication
   InstallFromTheWeb 3.1 features improved handling of Web sites that require authentication. If the Web site is protected NTLM authentication InstallFromTheWeb can gain access to the resource without prompting the end user. For sites protected with basic authentication, the authentication prompt no longer contains a user name of anonymous.

9. Separation of Web site content and Setup Downloads
   It is now possible to store your run-time reference file in the location contained in your installation Web page, and locate the other necessary installation files elsewhere. The files that are required for setup are downloaded from the host site that is selected by the end user. Previously, these files were always downloaded from the same location as the run-time reference file.

10. Improved Handling of Corrupted Files
    InstallFromTheWeb 3.1 checks the integrity of files that are downloaded prior to setup initialization. Previously, only files downloaded while the setup was running were checked for corruption. If a corrupted file is encountered, three attempts are made to download it.

1. Enhancement: InstallFromTheWeb Client for Netscape 4.x users installs automatically.
   Previously, Netscape users were required to download and save the Client file to their system, navigate to the file, run it, and then restart their browser.

   In this release of InstallFromTheWeb, the Client is automatically installed, eliminating the need to perform any of the steps above.

   As an InstallFromTheWeb developer, you do not need to take additional steps to use the auto-installing Client. During setup, simply enter the address where you want the Client files to be stored, just as you have done with previous versions of InstallFromTheWeb. The Client location will be entered in the Validation template (clientcheck.htm) and the Installation page template (iftw.htm) for you. The link to your installation Web page is also entered automatically for you.

   In order to benefit from automatic Client installation, Netscape users must be using at least a 4.x version of the browser and have Java, JavaScript, and AutoInstall (for Netscape 4.0-4.05 users) or SmartUpdate (for 4.5 users) enabled. The default settings for Netscape have Java, JavaScript, and AutoInstall enabled. However, if users have changed these settings and want to set them back, they can access the appropriate dialog for setting these properties by selecting Edit | Preferences | Advanced from their Netscape browser.

   For additional information on the auto-installing Client, please see the InstallFromTheWeb help file topic, "Automatically installing the Netscape Client".

2. Enhancement: New Validation Template Checks System Requirements
   In conjunction with offering the automatic installation of the Netscape Client, InstallFromTheWeb now generates a preliminary Validation page that your customers will see first (before the Web page offering your installation). The page, that is named "ProjectName.htm", includes a script that determines if the end user needs to download the Client or update to a newer version of the Client. If needed, Client installation for Netscape users takes place from this page.

   Once the Client installation is complete, users can click a link on the Validation page that directs them to the installation Web page that they install your application from. The Validation page also detects if users have the most recent version of the Client and if so, automatically redirects them to your installation Web page.

3. Change: ActiveX Control recreated using ATL
   Previously the InstallFromTheWeb control (IFTW.ocx) was dynamically linked to the Microsoft file MFC42.DLL.  The new control, now named IFTW.DLL, has been recreated with ATL to remove this dependency on MFC42.DLL.

4. Enhancement: InstallFromTheWeb automatically reattempts download if a file fails verification.
   Every file in your Web installation is checked for accuracy when it is downloaded to ensure that the file did not become corrupted in the process of file transfer.   Previously, if a file failed the verification check, users were immediately presented with a dialog that informed them about the verification error and gave them the option to attempt another download.  Now, InstallFromTheWeb automatically retries download of the corrupt file up to three times.

   Since InstallFromTheWeb now automatically retries download in the event of file corruption, no Retry or Ignore Option is presented to users if a file is still being reported as corrupt after three tries.  It is presumed, at this point, that there is a problem with the file hosted on the server. Users must exit the setup and are presented with an error message instructing them to report the problem to the Web site hosting the web installation.

5. Enhancement:  InstallFromTheWeb automatically retries connection in case of no response from the Server.
   Error 12029 indicates that the server that is being contacted is not responding.   Since this can be the result of temporary busy network conditions, the InstallFromTheWeb Client now retries connecting to the server up to three times.   This allows a Web installation to proceed uninterrupted if a connection is successfully re-established within the three tries.

6. Enhancement: InstallFromTheWeb further reduces download time by downloading cabinet files only if they are needed on the end user's system.
   InstallFromTheWeb groups certain files from your original installation into smaller, compressed cabinet files. The files created, which depend on the tool that you've used to create your original setup, are called IsxvxrX.cab (engine cabinet), ProjectTitleSetupDll.cab, and ProjectTitleSys1.cab (for further information on the specific contents of each cabinet file, please see the "Build panel" or "Web installation files" topics in the InstallFromTheWeb online help). If the target system already has the same named files (along with the same version number) as the files within a particular cabinet file to be downloaded, the cabinet is not downloaded to the end user's system.

   This method of file and version checking allows InstallFromTheWeb to reduce download time by not downloading unnecessary files.

7. Enhancement: Improved feedback on run-time dialogs.
   The download meter provides users feedback on the number of bytes that have been downloaded, showing total bytes that need to be retrieved prior to setup launch and counting up to match this number. Previously, the download meter switched from reporting bytes to time remaining, which was confusing to end-users.

8. Enhancement: You can connect directly to Verisign from within the InstallFromTheWeb Design-time Wizard.
   InstallFromTheWeb lets you digitally sign your Web installation so that users can be assured of its authenticity. If you do not have the proper credentials needed to sign your installation, you can now connect directly to Verisign to obtain them by clicking a link on the Digitally Sign Installation panel.

9. Enhancement: New "SCRIPT" parameter allows you to customize your setup based on user input collected on the Web.
   The new SCRIPT parameter allows you to pass information from your server to your setup script. For example, you may wish to pass a user profile to your setup so that setup will download only needed components. You can use this feature to pass dynamically generated information on your Web site to your setup.

10. Enhancement:  Users have option to save files if they cancel installation before setup launches
    Previously, InstallFromTheWeb always cleaned up files if users decided to cancel a Web installation.  Now, users who cancel a Web installation have the option to save the files already downloaded so that the files do not have to be downloaded again when users continue installing at a later time.

11. Change:  Internet Progress Bar does not loose focus when you click on the Setup background window
    Once setup is launched from the Web, two progress bars are displayed  - the InstallShield regular file copy progress bar and the Internet Progress bar right above.   Previously, if you clicked anywhere on the screen during the setup, the Internet progress bar would loose focus.   Now, the Internet progress bar remains in place and does not loose focus.

12. Change:  Cryptographic Digest Algorithm choice now limited to MD5.
    InstallFromTheWeb no longer supports the SH1 encryption method.

13. Fix: Server error 404 occurs when you save installation files from a previously installed project.
    Previously, error 404 appeared when all the following conditions existed:
    • Your InstallFromTheWeb project name was the same as a previously distributed project
    • You included different or additional files in your source folder or you used a different source folder
      (specified in the Source Files Folder panel).
    • The same Web installation has been saved previously on the target system and an attempt was
      made to save the installation again by selecting the options to save installation files or to install
      and save installation files during run time.
14. Fix:  _Setup.DLL retrieved from cache does not match the one needed for installation
    InstallFromTheWeb reads the Runtime Reference (WIS) file and checks for any components already cached on the system that do not have to be downloaded.   _Setup.DLL is one of the files that may be cached on users systems in the Program Files\Common Files\InstallShield\Cache directory.

    Previously, under certain conditions, InstallFromTheWeb retrieved a 32-bit version of _Setup.DLL from cache when the installation called for a 16-bit version. This caused a verification error to occur.  Deleting the cached files, or clicking 'Ignore' allowed the installation to proceed.  In this release the wrong _Setup.DLL is no longer retrieved.

15. Fix: Client does not recognize Netscape 4.x proxy settings.
    Because previous versions of the Client read settings only from the Netscape 3.0 location on end users' systems, errors 404, 12007 and 12029, as well as security errors could appear during Web installations for Netscape 4.x users connecting to the Internet via proxy servers. This known limitation has been fixed in this version of InstallFromTheWeb.  

    Now, the Client reads proxy settings from Netscape users' preferences file.

16. Change: InstallFromTheWeb reads InstallShield project file to compile list of projects that can be imported in the Design-time Wizard.
    Previously, if in the Start a Project panel, you selected the option to import and InstallShield5 or InstallShield Express project that you would like to Web enable, InstallFromTheWeb compiled a list of importable projects by reading the available projects from the "Media" folder on your system. This did not provide an accurate listing of projects, as some users may have specified that media be built to a custom location.

    In this version, InstallFromTheWeb determines the location of media available for importing from the InstallShield Professional or Express project file (.Ipr).

17. Change: Command buttons added to the Host Sites panel.
    To make adding and removing new host sites and group names for host sites easier and intuitive, the command buttons New Group, New Site, Edit, and Delete now appear in the Host Sites panel. Previously, you had to right-click to enter site information. Although the option to right-click to add sites is still available to you, the addition of the command buttons gives a clearer indication of how to add and remove host sites.

18. Change: Client installation fails if the host site and the run-time reference file reside in different locations when you are hosting your installation on only one server.
    Some InstallFromTheWeb users prefer to place the run-time reference file in a different location than their Webinstallation files This can be done by directly modifying thevalue and embed tags in the object tag of the installation Web page generated by InstallFromTheWeb. The value and embed tags must refer to the correct location of the run-time reference file, and the run-time reference file must include the correct address of your Web installation files.

    However, InstallFromTheWeb unable to locate installation files if the run-time reference file was hosted in a different location than the Web installation, and the files were hosted on only one site (InstallFromTheWeb allows you to host your installation files on multiple servers).

    In this version, you may host the run-time reference file in any location, regardless of the number of host sites you have indicated.

19. Fix: Progress bar does not provide accurate information.
    Previously, previous to setup launch, the InstallFromTheWeb progress bar would stay at 80 percent, then jump to 100 percent to indicate how much of a Web installation had been completed. In this release, the progress bar accurately reports the status of the installation's completion.

20. Known limitation: PLUGINSPAGE tag not updated if you enter new value in the Wizard.
    In the Web Page Generation panel, you may enter a value in the URL to Client Homepage field. This value is entered in a PLUGINSPAGE tag within the object tag of your installation Web page. If users do not have the Client, they may be directed to the URL you specify to retrieve and install and the Client. They may also be directed to this site if they have an old version of the Client. The default location for the Client homepage is www.installshield.com/client.

    If you change this default value in the Wizard in this version, InstallFromTheWeb does not recognize the entry and does not place the URL that you specify in the PLUGINSPAGE tag of your installation Web page. Instead, it takes the default value.

    You may manually edit the PLUGINSPAGE value after you have generated your installation Web page. Simply open your Web page in a text editor, locate the PLUGINSPAGE tag, and enter the appropriate address.

1. Fix: Browsing to another Web site or reloading the installation Web page before InstallFromTheWeb exits causes a Netscape invalid page fault error.
   The Netscape invalid page fault error appeared when users tried to reload the current page or access other pages before the InstallFromTheWeb run-time engine (Iftw.exe) had exited.

   The plug-in distributed with the InstallFromTheWeb Client is designed to exit only after setup ends or after a user cancel the setup process. When users browse to another page or reload a page before setup is completed, the plug-in is recreated, creating a new, different instance of the plug-in.

   When setup informs the plug-in that its process is completed, the stack is to be restored to the state it was in when the plug-in was launched. However, since the plug-in has been recreated, the stack is invalid, resulting in the invalid page fault error.

   In this release, a different process is used to notify the plug-in that setup has ended, avoiding the possibility of the invalid page fault message occurring.

2. Fix: Install button does not reset itself immediately after setup is completed.
   When you click the InstallFromTheWeb blue install button to begin installation, it changes state. Instead of the words "InstallFromTheWeb" appearing on the button, the words "install in progress" appear on the button until the setup process has ended. Once setup is completed, the button is reset to display "InstallFromTheWeb".

   In the previous release, resetting of the button was significantly delayed. The new 2.32 Client allows the button to reset itself immediately after setup is complete to provide users with a clear indication of when the installation process is over.

3. Fix: Modifying host sites at run time does not work properly if you call the Iftw.ocx sites property in the installation Web page.
   Due to an interface omission in the InstallFromTheWeb 2.3.1 Client, users who visit installation Web pages that call the Iftw.ocx SITES property to present a list of installation host sites will receive an interface error. (Users who modify sites at run time by listing a sites file after the PARAM NAME and SITES parameters are unaffected.)

   The SITES interface has been restored in the 2.32 Client so that the SITES property can be used to modify host sites at run time.

1. Fix: Systems with over 2 GB free space receive a message that the system is out of disk space
   InstallFromTheWeb used a Win32 API call, GetDiskFreeSpace( ), as part of determining whether or not there is enough disk space on the end userÕs system to conduct installation. Previously, this function could only measure up to 2 GB free space and was unable to return a valid value if the end userÕs system had more than 2 GB available. This in turn caused InstallFromTheWeb to erroneously report that the system was out of disk space.

   InstallFromTheWeb now uses the function call GetFreeDiskSpaceEx( ) which measures free space greater than 2 GB and returns an accurate value, eliminating this known limitation. This call is used on Windows NT 4.0 and Windows 95 OSR2 or later systems. The old function call, GetDiskFreeSpace( ) is still used for older versions of the Windows operating system.

2. Change: Netscape Plug-in includes version number in properties value
   The version number of the plug-in has been added so that it is now visible if you right-click it and view its properties.
3. Enhancement: Check performed on end userÕs system to determine if newer Client is needed
   If a Web installation requires a newer Client, a message is now displayed that asks the user to download the most recent Client. Please note that this version checking will not affect users who have Clients previous to 2.3.1
4. Enhancement: "URL to Client Homepage" field added to Web Page Generation panel
   The address entered in the newly added URL to Client Homepage field is shown to end users if they need to update to the most recent Client (see release note 3).
5. Change: Netscape Client distributes an additional file
   The Client for Netscape users now includes a file called URLMON. URLMON is a companion file to Microsoft's Wininet.dll, the Internet communications device for InstallFromTheWeb. The URLMON file's main responsibility is to interpret proprietary Internet addressing schemes. Internet Explorer users already have this file on their system; therefore, it is not distributed with the Client for Internet Explorer users.
6. Fix: Read only files deleted from the TEMP folder
   Previously, InstallFromTheWeb was unable to delete read-only files from the TEMP folder (the location where files are placed before they are transferred to the destination directory on the end user's system). Because the temporary files were not deleted, InstallFromTheWeb could not exit. This in turn caused the end userÕs system to beep.

   In this release, InstallFromTheWeb checks the attributes of the files in the TEMP folder. If a file is marked as read-only, the attribute is changed and then deleted.

   Deleting read-only files from the TEMP folder addresses cases where an installation would stop responding after the initial set of run-time dialogs was viewed. This typically occurred when InstallFromTheWeb developers would run the same setup on the same system more than once. If files remained in the TEMP folder that were read-only (for example, a license.txt file) and InstallFromTheWeb attempted to download the same files, the installation would not continue because the files could not be overwritten. In this release, deleting files from the TEMP folder eliminates this known limitation.

7. Fix: InstallFromTheWeb no longer deletes files in TEMP folder when a connection is broken
   If an installation terminates abnormally (for example, a broken connection occurs), installation files already downloaded to the end user's system remain in the TEMP folder. Upon retrying the installation, InstallFromTheWeb checks to see what files are in the TEMP folder. It does not download files that already reside in this location, reducing download time when users re-attempt installation.

   On systems that were connected to the Internet through a network card, InstallFromTheWeb deleted files that were in the TEMP folder, causing users to start the download from the beginning. This behavior occurred when using InstallFromTheWeb 2.2 and may be seen in InstallFromTheWeb 2.1.

   This behavior has been modified in the current version of InstallFromTheWeb so that those who are installing through a network connection can still enjoy the benefits of error recovery.

1. Enhancement: Secure HTTP supported.
   Previously, the error message "Connection scheme not supported" was displayed if users tried to access a Web installation through a secure connection.

   In this release, InstallFromTheWeb properly interprets the HTTPS connection scheme (https), and in turn downloads installation files through port 443 – the port for secure connections.

   Please note that you must have a secure server ID in order to enable a secure connection on your server.

   For further information, please see http://www.verisign.com.

2. Enhancement: InstallFromTheWeb Netscape Client supports the ability to modify host sites at run time.
   Instead of rebuilding a Web installation each time a host site changes, you may place a text file listing available host sites on your server and create a reference to it in your installation Web page. The information in the text file overrides any host site information entered in your InstallFromTheWeb project. In InstallFromTheWeb releases 2.0 and 2.1, this feature was only supported by the Internet Explorer Client. Now the Netscape Client also supports this feature.

   For information on how to modify host sites at run time, see the InstallFromTheWeb 2.2 help topic "Modifying host sites at run time" in the Tips and Tricks book.

3. Enhancement: Greater control over installation options during run time.
   Previously you were able to choose whether or not installation files could be saved on the end user’s system. This produced the Installation Modes run-time dialog which offered end users the options to install the application, to install the application and save the installation files, or to save the installation files and install the product at a later time.

   In this release, you may choose each one of the above options separately in the Installation Options Design-time Wizard panel. This allows you to customize the options your end users have for saving the original installation files. For example, if you would like to ensure that end users will always save the original installation files so that your application can be installed on other systems, select the Install and Save option. If you want to prohibit end users from saving original installation files, select Install Only. A full discussion of these options appears in the help file in the topics "Installation Options" and "Customizing installation options – saving installation files".

   When you open an InstallFromTheWeb 2.0 or 2.1 project that did not have the option selected that allows end users to save installation files on their system, the Install Only option is selected in the 2.2 Wizard.

4. Change: New cabinet files created in Web installation build process if you are Web-enabling an InstallShield5.x or Express installation.
   The SetupDLL cabinet file is created to reduce download time if you are distributing an internationalized InstallShield5.x or Express installation. The InstallShield _Setup.dll file contains initialization resources such as localized bitmaps and string tables for messages that may be displayed during installation. This cabinet file is downloaded only if the _Setup.dll needed for installation is not cached on the end user’s system in the Program Files\Common Files\InstallShield folder.

   If you are Web-enabling an InstallShield5 installation, the SYS1 cabinet file is created and includes the _Sys1.cab file. _Sys1.cab contains uninstallation executable files for both 16 and 32-bit systems, Corecomp.ini, an initialization file that InstallShield uses to determine how to handle installing and uninstalling core component files, and _isres.dll which contains InstallShield resources for dialog boxes and user interface objects.

5. Fix: InstallFromTheWeb properly handles requests for user name and password.
   Previously, when the InstallFromTheWeb run-time engine established a connection with a server hosting Web installation files, it tried to log on as "anonymous". If the server required a user name and password to log on, the engine displayed an authentication dialog box. However, the engine did not properly pass the user name and password to the server, causing the authentication dialog to repeatedly appear.

   In this release, if a user name and password is required to log on to a server, the run-time engine displays the authentication dialog and then properly supplies the server with the information the end user enters.

6. Fix: Code Signing works correctly on all systems with both IE 4.0 and Internet Client SDK for IE 4.0 installed.
   InstallFromTheWeb uses a version of the Microsoft Authenticode™ code signing tools based upon the browser environment of the system it is installed upon. Previously, code signing would fail on some systems because of conflicts between Authenticode™ code signing tools that are distributed with the Internet Client SDK for IE 4.0, and those that came with InstallFromTheWeb 2.0 and 2.1.
7. Fix: Netscape GPF no longer occurs if path to the run-time reference file is invalid.
   In previous versions of InstallFromTheWeb, if the path to the run-time reference file was invalid, Netscape would produce a general protection fault error once you clicked the install button. In this release, instead of receiving a GPF notification, InstallFromTheWeb warns you that the path to the run-time reference file may be incorrect.
8. Fix: Hyphens in host site domain names no longer replaced with %2D, eliminating Netscape "illegal operation" message.
   Previously, in order to interpret hyphens in domain names, InstallFromTheWeb replaced the hyphen with "%2D". This caused the InstallFromTheWeb Netscape plug-in included in the Client to fail after the install button was clicked since "%2D" rendered the domain name invalid. After the Client failed, Netscape reported that the application had performed an illegal operation and would be shut down.

   In this release, dashes in domain names are properly recognized and are not replaced with %2d, eliminating the Netscape error message.

9. Fix: Error message is no longer displayed if users decide not to accept the InstallFromTheWeb Client.
   Previously if users decided not to accept the InstallFromTheWeb Client by clicking the No button on the Client’s digital certificate, the following message was displayed:

   The run-time reference file is corrupt or has an invalid signature. Contact the software vendor at the installation site". In this release, if the user clicks No, the certificate is dismissed without presenting a warning or message.

10. Fix: InstallFromTheWeb properly recognizes destination location path when saving and installing files on Windows NT 4.0.
    Previously, if end users entered a path in which to save files that was similar to a path that already existed on their system, the message "Unable to execute \SMS\Zi<path to the file> was displayed. This was a result of InstallFromTheWeb not placing quotes around the path already entered by the user, causing the Windows API CreateProcess to fail. In this release, quotes are appended to the path.

    Be sure to rebuild any existing Web installations with Version 2.2 of the InstallFromTheWeb Design-time Wizard to eliminate this message.

    Although InstallFromTheWeb addresses this issue, the Setup.exe \SMS\Zi error message may appear in other situations. Please see knowledge base article Q101722, "’Cannot Launch Setup.exe \SMS\Zi’ Message Appears in ‘Save and Install’ Mode on Windows NT."

11. Fix: Project file updated in autobuild mode.
    Previously if you rebuilt a project from the command line (also known as "autobuild") and selected the Live Folder option, new files in the source files folder were not added to the project. In this release, all new files are added to a project.
12. Fix: Autobuild no longer adds duplicate files to the Web installation.
    Previously, files from the original Web installation were added to the project each time you rebuilt a project from the command line. For example, if you built a project with the file "Setup.exe", then rebuilt from the command line, the data cabinet file included two "Setup.exe" files. This produced large files that in turn, increased download times.

    In this release, duplicate files are not added to the Web installation.

13. Fix: When rebuilding an installation from the command line, cabinet files are preserved.
    Previously, when building a Web installation from the command line, InstallFromTheWeb placed all cabinet files into the same cabinet.

    Building from the command line now properly preserves all cabinet files.

14. Fix: Duplicate files no longer added to the data cabinet file.
    If with InstallFromTheWeb 2.0 and 2.1, you select the Live Folder option in the Source Files Folder panel and the Do not copy files directly option in the Host Site Configuration panel, InstallFromTheWeb-generated files such as the installation Web page (htm), wis file, run-time reference file, and data and engine cabinet files were placed in your source files directory. Previously, InstallFromTheWeb placed these files in a Web installation each time it was rebuilt, causing the size of the installation to grow unnecessarily larger and increasing download times for end users.

    In this release, the Wizard recognizes duplicate files and only adds the newest InstallFromTheWeb generated files to the Web installation.

15. Fix: Localized InstallShield5.x installations are created properly.
    InstallShield5.x international installations include subfolders that contain localized files needed for installation. In previous releases, InstallFromTheWeb did not include the subfolder path to these files. Because of this, during Web installation, users would receive messages that files could not be found for installation.

    In this release, InstallFromTheWeb properly preserves the subfolder paths in internationalized installations.

16. Fix: Client can now download the run-time reference file when it its location is specified with the file:// connection scheme followed by a UNC path.
    Previously, if you used the file connection scheme along with a UNC path as your host site, end users would receive a message that the run-time reference file could not be found. This occurred on Windows NT 4.0 systems with Internet Explorer 4.0.

    For example, if you entered file://\\myserver\wwwroot\webinstallation as the URL of your host site, the run-time reference file error occurred during Web installation. This error occurred because of a change in how the Internet communications device included with Internet Explorer 4.0 (Wininet.dll) interpreted backslashes in file paths.

    In this release, the InstallFromTheWeb run-time engine works in conjunction with Wininet.dll to properly interpret backslashes in path names.

17. Fix: Engine cabinet is now downloaded after a site is specified.
    Previously, the engine cabinet file was always downloaded from the same location as the run-time reference file, even if you had listed multiple host sites and chose to conduct installation from a location different from that of the run-time reference file.

    Currently, the run-time reference file is downloaded only after end users select a site location listed in the Installation Sites run-time dialog.

18. Fix: URL in Digital Signature panel persists when a previous project is opened.
    Previously, in the Digitally Sign Installation panel, the URL you entered for your site did not persist when you opened the project again. For example, if you entered http://www.mydomain.com in the original project, when you reopened it, the first URL listed as your host site appeared in the Enter your URL field.

    In this version, the InstallFromTheWeb Design-time Wizard displays the last URL you entered as the URL for your site.

19. Fix: Executable files residing in a subfolder are launched properly.
    Previously, if the executable file you choose to run on end user’s system once installation files were transferred resided in a subfolder in your original installation, end users received a message that the executable file could not be found. This was a result of the InstallFromTheWeb Design-time Wizard not including the subfolder in the command line to the executable file.

    In this release, the Design-time Wizard includes the subfolder in the command line to the executable file and displays the subfolder in the Installation Types panel window that lists all of the executable files included in the original installation.

    This issue did not affect all users with executable files in subfolders in the original installation. For example, if you selected the executable file in the Installation Types list, clicked Edit to view the Configuration dialog box, approved or changed the setting in this dialog and then clicked OK, the Wizard properly stored the command line.

Internet Explorer users with previous versions of the Client are notified that a new version is available when they visit a page that references an updated Client.

The Client installation process for Netscape users has not changed.

Please see http://www.installshield.com/client/ for instructions on updating the InstallFromTheWeb Clients.

Enhancement: MIME type automatically generated in installation Web page.
The InstallFromTheWeb MIME type, TYPE=application/x-InstallFromTheWeb, is now placed in the installation Web page the Wizard automatically generates. Although this does not eliminate the need to configure your Web server to recognize the InstallFromTheWeb file type and MIME type to accommodate Netscape users, it does help some browsers more easily recognize the plug-in included with the Netscape Client installation.

Change: InstallFromTheWeb does not verify Authenticode digital signature when installing through Netscape, eliminating the message "System Error: One of the libraries required to run this application cannot be found".
Previously, if InstallFromTheWeb could not find Wintrust.dll-the component used in Microsoft Authenticode to verify digital signatures-the system error listed above was displayed. Since Wintrust.dll is installed with Internet Explorer, Windows 95 B and Windows NT 4.0, users with Windows 95 A systems would receive this message if they installed Web-enabled installations through Netscape.

Now if Wintrust.dll does not exist on a user's system, rather than quitting, InstallFromTheWeb continues with the Web installation. If Wintrust.dll cannot be found, InstallFromTheWeb does not attempt to verify a digital signature for an installation since Netscape does not support Authenticode technology.

Change: Temporary directory cleaned up after installing non-InstallShield installations from the Web.
Previously, if you installed a non-InstallShield installation from the Web, files were left in the Windows\temp\ folder. In release 2.1, all files (except for locked or read-only files) are deleted from the temp directory after the setup executable file for the installation quits.

Change: Addressed known issue of _Setup32.lib not being added to Web installations.
In order to create more manageable disk sizes for download via the Internet, InstallFromTheWeb is integrated with InstallShield to place data files on separate disk images.

If _Setup32.lib is included in an original installation, this method of placing files on disk images caused InstallFromTheWeb to list _Setup32.lib as residing on disk 31 in the run-time reference file. Since this is a file needed to initialize setup and should be included on disk 0, this caused errors during run time.

InstallFromTheWeb has been modified to recognize _Setup32.lib and places the file on disk 0.

Change: You are now able to enter the root of any drive as a source file folder.
Previously, if you selected the root of a drive as your source folder in the Source Files Folder Wizard panel, no files appeared in the Installation Files panel list view. In this release, you may select the root of a drive for a source files folder and the Wizard properly recognizes all files within that folder.

Change: InstallFromTheWeb properly selects Setup.exe by default as the executable file to start once files are transferred.
Previously, if you selected a parent folder of disk1 as the source folder for your Web installation, Isdel.exe was chosen as the default executable to run once the installation is transferred to the end user's system instead of Setup.exe. In this version, InstallFromTheWeb properly selects Setup.exe as the executable to run for your Web installation if an InstallShield engine reside in disk1 of your source files folder.

Change: Addressed known issue of install button not being activated in Internet Explorer 4.0 after the Client is installed.
On some systems using Internet Explorer 4.0, the blue install button would appear after installing the InstallFromTheWeb Client, however, the button was inactive. This behavior occurred on systems in which the Occache folder did not exist under the Windows folder. This is the location in which InstallFromTheWeb installs the ActiveX control included in the Client for Internet Explorer users.

Currently, Internet Explorer 4.0 places ActiveX controls in the folder Windows\Downloaded Program Files. To ensure that the Client is properly installed and in the correct location, InstallFromTheWeb checks the end user's registry for the Downloaded Program Files folder. If this does not exist, InstallFromTheWeb checks the end user's system for the Windows\Occache folder and installs the Client . If neither folder exists, InstallFromTheWeb tries to create the Windows\Occache folder. If it cannot, then an error message is displayed.

Change: Wizard no longer loops on Windows 95A systems.
On some systems, clicking Next in the Source Files Folder Design-time Wizard panel returned users to the Welcome panel. This behavior occurred on Windows 95A systems that did not have the correct version of COMCTL.DLL. The correct version of the file, COMCTL32.DLL, is installed with InstallFromTheWeb 2.1 to eliminate this behavior.

Change: InstallFromTheWeb properly timestamps run-time reference file.
Previously the InstallFromTheWeb Wizard did not properly timestamp digitally signed installations. This resulted in the digital signature listing that the installation was signed at an "unknown date and time" if viewed through Internet Explorer 4.0. In this release, the Wizard records the correct date and time that the installation was signed.

To work around this problem, make a note on your installation Web page for end users to close their Web browser immediately after clicking the install button. You may also encourage Netscape users to upgrade to Communicator 4.0 since this issue has been addressed in that release.

Known Issue: Internet Explorer 4.0 users who have security set to High will not be able to view the InstallFromTheWeb install button.
If Internet Explorer 4.0 users have their security settings on High, they are not prompted to install the InstallFromTheWeb Client since this is considered "active content". Instead, end users will see a white box with an X inside of it.

You may advise end users to select the "Medium" security settings. From the View menu, select options, click the Security tab and select "Medium".

Known issue: Web installations unable to be completed on systems that have CompuServe® 3.0 installed.
Due to a possible conflict with a file (RpaWInet.dll) that is installed with CompuServe 3.0, Web installations cannot be successfully executed on systems with CompuServe 3.0 installed. The conflict causes the setup executable file for a Web installation to be launched, but unable to unpack all of the installation files onto the end user's system. A symptom of this known limitation includes installation progress stopping after any run-time panels you have specified for the installation have appeared. End users may uninstall RPADLL in the Add/Remove Program applet in the Control Panel (if they no longer need this file) to eliminate this problem.

Known issue: Restoring original installation's directory structure causes errors.
If you select the option in the Source Files Folder Design-time Wizard panel to restore the installation's directory structure, the following errors may appear:

If you have Web-enabled an InstallShield3 installation, end users are prompted to enter the next disk during Web installation, even though all installation files have been delivered to the target system.

If you have Web-enabled an InstallShield5 installation, end users may receive a message similar to the following: "An error occurred during the move data process -112".

Both of these errors are caused by the InstallShield engine's incorrect manipulation of the SRCDIR system variable when you pass the /Zi command line option to Setup.exe and you have Web-enabled a multi-disk InstallShield installation in which the disk images are in separate sub-folders. In this case, once installation files are downloaded to an end user's system, the InstallShield engine is unable to locate the files to use during installation.

Solution:

InstallShield3 and InstallShield Express users:
Modify your original installation so that there are no duplicate filenames or sub-folders. Leave the option to restore installation directory structure blank in InstallFromTheWeb's Source Files Folder Design-time Wizard panel. This will cause all files to be placed in the same directory, eliminating the Enter Disk dialog prompt that may appear with a multi-disk installation in which the directory structure is preserved.
InstallShield5 users:
Rebuild your original installation and select the InstallFromTheWeb media build type in the Media Build Wizard. In addition to creating a disk size optimized for Internet software distribution, it places all files within the same directory.

This known limitation will be addressed in InstallShield5.1.

If you experience this known limitation, select Cancel, save the information in your project, and shut down InstallFromTheWeb. Then open the appropriate InstallFromTheWeb project, enter the correct user name and/or password in the Host Site Configuration dialog and rebuild the installation.

Known issue: If you host your Web installation on multiple sites, you must manually edit the generated .htm page in each server location to link to the appropriate host site.
If you host your Web installation on multiple installation sites, you must manually edit the installation Web page InstallFromTheWeb generates for you to point to the appropriate host site.

Otherwise, the page only links to the first address you have entered in the Host Site Configuration panel as the "URL to this site".

For example, you may host your installation on a site in California, Illinois and New York. If you entered the California site first in the Host Site Configuration panel, the installation Web page residing on the Illinois and New York servers will link to the California installation unless you manually edit the .htm pages residing on the Illinois and New York servers to point to their respective installation sites.