
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: 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.
