Jump to content

DOS

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by G.Reza Yahyavi Fakour (talk | contribs) at 10:42, 16 June 2015. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

This article is about the family of operating systems for x86-based computers (most commonly IBM PC-compatibles). For other uses, see DOS (disambiguation).
FreeDOS screenshot showing the command line interface, directory structure and version information.

DOS (/dɒs/), short for "Disk Operating System",[1] is an acronym for several closely related operating systems that dominated the IBM PC compatible market between 1981 and 1995, or until about 2000 if one includes the partially DOS-based Microsoft Windows versions 95, 98, and Millennium Edition.

Related systems include MS-DOS, PC-DOS, DR-DOS, FreeDOS, PTS-DOS, ROM-DOS, Novell DOS, OpenDOS, 86-DOS , OSx16 and several others.

In spite of the common usage, none of these systems were simply named "DOS" (a name given only to an unrelated IBM mainframe operating system in the 1960s). A number of unrelated, non-x86 microcomputer disk operating systems had "DOS" in their name, and are often referred to simply as "DOS" when discussing machines that use them (e.g. AmigaDOS, AMSDOS, ANDOS, Apple DOS, Atari DOS, Commodore DOS, CSI-DOS, ProDOS, and TRS-DOS). While providing many of the same operating system functions for their respective computer systems, programs running under any one of these operating systems would not run under others (Compatible and incompatible).

Compatiblity

Compatibility is common capabilities between two or many Operating Systems. Compatibility may limit to the file system as method of managing and accessing files by Operating Systems (FAT16 , FAT32 , HPFS , ...), or Operating System maybe expanded and extended by Creator(s)/Developer(s) to cover all services that provided by other OS like as MS-DOS, include : commands, interrupts, reserved system names, format of commands, user interface, functions, and ... .
Also, if non of those common managing methods presents in two or more Operating Systems, Operating Systems are incompatible.
For transparency, if in one computer system, user changes installed Operating System to other incompatible Operating System, data and files will be lost and(or) programs will not executes or rejects by new OS.

Operating Systems Creators/Authors defines compatibility depth. End-users must notice to Operating Systems manuals for details and information.

History

Further information: Comparison of DOS operating systems and Timeline of DOS operating systems

Origins

IBM PC-DOS (and the separately sold MS-DOS) and its predecessor, 86-DOS, were loosely inspired by Digital Research's CP/M, which was the dominant disk operating system for 8-bit Intel 8080 and Zilog Z80 based microcomputers. PC-DOS ran on Intel 80x86-family processors.

When IBM introduced the IBM PC, built with the Intel 8088 microprocessor, they needed an operating system. Seeking an 8088-compatible build of CP/M, IBM initially approached Microsoft CEO Bill Gates (possibly believing that Microsoft owned CP/M due to the Microsoft Z-80 SoftCard, which allowed CP/M to run on an Apple II[2]). IBM was sent to Digital Research, and a meeting was set up. However, the initial negotiations for the use of CP/M broke down—Digital Research wished to sell CP/M on a royalty basis, while IBM sought a single license, and to change the name to "PC DOS". DR founder Gary Kildall refused, and IBM withdrew.[2][3]

IBM again approached Bill Gates. Gates in turn approached Seattle Computer Products. There, programmer Tim Paterson had developed a variant of CP/M-80, intended as an internal product for testing SCP's new 16-bit Intel 8086 CPU card for the S-100 bus. The system was initially named "QDOS" (Quick and Dirty Operating System), before being made commercially available as 86-DOS. Microsoft purchased 86-DOS, allegedly for $50,000. This became Microsoft Disk Operating System, MS-DOS, introduced in 1981.[4]

Microsoft also licensed their system to multiple computer companies, who supplied MS-DOS for their own hardware, sometimes under their own names. Microsoft later required the use of the MS-DOS name, with the exception of the IBM variant. IBM continued to develop their version, PC DOS, for the IBM PC.[4] Digital Research became aware that an operating system similar to CP/M was being sold by IBM (under the same name that IBM insisted upon for CP/M), and threatened legal action. IBM responded by offering an agreement: they would give PC consumers a choice of PC DOS or CP/M-86, Kildall's 8086 version. Side-by-side, CP/M cost almost $200 more than PC DOS, and sales were low. CP/M faded, with MS-DOS and PC DOS becoming the marketed operating system for PCs and PC compatibles.[2]

