![]() At first, this updated blue screen only appeared if the system crashed during the boot sequence, although it would later be fully utilized in all bugchecks around the time of build 7880's compilation. Around build 7788, the blue screen was updated to support higher resolutions using VBE 2.0 and anti-aliasing. The user instructions were further updated and the font changed to Lucida Console in Windows XP.ĭuring the development of Windows 8, the blue screen underwent many significant changes. Additionally, the introduction of a VGA driver in the kernel itself allowed for the blue screen to be displayed in 640×480 graphics mode instead of the legacy 80×50 text mode - although the initial implementation in build 17 featured a bug which caused text to be drawn over a black background or on top of the boot screen graphic. The message was simplified in Windows 2000 to only include possible instructions for the user should they encounter the blue screen. Originally, a system crash only resulted in the error code being printed out to the screen, although later during Windows NT 3.1 development it was extended to also display the stack trace and a list of loaded drivers and their base addresses. Earlier builds merely print the error code to a debugger, if attached, and trigger a breakpoint in an infinite loop. The first known build to implement a blue screen is the October 1991 build. According to John Vert, the developer who originally wrote the code in the NT kernel that was responsible for controlling the screen in text mode, the white-on-blue color was chosen in order to match the MIPS' firmware display, as well as the default color scheme of the SlickEdit text editor that many NT developers had used at the time. On Windows NT, blue screens are also commonly known as STOP errors, referring to the *** STOP label that introduced the error code up to Windows 7. Windows Me also replaced MS-DOS black screen errors for startup initialization errors during startup, such as protection errors, with a blue screen. Other notable uses for the interface also include ACPI subsystem errors in early Windows 98 builds, which override the background color to red, or early builds of Windows Me that briefly replaced the graphical "safe to turn off" screen with a blue screen at one point. The wording for the exception message was updated with Windows Me as a part of similar changes to other error dialogs. The Windows 9x series is also unique in that it allows the user to continue after most system errors, although it often resulted in an unstable system. Windows 95 and later notably use the user interface to report severe system errors instead of exiting to DOS, which earned it the infamous "blue screen of death" nickname. The message shown when there is an unresponsive program was originally written by Steve Ballmer, as later revealed by Microsoft developer Raymond Chen. The interface is also used for a simple task manager implemented in Windows 3.1, which allows the user to terminate an unresponsive program or to reboot the system by pressing Ctrl+ Alt+ Del, given that Windows is running in the 386 Enhanced Mode. ![]() However, severe system errors would still cause Windows to exit back to MS-DOS in a similar fashion to old Windows versions. In Windows 3.x, this is mostly used in situations where a program could not continue running until the user acted, such as device conflicts or disk swaps. ![]() Other than this, the interface was kept virtually unchanged through the rest of the classic Windows series. Initially, it used a black background but later changed to blue with Windows 3.1. This is a full screen message in text mode, which suspends Windows until it is dismissed by the user by pressing a key. Whenever Windows does crash, it often results in a system hang or the shell returning to DOS.Ī user interface for displaying important system messages was first introduced in Windows 3.0 and is mostly used by virtual device drivers in 386 enhanced mode. When early Windows is run on a newer version of MS-DOS, it will print out an "Incorrect DOS version" error message, followed by portions of the computer's memory contents being spewed into the console buffer during the boot process, which is often thought to be a crash screen, although it is simply a bug that is present within the logo code. Contrary to popular belief, Windows 1.0 and Windows 2.x do not have a crash screen. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |