The Wayback Machine - https://web.archive.org/web/20121105132035/http://technet.microsoft.com/en-us/library/dd361925.aspx
Internet Explorer
United States - English
Home
Internet Explorer 10
Internet Explorer 9
Internet Explorer 8
Previous Versions
Library
Forums
This topic has not yet been rated - Rate this topic

Chapter 4 - Working with Different Platforms

This chapter identifies the platforms on which you can install Microsoft Internet Explorer 5 and describes the deployment variations among the supported platforms. This information is particularly important if you are deploying Internet Explorer on multiple platforms.

See Also 

  • For more information about planning your browser deployment for different platforms, see Chapter 9, "Planning the Deployment." 

  • For more information about building custom packages of Internet Explorer for different platforms, see Chapter 15, "Running the Internet Explorer Customization Wizard." 

  • For more information about installing Internet Explorer on different platforms, see Chapter 19, "Deploying Microsoft Internet Explorer 5." 

Overview

Dd361925.spacer(en-us,TechNet.10).gif Dd361925.spacer(en-us,TechNet.10).gif

You can install Internet Explorer 5 on the following platforms:

  • UNIX, including Sun Solaris 2.5.1, Sun Solaris 2.6, and Hewlett Packard HP-UX 

If your organization uses several different platforms, you will need to deploy and maintain a separate version of Internet Explorer 5 for each platform. Internet Explorer 5 provides a single, standards-based set of technologies for Web authoring, browsing, communication, and collaboration for all supported platforms. The HTML rendering engine for Internet Explorer on Windows and UNIX platforms was derived from the same code base, so developers are assured that content developed for one platform will render the same on all platforms.

Note Although Macintosh is not included in this platform discussion, Internet Explorer for the Macintosh is also developed from the same standards-based set of technologies. If you have deployed Internet Explorer on the Macintosh platform or developed Web content for the Macintosh, you can expect the same benefits of this common browser across all platforms.

If you plan to install Internet Explorer on different platforms, you should consider the following issues:

  • Planning the deployment—To successfully deploy Internet Explorer, you need to determine the platform and browser requirements for all groups targeted to migrate to Internet Explorer. For more information about planning your deployment on different platforms, see Chapter 9, "Planning the Deployment." 

  • Conducting a pilot program—Before you deploy Internet Explorer to your users, you should conduct a pilot program to test your browser packages for each platform. For more information about conducting a pilot program, see Chapter 11, "Setting Up and Administering a Pilot Program." 

  • Building custom packages—You can use the Internet Explorer Customization wizard, which is part of the Internet Explorer Administration Kit (IEAK) 5, to build custom packages of Internet Explorer for the Windows and UNIX platforms. For more information about the Internet Explorer Customization wizard, see Chapter 15, "Running the Internet Explorer Customization Wizard." 

  • Maintaining browser versions—You can use the IEAK Profile Manager to administer Internet Explorer for the Windows and UNIX platforms. The IEAK Profile Manager enables you to update browser settings and manage different versions of the browser from a single location. For more information about using the IEAK Profile Manager, see Chapter 22, "Keeping Programs Updated." 

Windows Platform: 32-bit Versions

Dd361925.spacer(en-us,TechNet.10).gif Dd361925.spacer(en-us,TechNet.10).gif

The 32-bit versions of Windows integrate Internet technology and browser features directly into the operating system. This browser-platform integration means that users who run Windows 32-bit versions can take advantage of advanced browsing capabilities. Users can browse their hard disk, local area network, or the Internet to quickly find the information they need. Using Internet Explorer, they can quickly navigate the Web using the Search, History, and Favorites bars, or get information delivered directly to their computers for offline viewing. For more information about this browser-platform integration, see the Microsoft Windows Web site at http://www.microsoft.com/windows/ .

Some Internet Explorer customization features, deployment methods, and maintenance practices are specific to Windows 32-bit versions. You should consider the following issues when you deploy Internet Explorer on Windows 32-bit versions:

  • CD-ROM installation—If you distribute your custom-browser package to users who run Windows 32-bit versions on a CD-ROM, a splash-screen Autorun program appears when users insert the 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 (if this feature is enabled using the Internet Explorer Customization wizard), with the Start.htm file or your own custom start page loaded. 

  • Administrative privileges—For Windows NT, you must have privileges as an administrator to install and uninstall Internet Explorer. Users must, therefore, have administrative privileges the first time they start their computers after installing or uninstalling Internet Explorer. 

  • Setup download folder—You can find the IE5Setup.exe file in the media type folder created for your language and platform version. For example, the English version of Internet Explorer for Windows 32-bit versions would reside in the \Download\Win32\En folder of your build directory. 

  • Code signing—If you are distributing Internet Explorer 5 over the Internet or intranet, you should sign custom cabinet (.cab) files created by the Internet Explorer Customization wizard for Windows 32-bit versions. This is recommended unless you preconfigure the Local intranet zone with the Low security setting. You should also sign any custom components that you distribute with your browser package for this platform. Code signing lets users know that they can trust your code before downloading it to their computers. The default settings in Internet Explorer will reject unsigned code. If you have a digital certificate, the Internet Explorer Customization wizard can sign these files automatically. 

  • Single-disk branding—When you build custom packages using the Internet Explorer Customization wizard, you can choose the single-disk branding option for your media type. This option customizes an existing installation of Internet Explorer 4.01 Service Pack 1 (which is part of Windows 98) or higher. It does not install Internet Explorer 5. 

