Search results
Results from the WOW.Com Content Network
SetVer is a TSR program designed to return a different value to the version of DOS that is running. This allows programs that look for a specific version of DOS to run under a different DOS. The command is available in MS-DOS versions 5 and later. [1]
In MS-DOS, a batch file can be started from the command-line interface by typing its name, followed by any required parameters and pressing the ↵ Enter key. When DOS loads, the file AUTOEXEC.BAT, when present, is automatically executed, so any commands that need to be run to set up the DOS environment may be placed in this file.
MS-DOS / PC DOS and some related disk operating systems use the files mentioned here. System Files: [1] IO.SYS (or IBMBIO.COM): This contains the system initialization code and builtin device drivers; MSDOS.SYS (or IBMDOS.COM): This contains the DOS kernel. Command-line interpreter (Shell): COMMAND.COM: This is the command interpreter.
AUTOEXEC.BAT is a system file that was originally on DOS-type operating systems.It is a plain-text batch file in the root directory of the boot device.The name of the file is an abbreviation of "automatic execution", which describes its function in automatically executing commands on system startup; the filename was coined in response to the 8.3 filename limitations of the FAT file system family.
COMMAND.COM is the default command-line interpreter for MS-DOS, Windows 95, Windows 98 and Windows Me.In the case of DOS, it is the default user interface as well. [2] It has an additional role as the usual first program run after boot (init process), hence being responsible for setting up the system by running the AUTOEXEC.BAT configuration file, and being the ancestor of all processes.
The CONFIG.SYS directives also set up the memory managers in the system. After processing the CONFIG.SYS file, DOS proceeds to load and execute the command shell specified in the SHELL line of CONFIG.SYS, or COMMAND.COM if there is no such line. The command shell in turn is responsible for processing the AUTOEXEC.BAT file.
This could run many DOS and variously Win32, OS/2 1.x and POSIX command-line utilities in the same command-line session, allowing piping between commands. The user interface, and the icon up to Windows 2000, followed the native MS-DOS interface. The Command Prompt introduced with Windows NT is not actually MS-DOS, but shares some commands with ...
The COMMAND.COM file is copied to the ram disk during boot and the COMSPEC environment variable is set to the new location on the ram disk. This way the boot disk can be removed without the need to reinsert it after a big application has been stopped. The command line interpreter will be reloaded from the ram disk instead of the boot disk.