How to Distribute Your Browser

By default, the Internet Explorer Customization wizard creates files for downloading via the Internet or an intranet server. You can also create a custom browser package on CD-ROM or on multiple floppy disks.

Downloadable files

If you created the browser package on an Internet or intranet server, you need to set up your Web site so that users can download the files. For example, you might create a page where you post download information and a link to the install engine, IE5setup.exe.

If you created the browser package on your hard disk or network drive, you need to move the following items to an Internet or intranet server:

The folder that contains the language version you are posting and the folder contents. For example, the folder for the English version is named En, so you need to move the En folder and the files it contains. This folder will be in folders for your media type, such as Download, and platform, such as Win32.
The file named Ie5sites.dat. This file points to the download site (or sites) you specified when you ran the wizard.

For an illustration, see How to Set Up Files for Distribution.

Signing your custom packages

Web browsers have security features that help protect users from downloading harmful programs. Depending on the security level and the platform, the user may be prevented from or warned against downloading programs that aren't digitally signed.

The custom .cab files created by the Customization wizard for 32-bit versions of the browser should be signed, unless you preconfigure the Local intranet zone with a Low security setting. Any custom components you distribute with your browser package for these platforms should also be signed. If you have a digital certificate, the Customization wizard can sign these files automatically.

Unlike Internet Explorer 32-bit versions of the browser, 16-bit and UNIX versions of the browser do not perform digital signature verification. Programs or cabinet files for these operating systems do not need to be signed.

Notes

Signing the cabinet files and custom programs requires two steps: obtaining a digital certificate and specifying the certificate information when you run the Customization wizard. For more information, see Signing Your Programs.
You may need to change the case of file names on a UNIX FTP server. Below are the conventions you should use for specific UNIX operating systems.
- Solaris UNIX
  If you are using a case-sensitive UNIX FTP server, you must make sure your cab folder is not capitalized, but the following file names are capitalized: BRANDING.CAB, CUSTOM.CIF, DESKTOP.CAB, IE.CIF, IECIF.CAB, and IE5SITES.DAT.
- AT&T UNIX
  All file names must be capitalized on an AT&T UNIX FTP server.
- IRIX UNIX (Silicon Graphics)
  The following file names must be capitalized: BRANDING.CAB, CUSTOM.CIF, DESKTOP.CAB, IE.CIF, IECIF.CAB, and IE5SITES.DAT. You should also use a text editor to modify the file names listed in IE.CIF to match the case of the files.

CD-ROM

If you distribute your custom browser for Windows 95 and Windows 98 users, a splash screen Autorun program appears when the user inserts the compact disc. This program offers users the choice of installing your custom browser or viewing more information. If the current version of Internet Explorer is already installed, the Autorun program detects it. The browser appears in what is known as Kiosk mode with the Start.htm file loaded.

Multiple floppy disks

You can also distribute your custom browser on multiple floppy 1.44 MB disks. In the destination directory you have specified, you will find a folder named \Mfloppy that contains subfolders named Disk1, Disk2, and so on. Copy the contents of these folders to your floppy disks.