Microsoft KB Archive/257331

{|
 * width="100%"|

PRB: Shell Does Not Start on Microsoft Windows NT Embedded System

 * }

Q257331

-

The information in this article applies to:


 * Microsoft Windows NT Embedded 4.0

-

SYMPTOMS
When you start Microsoft Windows NT Embedded 4.0 on a target computer, the selected shell may not start; only the graphical user interface (GUI) background may appear. If a mouse is installed on the target computer, a mouse pointer may appear and respond to movement, but it may not respond to button clicks. If a keyboard is installed on the target computer, the computer may not respond to the CTL+ALT+DEL keystroke combination.

CAUSE
A test Product ID (PID) was used to build the target embedded run-time image. The target computer's system date/time is either:


 * Greater than or equal to 24 hours earlier than the development computer's system date/time.
 * Greater than or equal to 60 days later than the development computer's system date/time.

RESOLUTION
To resolve this issue, do one of the following:


 * Set the target computer's system date/time to be no more than 24 hours earlier than the development computer's system date/time.
 * Set the development computer's system date/time to be no more than 24 hours later than the target computer's system date/time.
 * Rebuild the target embedded run-time image and reinstall it on the target system to reset the test PID timeout period.
 * Use a licensed embedded run-time PID rather than the test PID.

STATUS
This behavior is by design.

MORE INFORMATION
This behavior is an extension of the timing code that governs the use of the test PID. Test PID builds are limited to 60 days. The code that governs the 60-day time limitation also checks for license violations that arise from setting back the time on the target computer to artificially delay the 60-day count.