Building Customized 16-bit IEAK Packages

You can now use the Internet Explorer Customization wizard and Profile Manager to build customized packages and administer 16-bit versions of Internet Explorer.

You build the packages and run the IEAK from a computer running Internet Explorer 5 and any Windows 32-bit operating system (except Windows NT 3.51).

Some customization features, deployment methods, and maintenance practices differ from the Windows 32-bit platform.

Here's some information you should know about building packages for Windows 16-bit platform:

• 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.
• If you build a Windows 32-bit platform package, and then rebuild a Windows 16-bit platform package in the same folder, the file names are automatically converted to eight-character names with three-character extensions (8.3 format). If you rebuild a Windows 32-bit platform package in the same location, the file names will continue to be converted into 8.3 format.If you need to build a Windows 32-bit platform package after you build a Windows 16-bit platform package, it's recommended that you build it in a new location.
• The Setup graphic must be a 16-color, 162-by-312 pixel .bmp file.
• You must include the Stack and Dialer for Windows 16-bit platforms if your users need dial-up access. 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.x and Windows for Workgroups 3.x) and one without it (for Windows NT 3.51). For dial-up access, Windows NT 3.51 computers must first be configured for Remote Access Service.
• You can create multiple-floppy-disk builds for Windows 3.1 and Windows for Workgroups 3.11, but not for Windows NT 3.51.
• The following security options for 32-bit versions of the browser do not apply to 16-bit versions of the browser:
  • User authentication
  • Font download
  • Software channel permissions
  • Installation of desktop items
  • Active scripting
  • Launching applications and files from an IFrame