Working with Multiple Platforms

  • Article

Cc939910.chap_17(en-us,TechNet.10).gifCc939910.image(en-us,TechNet.10).gif

If you create customized browsers for different platforms, and you want the browsers to share similar settings, you can avoid repeating all customization steps for each platform version. If you use automatic configuration, you can use the IEAK Profile Manager to efficiently create profiles for more than one platform.

For most multiple-platform scenarios, you would build the 32-bit custom package first. Then, you can use those settings when using the IEAK Profile Manager or the Customization wizard for other platforms.

Recreating an Automatic-Configuration Profile in a Corporate Setting

If you are a corporate administrator, and you use automatic configuration, you can recreate an .ins file based on a profile from a different platform. This method eliminates the need to specify all the settings for each platform again. Note, however, that some features differ slightly across platforms. For more details, see Chapter 4 , "Working with Different Platforms."

To rebuild an .ins file for another platform by using the IEAK Profile Manager, carry out the following procedure.

Cc939910.prcarrow(en-us,TechNet.10).gifTo rebuild an .ins file by using the IEAK Profile Manager

  1. Open the .ins file that you want to use as a starting point in the IEAK Profile Manager (if it is not already open).

  2. On the Platform menu, click the platform that you want, such as UNIX.

  3. Set any additional platform-specific settings that you want.

  4. Save the IEAK profile, and copy the profile to your automatic-configuration server.
    The profile consists of the .ins file and any .cab files associated with your package.

Rebuilding a Custom Package for Another Platform

All IEAK users can rebuild packages for another platform by building in the same folder. Corporate administrators can build 32-bit, 16-bit, and UNIX packages. Developers, Internet content providers, and Internet service providers can build 32-bit and 16-bit packages.

Typically, you would build the 32-bit package first. Then, specify the same build location for subsequent packages on the File Locations screen in Stage 1 of the wizard. You do not need to specify the same settings for subsequent packages that you set for the first package.

If you build a Windows 32-bit-package and then rebuild a Windows 16-bit- package in the same folder, the file names are automatically converted to eight-character names with three-character extensions (8.3 format). If you build a Windows 32-bit-package in the same location as an existing Windows 16-bit package, the file names will continue to be in 8.3 format.

If you need to build a Windows 32-bit-package after you have built a Windows 16-bit-package, it's recommended that you build it in a new location.

.