Table of Contents Categories
Windows Console
Topic: Software
From HandWiki - Reading time: 9 min
 A Windows Console with cmd.exe in Windows 10 20H2 | |
| Other names | Win32 console |
|---|---|
| Developer(s) | Microsoft |
| Repository | github |
| Written in | C++ |
| Operating system | Microsoft Windows |
| Platform | IA-32, x86-64, ARM64 |
| Type | Terminal emulator |
| License | MIT License |
| Website | docs |
Windows Console is the infrastructure for console applications in Microsoft Windows. An instance of a Windows Console has a screen buffer and an input buffer. It allows console apps to run inside a window or in hardware text mode (so as to occupy the entire screen). The user can switch between the two using the key combination. The text mode is unavailable in Windows Vista and later. Starting with Windows 10, however, a native full-screen mode is available.
Windows Console instances are typically used for apps that do not need to display images but might use color. Examples include cmd.exe, Windows PowerShell, Far Manager, and Midnight Commander.
In 2019, the console host was open-sourced under the MIT License, alongside Windows Terminal.[1]
Window and full screen modes
In Windows, a console application may run in two modes.
One mode places the text in a window and uses an operating system's font rendering. In this mode, an application's interaction with user is controlled by the windowing system. This is analogous to X Window System applications such as xterm.
The second is the full-screen mode. In Windows XP and earlier, the full-screen console uses a hardware text mode and uploads a raster font to the video adapter. This is analogous to a text system console. This early full-screen mode only supports VGA-compatible text modes, giving it a maximum character resolution of 80 columns by 28 rows.[2] This mode was deprecated in Windows Vista.[3] It was possible to circumvent this issue by installing a Windows XP display driver;[3] however, Windows 8 and later do not accept them.[4] Windows 10 features a full-screen mode once again, but this implementation uses the native Windows rendering subsystem, instead of the text mode. It can have as many columns and rows as fits on the screen.[5]
Apps can be made to switch between the two modes using the key combination.
Details
The input buffer is a queue where events are stored (from keyboard, mouse etc.). The output buffer is a rectangular grid where characters are stored, together with their attributes. A console window may have several output buffers, only one of which is active (i.e. displayed) for a given moment. Apps may programmatically interact with Windows Console through Windows API, which exposes both high-level functions (such as ReadConsole and WriteConsole) and low-level functions (e.g. ReadConsoleInput and WriteConsoleOutput).[6]
Users can change the color palette or font, either on the system-wide level or app-level. Each instance of a console app themselves, however, cannot change its color palette or font on the fly.
Windows Console apps are distinct from MS-DOS apps, even though on Windows (especially on Windows 9x), they may not look different. Windows Console apps have access to entire Windows API and do not run on MS-DOS or compatible operating systems. DOS apps, however, cannot access Windows API and may only run on 32-bit versions of Windows with the aid of Virtual DOS machine (VDM).
Implementations
Prior to Windows 95, there is no native support for consoles. Because Windows 3.1 and earlier are merely a graphical interface for MS-DOS, most text programs that ran on earlier Windows versions were actually MS-DOS programs running in a window. To simplify the task of porting applications to Windows, early versions of Visual C++ are supplied with QuickWin, a library that implements basic console functionality inside a regular window. A similar library for Borland C++ was called EasyWin.
Windows 9x
Windows 9x support is relatively poor compared to Windows NT, because the console window runs in the system virtual DOS machine and so keyboard input to a Win32 console application had to be directed to it by conagent.exe running in a DOS VM that are also used for real DOS applications by hooking the keyboard interrupt. conagent.exe then calls Vcond (which is a VxD). Vcond then had to pass the keyboard input to the System VM, and then finally to the Win32 console application. Besides performance, another problem with this implementation is that drives that are local to a DOS VM are not visible to a Win32 console application. This can cause confusion.
Under Windows 9x, the screen buffer mirrors the structure of VGA text buffer, with two bytes per character cell: one byte for character code, one byte for attributes (the character must be in OEM character set, the attribute is with high-intensity background/no blinking). This speeds up operation considerably if the actual VGA text mode is used.
Windows NT and Windows CE
_cmd.exe_Command_Prompt_800x574.png)
Traditionally, the Client/Server Runtime Subsystem (CSRSS) has been responsible for managing console windows on the Windows NT family of operating systems.[7] In Windows 7, CSRSS spawns one conhost.exe for each console window, to manage it. In Windows 8 and later, the console apps spawn their conhost.exe processes directly. This change has both security and usability implications. While CSRSS runs in a highly privileged security context, each conhost.exe runs in the same security context as the console app. In addition, in Windows 7, this change enabled console windows to have the features of the Aero Glass theme.[8]
On Windows NT and Windows CE, the screen buffer uses four bytes per character cell: two bytes for character code, two bytes for attributes. The character is then encoded in a 16-bit subset of Unicode (UCS-2).[9] For backward compatibility, the console APIs exist in two versions: Unicode and non-Unicode. The non-Unicode versions of APIs can use code page switching to extend the range of displayed characters (but only if TrueType fonts are used for the console window, thereby extending the range of codes available). Even UTF-8 is available as "code page 65001"[10] (displaying only from the UCS-2 subset of full Unicode[citation needed]).
As of the Windows 10 October 2018 update, the Windows Console has full Unicode support.[11]
See also
- Comparison of terminal emulators
- Command-line interface
- Shell (computing)
- System console
- Windows Terminal
- Linux console
- Text-based (computing)
- List of formerly proprietary software
References
- ↑ Cinnamon, Kayla (May 6, 2019). "Introducing Windows Terminal". Microsoft. https://devblogs.microsoft.com/commandline/introducing-windows-terminal/.
- ↑ Julio Sanchez; Maria P. Canton (2003), "VGA Fundamentals, Part II: DOS Graphics", The PC Graphics Handbook (for C++ Programmers), CRC Press, p. 125, ISBN 0849316782
- ↑ 3.0 3.1 "Some 16-bit DOS-based Programs and the Command Prompt will not run in full-screen mode in Windows Vista and in Windows 7". Support. Microsoft. 2011-09-23. http://support.microsoft.com/kb/926657.
- ↑ "Roadmap for Developing Drivers for the Windows 2000 Display Driver Model (XDDM)". Windows Dev Center - Hardware. Microsoft. 16 November 2013. http://msdn.microsoft.com/en-us/library/windows/hardware/ff569512.aspx. "XDDM and VGA drivers will not compile on Windows 8 and later versions"
- ↑ Tkachenko, Sergey (2014-11-24). "Open command prompt fullscreen in Windows 10" (in en-US). https://winaero.com/open-command-prompt-fullscreen-in-windows-10/.
- ↑ "Console Modes". Microsoft. https://docs.microsoft.com/en-us/windows/console/console-modes.
- ↑ Microsoft Security Advisory (930181): Exploit Code Published Affecting Windows Client Server Run-Time Subsystem
- ↑ Yosifovich, Pavel; Ionescu, Alex; Russinovich, Mark E.; Solomon, David A. (2017-05-15). Windows Internals, Part 1: System architecture, processes, threads, memory management, and more (7th ed.). Redmond, Washington: Microsoft Press. p. 67. ISBN 9780735684188.
- ↑ "Console Reference". Microsoft. 2009. http://msdn.microsoft.com/en-us/library/ms682087(VS.85).aspx.
- ↑ "Release Notes" (in en-us). https://docs.microsoft.com/en-us/windows/wsl/release-notes. "Console: Fix for no output text being displayed in codepage 65001 (utf8)"
- ↑ Turner, Rich (2018-11-15). "Windows Command-Line: Unicode and UTF-8 Output Text Buffer" (in en-us). Microsoft. https://devblogs.microsoft.com/commandline/windows-command-line-unicode-and-utf-8-output-text-buffer/.
External links
 |  |
EncycloReader
is supported by the 
KSF