Microsoft originally only sold MS-DOS to Original equipment manufacturers (OEMs). One major reason for this was that not all early PCs were 100% IBM PC compatible. DOS was structured such that there was a separation between the system specific device driver code (IO.SYS) and the DOS kernel (MSDOS.SYS). Microsoft provided an OEM Adaptation Kit which allowed OEMs to customize the device driver code to their particular system. By the early 1990s, most PCs adhered to IBM PC standards so Microsoft began selling MS-DOS in retail with MS-DOS 5.0.

In the mid-1980s Microsoft developed a multitasking version of DOS[5][6]. This version of DOS is generally referred to as "European MS-DOS 4" because it was developed for ICL and licensed to several European companies. It was never released to the general public or any other OEMs. This version of DOS supports preemptive multitasking, shared memory, device helper services and New Executable ("NE") format executables. None of these features were used in later versions of DOS but they were used to form the basis of the OS/2 1.0 kernel. This version of DOS is distinct from the widely released PC-DOS 4 which was developed by IBM and based upon DOS 3.3.

Digital Research attempted to regain the market lost from CP/M-86; initially with Concurrent DOS, FlexOS and DOS Plus (both compatible with both MS-DOS and CP/M-86 software), later with Multiuser DOS (compatible with both MS-DOS and CP/M-86 software) and DR-DOS (compatible with MS-DOS software). Digital Research was bought by Novell, and DR DOS became Novell DOS 7; later, it was part of Caldera (under the names OpenDOS and DR-DOS 7.02/7.03), Lineo, and DeviceLogics.

Microsoft and IBM later had a series of disagreements over two successor operating systems to DOS - Microsoft's Windows and IBM's OS/2.[7] They split development of their DOS systems as a result.[8] The last retail version of MS-DOS was MS-DOS 6.22, after this MS-DOS was used as a bootloader for Windows 9x. The last retail version of PC DOS was PC DOS 2000 (a.k.a. PC DOS 7 revision 1) though IBM did later develop PC DOS 7.10 for OEMs and internal use.

The FreeDOS project began 26 June 1994, when Microsoft announced it would no longer sell or support MS-DOS. Jim Hall then posted a manifesto proposing the development of an open-source replacement. Within a few weeks, other programmers including Pat Villani and Tim Norman joined the project. A kernel, the command.com command line interpreter (shell) and core utilities were created by pooling code they had written or found available. There were several official pre-release distributions of FreeDOS before the FreeDOS 1.0 distribution was released on 3 September 2006. Made available under the GNU General Public License (GPL), FreeDOS does not require license fees or royalties.[9][10]

Decline

Main article: History of Microsoft Windows

Early versions of Microsoft Windows ran on top of a separate version of DOS.[11] By the early 1990s, Windows saw heavy use on new DOS systems. With MS-Windows for Workgroups 3.11, DOS was almost reduced to the role of a boot loader for the Windows kernel; in 1995, MS-Windows 95 was bundled as a standalone operating system that did not require a separate DOS license. With Windows 95 (and Windows 98 and Me, that followed it), the MS-DOS kernel remained, but with Windows as the system's graphical shell. With Windows 95 and 98, but not ME, the MS-DOS component could be run without starting Windows.[12][13] With DOS no longer required to use Windows, the majority of PC users stopped using it directly.

Continued use

DOSBox

Currently available DOS systems are FreeDOS, DR-DOS (and Enhanced DR-DOS), ROM-DOS, PTS-DOS, RxDOS, Multiuser DOS,[14] REAL/32, and others. Some computer manufacturers, including Dell and HP, sell computers with FreeDOS as the OEM operating system.[15][16] NX-DOS is currently under development. It is 16-bit, real-time, networkable, bootable from a floppy, and has an incomplete USB driver. It dates back to 1992 as a personal project, and was released as GPL in 2005.[17]

Embedded systems

DOS's structure of accessing hardware directly makes it ideal for use in embedded devices. The final versions of DR-DOS are still aimed at this market.[18] ROM-DOS was used as the embedded system on the Canon PowerShot Pro 70.[19]

Emulation

