How To Apply Service Pack 6a and Security Update to Windows NT Embedded 4.0 Run-Time Image (318197)

MORE INFORMATION

Update with the Standard OS Option

To update a Microsoft Windows NT Embedded 4.0 run-time image that uses the Standard OS option, follow these steps:

1. Install Windows NT 4.0 Option Pack on the Windows NT Embedded 4.0 run-time image, and then click the Update only option in the Installation Wizard (which updates IIS 3.0 to IIS 4.0 if IIS 3.0 is installed)
2. Reboot the embedded run-time image.
3. Install Windows NT 4.0 Service Pack 6.0a on the embedded run-time image.
4. Reboot the embedded run-time image.
5. Install Post-Windows NT 4.0 Service Pack 6a Security Rollup Package (SRP). To do this, unzip Q299444i.exe, save the file to a local directory, and then run the update command on the embedded run-time image.
6. Reboot the embedded run-time image.

For more information about each step, refer to the articles that are listed in the "References" section.

Update with the Minimal OS Option

To update a Microsoft Windows NT Embedded 4.0 run-time image that uses the Minimal OS option, follow these steps:

1. On the Windows NT Embedded 4.0 run-time image, add a directory to the path that includes the files that are listed below. You can obtain this list of files from a full installation of Windows NT 4.0 that includes Service Pack 5, or you can obtain the list from an installation of Windows NT Embedded 4.0 that uses the Standard OS option.
   • Lz32.dll
   • Version.dll
   • Cfgmgr32.dll
   • Ws2_32.dll
   • Ws2help.dll
   • Regsvr32.exe
   • Ole32.dll
2. Copy the Setup.log file from either of the following installations to C:\Winnt\Repair\ on the embedded run-time image:
   
   
   • A similar full installation of Windows NT 4.0 that includes Service Pack 5.
   • An installation of Windows NT Embedded 4.0 run-time image that uses the Standard OS option.
   NOTE: You must create the repair directory on the embedded run-time image.
3. Install Windows NT 4.0 Service Pack 6.0a on the embedded run-time image.
4. Reboot the embedded run-time image.
5. Install Post-Windows NT 4.0 Service Pack 6a Security Rollup Package (SRP). To do this, unzip Q299444i.exe, save the file to a local directory, and then run the update command on the embedded run-time image.
6. Reboot the embedded run-time image.

For more information about each step, refer to the articles that are listed in the "References" section of this article.

NOTE: Microsoft does not support the upgrade to IIS 4.0 in Windows NT Embedded 4.0 run-time images that use the Minimal OS option. In addition, if the embedded run-time image uses the Minimal OS option, remove files that you add to the Windows NT Embedded 4.0 run-time image at your own risk. If you remove these files, you may affect the functionality and reliability of the Windows NT Embedded 4.0 run-time image that uses the Minimal OS option. This does not apply to files that you update.

Problems That May Occur When You Update

Multiprocessor Issue

For additional information about how to upgrade a multiprocessor device by using one of the methods in this article, click the article number below to view the article in the Microsoft Knowledge Base: Windows NT Embedded 4.0 does not produce the correct Setup.log file to upgrade multiprocessor devices by default.

Internet Information Server (IIS)

Neither of the following components can create a clone when a functional IIS 4.0 is present:

• The System Clone component, which is available in Target Designer in the Main Node\Applications Node\Utilities Node folder.
• The system preparation tool (Sysprep.exe), which is available in the Windows NT 4.0 OEM Preinstall Kit (OPK).

You must not change the unique machine key that is present when IIS 4.0 is installed. IIS 4.0 cannot continue to function if you change the key. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: For additional information and the system preparation tool, click the article number below to view the article in the Microsoft Knowledge Base: