#Tangled pc vs console windows#

WinME also adopted some features from Windows 2000 (e.g.

Note: Windows ME (Millennium Edition) was an interesting chimera! It finally replaced the MS-DOS underpinnings and real-mode support of previous versions of Windows with new OS underpinnings that took advantage of IntelвЂ™s 8026 processors. Windows 1.x, 2.x, 3.x, 95, and 98, allВ ran atop an MS-DOS foundation and heavily relied upon their MS-DOS foundations. Many competing GUIвЂ™s emerged rapidly in the Apple Lisa and Macintosh, Commodore Amiga (Workbench), Atari ST (DRIвЂ™s GEM), Acorn Archimedes (Arthur/RISC OS), Sun Workstation, X11/X Window System, and many others, including Microsoft Windows: Windows 1.0 arrived in 1985, and was basically an MS-DOS application that provided a simple tiled-window GUI environment, allowing users to run several applications side-by-side: The GUI goes mainstreamД®nter, the Graphical User Interface (GUI), inspired by the work of XeroxвЂ™ Alto. A more user-friendly, productivity-oriented user experience was required.

#Tangled pc vs console how to#

But hundreds of billions of command-line scripts and commands are executed every day on Windows alone! While the Command-Line is a powerful tool in the hands of those with the patience and tenacity to learn how to make the most of the available commands and tools, most non-technical users struggled to use their Command-Line driven computers effectively, and most disliked having to learn and remember many seemingly arcane/abbreviated commands to make their computers do anything useful. You may never/rarely see batch or command-line scripts running since many are executed in the background while, for example, logging into a work PC. MS-DOS was very rapidly adopted by businesses large and small, that, combined, created many millions of batch scripts, some of which are still in use today! Batch scripts are used to automate the configuration of usersвЂ™ machines, setting/changing security settings, updating software, building code, etc. Like most mainstream Operating Systems of the time, MicrosoftвЂ™s MS-DOSвЂ™ вЂњCommand-Line InterpreterвЂќ or вЂњshellвЂќ provided a simple, quirky, but relatively effective set of commands, and a command-scripting syntax for writing batch (.bat) files. Ultimately, MS-DOS rose to prominence as the de-facto standard OS for IBM PCвЂ™s & compatibles, especially in businesses:

Machines based on Unix, CP/M, DR-DOS, and others tussled for position and market share. Our journey now continues along a rather tangled path, starting with early PCвЂ™s, winding through MicrosoftвЂ™s involvement with several Operating Systems, to the newly reinvigorated Command-Line of today: From humble beginnings вЂ“ MS-DOSД«ack in the early years of the PC industry, most computers were operated entirely by typing commands into the command-line. In this seriesвЂ™ previous post,В we discussed the history and fundamentals of the Command-Line and saw how the architecture of Command-Lines in general has remained largely consistent over time, even while terminals evolved from electro-mechanical teletypes through to modern terminal applications.

Introducing the Windows Pseudo Console (ConPTY).

The evolution of the Windows Command-Line.

Note: This chapter list will be updated as more posts are published:

#Tangled pc vs console series#

Posts in the вЂњWindows Command-LineвЂќ series Specifically, weвЂ™ll explore its humble origins in MS-DOS, to its modern-day incarnation supporting tools like PowerShell and Windows Subsystem for Linux. In this post weвЂ™ll discuss some of the background & history behind the Windows Command-Line. Welcome to the second post in this вЂњWindows Command-LineвЂќ series.