Under Linux, it is also possible to run copies of DOS and many of its clones under DOSEMU, a Linux-native virtual machine for running DOS programs at near native speed. There are a number of other emulators for running DOS under various versions of UNIX, even on non-x86 platforms, such as DOSBox.[20][21]

DOS emulators are gaining popularity among Windows XP and Windows Vista users, due to these systems being very incompatible with pure DOS. They can be used to run games or other DOS software. One of the best-known is DOSBox, designed for legacy gaming (e.g. King's Quest, Doom) on modern operating systems.[11][20]

It is possible to run DOS applications in a copy of a DOS operating system on a PC emulator, allowing better compatibility than DOS emulators where the emulation of the DOS operating environment is imperfect.[22]

Design

All MS-DOS-type operating systems run on machines with the Intel x86 or compatible CPUs, mainly the IBM PC and compatibles. Machine-dependent versions of MS-DOS were produced for many non-IBM-compatible x86-based machines, with variations from relabelling of the Microsoft distribution under the manufacturer's name, to versions specifically designed to work with non-IBM-PC-compatible hardware. For as long as application programs used DOS APIs instead of direct hardware access, they could thereby also run on non-IBM-PC compatible machines. In 1985, Digital Research also had a version of Concurrent DOS 68K for use on Motorola 68000 CPUs, and the original FreeDOS kernel DOS-C derived from DOS/NT, also for Motorola CPUs, in the early 1990s. While these systems resembled the DOS architecture, applications were not binary compatible due to the incompatible instruction sets of these non-x86-CPUs. However, applications written in high-level languages could be ported easily.

DOS is a single-user, single-tasking operating system with basic kernel functions that are non-reentrant: only one program at a time can use them and DOS itself has no functionality to allow more than one program it execute at a time. The DOS kernel provides various functions for programs (an application program interface), like character I/O, file management, memory management, program loading and termination.

DOS by default provides a primitive ability for shell scripting, via batch files (with the filename extension .BAT). These are text files that can be created in any text editor. They are executed in the same fashion as compiled programs, and run each line of the batch file as a command. Batch files can also make use of several internal commands, such as GOTO and conditional statements.[23] GOSUB and simple arithmetic is supported with the DR DOS COMMAND.COM as well as some with third-party shells like 4DOS; however, no real form of programming is usually enabled.

The operating system offers an application programming interface that allows development of character-based applications, but not for accessing most of the hardware, such as graphics cards, printers, or mice. This required programmers to access the hardware directly, usually resulting in each application having its own set of device drivers for each hardware peripheral. Hardware manufacturers would release specifications to ensure device drivers for popular applications were available.[24]

Boot sequence

  • The bootstrap loader on PC-compatible computers (MBR or boot sector) is located at track zero, the first sector on a disk. The ROM BIOS will load this sector into memory at address 0000h:7C00h, and typically check for a signature "55h AAh" at offset +1FEh. If the sector is not considered to be valid, the ROM BIOS will try the next physical disk in the row, otherwise it will jump to the load address with certain registers set up.
  • If the loaded boot sector happens to be a Master Boot Record (MBR), as found on partitioned media, it will relocate itself to 0000h:0600h in memory,[25] otherwise this step is skipped. The MBR code will scan the partition table, which is located within this sector, for an active partition (modern MBRs check if bit 7 is set at offset +1BEh+10h*n, whereas old MBRs simply check for a value of 80h), and, if found, load the first sector of the corresponding partition, which holds the Volume Boot Record (VBR) of that volume, into memory at 0000h:7C00h in the similar fashion as it had been loaded by the ROM BIOS itself. The MBR will then pass execution to the loaded portion with certain registers set up.
  • The sector content loaded at 0000h:7C00h constitutes a VBR now. VBRs are operating system specific and cannot be exchanged between different DOS versions in general, as the exact behaviour differs between different DOS versions. In very old versions of DOS such as DOS 1.x, the VBR would load the whole IO.SYS/IBMBIO.COM file into memory at 0000h:0600h.[26] For this to work, these sectors had to be stored in consecutive order on disk by SYS. In later issues, it would locate and store the contents of the first two entries in the root directory at 0000h:0500h and if they happen to reflect the correct boot files as recorded in the VBR, the VBR would load the first 3 consecutive sectors of the IO.SYS/IBMBIO.COM file into memory at 0070h:0000h. The VBR also has to take care to preserve the contents of the Disk Parameter Table (DPT). Finally, it passes control to the loaded portion by jumping to its entry point with certain registers set up (with considerable differences between different DOS versions).
  • In modern DOS versions, where the VBR has loaded only the first 3 sectors of the IO.SYS/IBMBIO.COM file into memory, the loaded portion contains another boot loader, which will then load the remainder of itself into memory, using the root directory information stored at 0000h:0500h. For most versions, the file contents still need to be stored in consecutive order on disk. In older versions of DOS, which were still loaded as a whole, this step is skipped.
  • The DOS system initialization code will initial its builtin device drivers and then load the DOS kernel, located in MSDOS.SYS on MS-DOS systems, into memory as well. In Windows 9x, the DOS system initialization code and builtin device drivers and the DOS kernel are combined into a single IO.SYS file while MSDOS.SYS is used as a text configuration file.
  • The CONFIG.SYS file is then read to parse configuration parameters. The SHELL variable specifies the location of the shell which defaults to COMMAND.COM.
  • The shell is loaded and executed.
  • The startup batch file AUTOEXEC.BAT is then run by the shell.[27][28]

The DOS system files loaded by the boot sector must be contiguous and be the first two directory entries.[29] As such, removing and adding this file is likely to render the media unbootable. It is, however, possible to replace the shell at will, a method that can be used to start the execution of dedicated applications faster. This limitation does not apply to any version of DR DOS, where the system files can be located anywhere in the root directory and do not need to be contiguous. Therefore, system files can be simply copied to a disk provided that the boot sector is DR DOS compatible already.

In PC-DOS and DR-DOS 5.0 and above, the DOS system files are named IBMBIO.COM instead of IO.SYS and IBMDOS.COM instead of MSDOS.SYS. Older versions of DR DOS used DRBIOS.SYS and DRBDOS.SYS instead.

File system

DOS uses a filesystem which supports 8.3 filenames; 8 characters for the filename and 3 characters for the extension. Starting with DOS 2 hierarchical directories are supported. Each directory name is also 8.3 format but the maximum directory path length is 64 characters due to the internal current directory structure (CDS) tables that DOS maintains. Including the drive name, the maximum length of a fully qualified filename that DOS supports is 80 characters using the format drive:\path\filename.ext followed by a null byte.

DOS uses the File Allocation Table (FAT) filesystem. This was originally FAT12 which supported up to 4078 clusters per drive. DOS 3 added support for FAT16 which used 16-bit allocation entries and supported up to 65518 clusters per drive. DOS 3.31 added support for FAT16B which removed the 32 MB drive limit and could support up to 2 GB. Finally MS-DOS 7.1 (the DOS component of Windows 9x) added support for FAT32 which used 32-bit allocation entries and could support hard drives up to 137 GB.

Starting with DOS 3.1, file redirector support was added to DOS. This was initially used to support networking but was later used to support CD-ROM drives with MSCDEX. IBM PC-DOS 4.0 also had preliminary installable file system (IFS) support but this was unused and removed in DOS 5.

Drive naming scheme

Main article: Drive letter assignment

In DOS, drives are referred to by identifying letters. Standard practice is to reserve "A" and "B" for floppy drives. On systems with only one floppy drive DOS assigns both letters to the drive, prompting the user to swap disks as programs alternate access between them. This facilitates copying from floppy to floppy or having a program run from one floppy while accessing its data on another. Hard drives were originally assigned the letters "C" and "D". DOS could only support one active partition per drive. As support for more hard drives became available, this developed into first assigning a drive letter to each drive's active primary partition, then making a second pass over the drives to allocate letters to logical drives in the extended partition, then a third pass to give any other non-active primary partitions their names (where such additional partitions existed and contained a DOS-supported file system.) Lastly, DOS allocates letters for optical disc drives, RAM disks, and other hardware. Letter assignments usually occur in the order the drivers are loaded, but the drivers can instruct DOS to assign a different letter; drivers for network drives, for example, typically assign letters nearer the end of the alphabet.[30]

Because DOS applications use these drive letters directly (unlike the /dev directory in Unix-like systems), they can be disrupted by adding new hardware that needs a drive letter. An example is the addition of a new hard drive having a primary partition where a pre-existing hard drive contains logical drives in extended partitions; the new drive will be assigned a letter that was previously assigned to one of the extended partition logical drives. Moreover, even adding a new hard drive having only logical drives in an extended partition would still disrupt the letters of RAM disks and optical drives. This problem persisted through Microsoft's DOS-based 9x versions of Windows until they were replaced by versions based on the NT line, which preserves the letters of existing drives until the user changes them.[30] Under DOS, this problem can be worked around by defining a SUBST drive and installing the DOS program into this logical drive. The assignment of this drive would then be changed in a batch job whenever the application starts. Under some versions of Concurrent DOS, as well as under Multiuser DOS, System Manager and REAL/32, the reserved drive letter L: will automatically be assigned to the corresponding load drive whenever an application starts.

Reserved device names

Main article: Device file

There are reserved device names in DOS that cannot be used as filenames regardless of extension; these are used to send application output to hardware peripherals. These restrictions also affect several Windows versions, in some cases causing crashes and security vulnerabilities.[31]

A partial list of these reserved names is: NUL:, CON:, AUX:, PRN:, COM1:, COM2:, COM3:, COM4:, LPT1:, LPT2:, LPT3:,[32] and sometimes LPT4: as well. AUX: typically defaults to COM1:, and PRN: to LPT1:, but these defaults can be changed on some systems.

Colons are not necessary in some cases, for example: 

echo This does nothing > nul

It is still possible to create files or directories using these reserved device names, such as through direct editing of directory data structures in disk sectors. Such naming, such as starting a file name with a space, has sometimes been used by viruses or hacking programs to obscure files from users who do not know how to access these locations.

Memory management

Main article: DOS memory management

DOS was originally designed for the Intel 8086/8088 processor and therefore could only directly access a maximum of 1 MB of RAM. Due to PC architecture only a maximum of 640 KB (known as conventional memory) is available as the upper 384 KB is reserved.

Specifications were developed to allow access to additional memory. The first was the Expanded Memory Specification (EMS) which originally allowed memory on an add-on card to be accessed via a 64 KB page frame in the reserved upper memory area. 80386 and later systems could use a virtual 8086 mode (V86) mode memory manager like EMM386 to create expanded memory from extended memory without the need of an add-on card. The second specification was the Extended Memory Specification (XMS) for 80286 and later systems. This provided a way to copy data to and from extended memory, access to the 65520-byte High Memory Area (HMA) directly above the first megabyte of memory and the Upper Memory Block (UMB) area. Generally XMS support was provided by HIMEM.SYS or a V86 mode memory manager like QEMM or 386MAX which also supported EMS.

Starting with DOS 5, DOS could directly take advantage of the HMA by loading its kernel code and disk buffers there via the DOS=HIGH statement in CONFIG.SYS. DOS 5+ also allowed the use of available UMBs via the DOS=UMB statement in CONFIG.SYS.

DOS under OS/2 and Windows

See also: Virtual DOS Machine
CMD.EXE, the DOS-styled command prompt used in Microsoft-NT-based Windows.

The DOS emulation in OS/2 and Windows runs in much the same way as native applications do. They can access all of the drives and services, and can even use the host's clipboard serves. Because the drivers for file systems and such forth reside in the host system, the DOS emulation needs only provide a DOS API translation layer which converts DOS calls to OS/2 or Windows system calls. The translation layer generally also converts BIOS calls and virtualizes common I/O port accesses which many DOS programs commonly use.

In Windows 3.1 and 9x, the DOS virtual machine is provided by WINOLDAP. WinOldAp creates a virtual machine based on the program's PIF file, and the system state when Windows was loaded. The DOS graphics mode, both character and graphic, can be captured and run in the window. DOS applications can use the Windows clipboard by accessing extra published calls in WinOldAp, and one can paste text through the WinOldAp graphics.

The emulated DOS in OS/2 and Windows NT is based upon DOS 5. Although there is a default configuration (config.sys and autoexec.bat), one can use alternate files on a session-by-session basis. It is possible to load drivers in these files to access the host system, although these are typically third-party.

Under OS/2 2.x and later, the DOS emulation is provided by DOSKRNL. This is a file that represents the combined IBMBIO.COM and IBMDOS.COM, the system calls are passed through to the OS/2 windowing services. DOS programs run in their own environment, the bulk of the DOS utilities are provided by bound DOS / OS2 applications in the \OS2 directory. OS/2 can run Windows 3.1 applications by using a modified copy of Windows (Win-OS/2). The modifications allow Windows 3.1 programs to run seamlessly on the OS/2 desktop, or one can start a WinOS/2 desktop, similar to starting Windows from DOS.

OS/2 allows for 'DOS from Drive A:', (VMDISK). This is a real DOS, like MS-DOS 6.22 or PC-DOS 5.00. One makes a bootable floppy disk of the DOS, add a number of drivers from OS/2, and then creates a special image. The DOS booted this way has full access to the system, but provides its own drivers for hardware. One can use such a disk to access cdrom drives for which there is no OS/2 driver.

In Windows NT (2000, XP, Vista, 7), the DOS emulation is provided by way of a virtual DOS machine (NTVDM). The DOS files reside in NTIO.SYS and NTBIO.SYS as usual, but run in the virtual machine provided by NTVDM. The character input is passed to the console session that launched the DOS program. This allows one to use CLI features such as pipes and redirection between DOS and Windows NT. The OS/2 emulation in NT and 2000 is similar, but no virtual machine is loaded: it is handled by OS2SS.EXE and OS2.EXE.

64-bit versions of Windows do not support NTVDM and cannot run 16-bit DOS applications directly.

User interface

See also: List of DOS commands

DOS systems utilize a command line interface. Programs are started by entering their filename at the command prompt. DOS systems include several programs as system utilities, and provides additional commands that don't correspond to programs (internal commands).[33]

In an attempt to provide a more user-friendly environment, numerous software manufacturers wrote file management programs that provided users with menu- and/or icon-based interfaces. Microsoft Windows is a notable example, eventually resulting in Microsoft Windows 9x becoming a self-contained program loader, and replacing DOS as the most-used PC-compatible program loader. Text user interface programs included Norton Commander, Dos Navigator, Volkov Commander, Quarterdesk DESQview, and SideKick. Graphical user interface programs included Digital Research's Graphical Environment Manager (originally written for CP/M) and GEOS.

Eventually, the manufacturers of major DOS systems began to include their own environment managers. MS-DOS/IBM DOS 4 included DOS Shell;[34] DR DOS 5.0, released the next year, included ViewMAX, based upon GEM.[35]

Terminate and Stay Resident

Main article: Terminate and Stay Resident

DOS was not a multitasking operating system. DOS did however provide a Terminate and Stay Resident (TSR) function which allowed programs to remain resident in memory. These programs could hook the system timer and/or keyboard interrupts to allow themselves to run tasks in the background or to be invoked at any time preempting the current running program effectively implementing a simple form of multitasking on a program-specific basis. The PRINT command did this to implement background print spooling. Borland Sidekick, a popup personal information manager (PIM) also used this technique. Terminate and Stay Resident programs were also used to provide additional features not available by default. Programs like CED and DOSKey provided command line editing facilities beyond what was natively available in COMMAND.COM. Programs like the Microsoft CD-ROM Extensions (MSCDEX) provided access to files on CD-ROM disks.

Software

Further information: Category:DOS software
Arachne web browser

DOS was the dominant PC-Compatible platform and many notable programs were written for it. These included:

See also

References

  1. ^ Murdock, Everett (1988). DOS the Easy Way. EasyWay Downloadable Books. ISBN 0-923178-00-7.
  2. ^ a b c Rolander, Tom. "The rest of the story: How Bill Gates beat Gary Kildall in OS war, Part 1" (Interview). {{cite interview}}: Unknown parameter |interview= ignored (help); Unknown parameter |show= ignored (help)
  3. ^ Bove, Tony (2005). Just Say No to Microsoft. No Starch Press. pp. 9–11. ISBN 1-59327-064-X.
  4. ^ a b Bellis, Mary. "The Unusual History of MS-DOS The Microsoft Operating System". Retrieved 2008-09-02.
  5. ^ "Did you know that OS/2 wasn't Microsoft's first non Unix multi-tasking operating system?".
  6. ^ http://blogs.technet.com/b/exchange/archive/2004/03/05/larry-osterman-s-biography.aspx
  7. ^ Pollack, Andrew (1991-07-27). "Microsoft Widens Its Split With I.B.M. Over Software". New York Times. Retrieved 2008-09-02.
  8. ^ Brinkley, Joel (1999-05-28). "I.B.M. Executive Describes Price Pressure by Microsoft". New York Times. Retrieved 2008-09-02.
  9. ^ Jim Hall (2002-03-25). "The past, present, and future of the FreeDOS Project". Retrieved 2008-06-14.
  10. ^ Hall, Jim (September 23, 2006). "History of FreeDOS". freedos.org. Retrieved 2007-05-28.
  11. ^ a b James Bannan (2006-10-13). "HOW TO: Coax retro DOS games to play on Vista". Retrieved 2008-07-03.
  12. ^ "Finding The DOS In Windows 95". Smart Computing. 1996. Retrieved 2008-07-12. {{cite web}}: Unknown parameter |month= ignored (help)
  13. ^ http://support.microsoft.com/kb/138996
  14. ^ http://www.conctrls.com/CCInews.html
  15. ^ Hall, Jim (2007-07-13). "Jim Hall". Retrieved 2008-06-12.
  16. ^ "Dell PCs Featuring FreeDOS". Retrieved 2008-06-14.
  17. ^ "GPL'd DOS workalike adds features". 2007-04-01. Retrieved 2008-06-01.
  18. ^ "DR DOS Embedded DOS". Retrieved 2008-09-26.
  19. ^ "Datalight DOS Selected for Canon's New Line of Digital Still Cameras". Business Wire. 1999-08-24. Retrieved 2008-09-26.
  20. ^ a b "DOSBox Information". Retrieved 2008-05-18.
  21. ^ "DOSEMU Home". 2007-05-05. Retrieved 2008-07-03.
  22. ^ "DOS Games on Vista". 2008-03-11. Retrieved 2008-09-02.
  23. ^ "Batch File Help". computerhope.com. Retrieved 2008-09-10.
  24. ^ Matczynski, Michael. "ZINGTECH - Guide to the New Game Programmer". Retrieved 2008-09-02.
  25. ^ "The Master Boot Record (MBR) and What it Does". 090912 dewassoc.com
  26. ^ "Reverse-Engineering DOS 1.0 – Part 1: The Boot Sector « pagetable.com". 090912 pagetable.com
  27. ^ "CONFIG.SYS Commands". 090913 academic.evergreen.edu
  28. ^ Kozierok, Charles (2001). "The DOS Boot Process". The PC Guide. Retrieved 2008-09-02.
  29. ^ "misc.txt". 090912 arl.wustl.edu
  30. ^ a b "Drive Letter Assignment and Choosing Primary vs. Logical Partitions". The PC Guide. 2001-04-17. Retrieved 2012-04-04.
  31. ^ "Microsoft Windows MS-DOS Device Name DoS Vulnerability". Retrieved 2008-09-02.
  32. ^ "DOS device names definition". PC Magazine. Retrieved 2008-09-02.
  33. ^ Murdock, Everett. DOS the Easy Way. EasyWay Downloadable Books. pp. 7–12. ISBN 0-923178-02-3.
  34. ^ Murdock, Everett. DOS the Easy Way. EasyWay Downloadable Books. p. 71. ISBN 0-923178-02-3.
  35. ^ Dvorak, John (1991). Dvorak's Guide to DOS and PC Performance. Osborne McGraw-Hill. pp. 442–444. {{cite book}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  36. ^ Darrow, Barbara (1 February 2002). "Whatever Happened To Lotus 1-2-3?". Retrieved 2008-07-12.
Notes

  • IBM Corp., IBM, (January 1984). “IBM DOS Release 2.10 Cloth bound retail hard board box”. 1st edition. IBM Corp. Item Number. 6183946
  • IBM Corp., IBM, (January 1984). “Disk Operating System User's guide (DOS Release 2.10)”. 1st edition. Microsoft Corp. (100 pages including colour illustrations) Item Number. 6183947
  • IBM Corp., IBM, (January 1984). “Disk Operating System Manual (DOS Release 2.10)”. 1st edition. Microsoft Corp. (574 looseleaf pages in 3 ring folder) Item No. 6183940
Retrieved from "https://en.wikipedia.org/w/index.php?title=DOS&oldid=667176953"