Windows Platform: 16-bit Versions

Dd361925.spacer(en-us,TechNet.10).gif Dd361925.spacer(en-us,TechNet.10).gif

Internet Explorer delivers a full set of browser features and functions for Windows 16-bit versions. The 16-bit versions of Internet Explorer were designed for computers with less than 12 MB of RAM and requires as little as 6.5 MB of hard-disk space to install, providing complete, standards-based Web-browsing and authoring capabilities even on lower-performance computers. Users can easily browse the Internet or intranet, use Internet standards-based e-mail and discussion groups, and benefit from the same secure browsing environment that is available to Windows 32-bit and UNIX users.

The Windows 16-bit browser also includes special features, such as the Preview button, which was designed to optimize the user's browsing experience on Windows 16-bit versions. The Preview button enables you to browse the Web faster by turning off images and formatting until you get to the page you want to see.

Some customization features, deployment methods, and maintenance practices for Windows 16-bit versions differ from Windows 32-bit versions. You should consider the following issues when you deploy Internet Explorer with Windows 16-bit versions:

  • Digital signatures—Unlike Windows 32-bit versions with Authenticode technology, Windows 16-bit versions do not perform digital-signature verification. Windows 16-bit browsers do not support certificates, so automatic-configuration files are not signed. You do not need to sign your programs or cabinet files for this platform. You should, therefore, ensure that your automatic-configuration Web site has restricted access so that no one can tamper with your files. 

  • Certification authorities—For Windows 16-bit versions, you can import and install certificates for up to 20 certification authorities. If you have certificates for more than 20 certification authorities on your computer, you will need to identify the 20 certificates that you plan to install, and then remove the certificates for remaining certification authorities before you build your custom package. 

  • File-naming format—If you build a custom package for Windows 32-bit versions and then rebuild a custom package for Windows 16-bit versions in the same folder, the file names will automatically be converted to eight-character names with three-character extensions (8.3 format). If you rebuild a custom package for Windows 32-bit versions in the same location, the files will continue to be converted to 8.3 format. After rebuilding a custom package for Windows 16-bit versions, it is recommended that you build a new custom package for Windows 32-bit versions in a different location.

  • Dial-up access—If your users need dial-up access, you must include the Stack and Dialer for Windows 3.1 as part of your setup package. If some users are running Windows NT 3.51 and some are running Windows 3.x, you should include at least two installation options: one with the dialer for Windows 3.1 and Windows for Workgroups 3.11, and one without it for Windows NT 3.51. For dial-up access, you must first configure Windows NT 3.51 computers for Remote Access Service (RAS).

  • Media selection—When you build custom packages by using the Internet Explorer Customization wizard, you can choose the multiple floppy disks option for your media type. You can distribute custom packages on multiple floppy disks for Windows 3.1 and Windows for Workgroups 3.11, but not for Windows NT 3.51.

  • Microsoft Outlook Express—With Windows 16-bit versions, you cannot use automatic configuration for Outlook Express.

  • Custom channels—When you customize channels for Windows 16-bit versions, you should verify that any channels you include are displayed correctly for this platform. The channels will display in the Explorer bar, which appears in the left part of the browser window when the user clicks the Channels button, but they will not appear in a separate channel bar on the desktop.

    Security options—All security options apply to the Internet Explorer browser, but they are not necessarily applicable system-wide—that is, other programs may or may not respect these options. When you set the security options for Internet Explorer, you should be aware that the following options do not apply to the Windows 16-bit platform:

    • User authentication 

    • Font download 

    • Software channel permissions 

    • Installation of desktop items 

    • ActiveX® scripting 

    • Launching applications and files from an IFRAME element 

  • Setup download folder—You can find the IE5Setup.exe file in the media type folder created for your language and platform version. For example, the English version of Internet Explorer for Windows 16-bit versions would reside in the \Download\Win16\En folder of your build directory. 

  • Setup graphic file—For Windows 16-bit versions, the Setup graphic that you use for a custom package must be a 16-color, 162-by-312-pixel bitmap (.bmp) file.

UNIX Platform

Dd361925.spacer(en-us,TechNet.10).gif Dd361925.spacer(en-us,TechNet.10).gif

Internet Explorer for UNIX provides a full set of browser features that have been optimized for UNIX operating systems. Internet Explorer supports the primary UNIX installed systems. Users can also remotely use Internet Explorer for UNIX from other UNIX operating systems, such as Linux, Silicon Graphics IRIX, and IBM AIX.

Implementation of the Internet Explorer user interface is consistent with the standard UNIX design. Internet Explorer for UNIX takes advantage of UNIX interface standards and was developed using the Motif look. Users benefit from the power and flexibility of Windows, implemented in a way that is immediately familiar to UNIX users.

Internet Explorer also includes support for existing UNIX applications, such as Emacs, Elm, RN, and VI. This integration uses the UNIX features and functions that users are accustomed to. You can easily configure Internet Explorer to handle e-mail links or open a favorite e-mail client or news reader directly from the browser. Integration with existing applications also includes the ability to read UNIX-specific file types from Web sites without opening the application for that file separately.

Using Internet Explorer for UNIX, you can customize existing applications or Multipurpose Internet Mail Extension (MIME) types directly from the browser. This functionality allows you to configure existing applications to handle different content on the Internet, such as Adobe Acrobat file formats. For example, a user can click on a link to an Acrobat file and Internet Explorer automatically opens the Acrobat Reader.

Some customization features, deployment methods, and maintenance practices for UNIX differ from Windows 32-bit versions. You should consider the following issues when you deploy Internet Explorer for UNIX:

  • Custom packages—You must build custom packages of Internet Explorer for UNIX from a Windows 32-bit computer. On the UNIX platform, the setup package will consist of one self-contained file rather than a collection of files or a set of floppy disks. 

  • Digital signatures—Unlike Windows 32-bit versions with Authenticode technology, UNIX does not perform digital-signature verification. UNIX browsers do not support certificates, so automatic-configuration files are not signed. You do not need to sign your programs or .cab files for UNIX. You should, therefore, ensure that your automatic-configuration Web site has restricted access so that no one can tamper with your files. 

  • Server installations—The UNIX functionality in the IEAK supports the common UNIX method of installing the customized product on only a few servers. Users can then run Internet Explorer from this location rather than installing the product locally. This configuration is recommended for UNIX installations. Windows Update Setup for Internet Explorer 5 and Internet Tools, which downloads .cab files, is not available on the UNIX platform.

  • Custom channels—When you create custom packages for UNIX, you should verify that any channels you include are displayed correctly for this platform. The channels will display in the Explorer bar, which appears in the left side of the browser window when the user clicks the Channels button, but they will not appear in a separate Channel bar on the desktop.

  • Custom components—For the UNIX platform, you should create a .cab file that contains your custom components and installation scripts. Then, specify the name of the .cab file, the script name, and size information when you run the Internet Explorer Customization wizard.

    When you install your customized IEAK package, it decompresses the .cab file, runs the script, and installs the components before it customizes the browser. After the setup script has run, it is deleted automatically. For more information, see the IEAK Help, which provides procedures and samples to help you create a script file and a .cab file so that you can prepare UNIX components for your custom package. 

    Security options—All security options apply to the Internet Explorer browser, but they are not necessarily applicable system-wide—that is, other programs may or may not respect these options. When you set the security options for Internet Explorer, you should be aware that the following options do not apply to the UNIX platform:

    • ActiveX controls and plug-ins 

    • Font downloads 

    • Software channel permissions 

    • Installation of desktop items 

    • Launching applications and files from an IFRAME element 

  • Setup download folder—You can find the IE5Setup.exe file in the media type folder created for your language and platform version. For example, the English version of Internet Explorer for UNIX would reside in the \Download\Unix\En folder of your build directory. 

  • File naming conventions—You may need to change the case of file names on a UNIX FTP server.

    Use the following conventions for UNIX operating systems: 

    Sun Solaris UNIX
    If you are using a case-sensitive UNIX FTP server, the .cab directory must not be capitalized. You must, however, capitalize the following file names:

    • BRANDING.CAB 

    • CUSTOM.CIF 

    • DESKTOP.CAB 

    • IE.CIF 

    • IECIF.CAB 

    • IE5SITES.DAT 

    AT&T UNIX
    On an AT&T UNIX FTP server, all file names must be capitalized.

    IRIX UNIX (Silicon Graphics)
    For IRIX UNIX, you must capitalize the following file names:

    • BRANDING.CAB 

    • CUSTOM.CIF 

    • DESKTOP.CAB 

    • IE.CIF 

    • IECIF.CAB 

    • IE5SITES.DAT 

    You should also use a text editor to modify the file names listed in the IE.CIF file to match the case of the files.

  • UNIX settings in the Internet Explorer Customization wizard—If you are building custom packages of Internet Explorer for UNIX, the Internet Explorer Customization wizard provides several screens where you can enter UNIX-specific settings. The UNIX Programs screen enables you to specify which programs will run when the user performs tasks related to e-mail, newsgroups, or printing, or when the user views the HTML source of a page. The UNIX Mappings screen enables you to specify the options for associating extensions and MIME types with a program so that the appropriate program starts when a user clicks a link. 

Dd361925.spacer(en-us,TechNet.10).gif