Q: Modem control with AT commands: Which command from the standard Hayes “AT command set” resets the modem to its default configuration?

Introduction / Context: Hayes-compatible modems use a standardized “AT” command set for dialing, configuration, and diagnostics. A reset command is frequently needed to clear prior settings and return the modem to a known good state before establishing a connection. Given Data / Assumptions: You have a Hayes-compatible modem. You want to reset the modem via serial commands. Basic control signals (e.g., DTR) and terms (e.g., DCE) may appear as distractors. Concept / Approach: “ATZ” resets the modem to stored default settings (often profile 0) and clears active configurations. Other commands: “ATD” dials, “ATH” hangs up, “ATI” queries identification, “AT&F” loads factory defaults, and “AT&F” differs from “ATZ” by sourcing defaults from factory rather than stored profile. “DTR” is a hardware control line; “DCE” denotes the modem device type. Step-by-Step Solution: Identify the desired action: reset to defaults.Recall: “ATZ” performs a soft reset using stored profile.Choose ATZ as the correct modem command. Verification / Alternative check: Sending “ATZ” in a terminal emulator typically returns “OK,” after which querying “ATI” or “AT&V” shows a default profile. Why Other Options Are Wrong: ATR: not a standard reset command. DTR: a signal line, not an AT command. DCE: device role term, not a command. None: incorrect because ATZ is valid. Common Pitfalls: Confusing “ATZ” with “AT&F”; both reset, but from different default sources (stored vs factory). Final Answer: ATZ

Q: AUTOEXEC.BAT control: Which command can you place in AUTOEXEC.BAT to make the batch file pause and wait for a key press before continuing execution?

Introduction / Context: Batch files in DOS execute sequentially. Sometimes you need to halt processing to read messages or confirm settings before proceeding. DOS provides a built-in command to wait for user input in batch scripts such as AUTOEXEC.BAT. Given Data / Assumptions: You are editing AUTOEXEC.BAT or another .BAT file. You want a simple, built-in way to pause execution. No external utilities should be required. Concept / Approach: The PAUSE command displays “Press any key to continue . . .” and waits for a key press. It is an internal command (part of COMMAND.COM). There is no native HALT or WAIT command in classic DOS that accepts seconds; timing delays typically require external tools (e.g., CHOICE with /T in later DOS/Windows) or looping tricks. Step-by-Step Solution: Identify the need: stop, display a prompt, continue when user is ready.Recall the correct internal command: PAUSE.Insert PAUSE in the desired location in AUTOEXEC.BAT. Verification / Alternative check: Run the batch file and observe that execution stops with the standard prompt until a key is pressed. Why Other Options Are Wrong: HALT / WAIT x.xx seconds / WAIT until Files="x": not standard DOS batch commands. None of the above: incorrect because PAUSE exists and is intended for this use. Common Pitfalls: Expecting a built-in timed delay; forgetting PAUSE pauses indefinitely until keypress. Final Answer: PAUSE

Q: DOS filename extensions: Which extension commonly indicates that a file is a backup copy created by an application or utility?

Introduction / Context: Many DOS and Windows utilities create backup copies of files before overwriting or updating them. Recognizing standard backup extensions helps you restore previous versions and manage files safely during maintenance tasks. Given Data / Assumptions: Legacy and many modern tools save backups in the same directory. Extensions vary by tool, but .BAK has long been a convention. We differentiate .BAK from other common extensions. Concept / Approach: The .BAK extension is traditionally used for backup copies of configuration files, documents, and program data. Other extensions here serve different purposes: .BAS indicates a BASIC source file, .COM is a binary executable (command file), and .TXT is a plain text file. While tools may also use .OLD, .TMP, or timestamped names, .BAK remains a widely recognized backup convention. Step-by-Step Solution: Identify the question’s cue: “backup copy.”Match to the conventional extension: .BAK.Select BAK as the correct answer. Verification / Alternative check: Inspect directories after running editors or setup utilities; backup artifacts commonly appear with .BAK or .OLD. Why Other Options Are Wrong: BAS: BASIC source code. COM: executable command file. TXT: plain text, not specifically backup. None: incorrect since .BAK is standard. Common Pitfalls: Assuming backups always use the same extension—tools vary; forgetting to check timestamps or original filenames when restoring. Final Answer: BAK

Q: Understanding the MS-DOS COPY command: What can the COPY command accomplish in standard DOS usage?

Introduction / Context: The MS-DOS COPY command is a versatile tool for file operations. While DISKCOPY clones entire disks, COPY focuses on files and can operate across drives, directories, and even concatenate files. Understanding these capabilities prevents misuse and streamlines maintenance tasks. Given Data / Assumptions: You are moving or duplicating files, not entire disk images. Both source and destination paths can reference different drives (e.g., A: to B:). Concatenation uses the “+” operator in COPY. Concept / Approach: COPY supports copying from one drive to another (e.g., COPY A:FILE.TXT B:), copying multiple files (wildcards), and concatenating files (e.g., COPY FILE1+FILE2 OUTPUT.TXT). It cannot create a sector-by-sector disk copy—that is DISKCOPY’s job—but it can certainly copy files between floppy disks if drives and paths are specified correctly. Step-by-Step Solution: Confirm that file-level copying is required (vs disk cloning).Recognize COPY can target another drive letter for cross-disk transfers.Remember concatenation syntax: COPY file1+file2 newfile.All listed actions are supported by COPY, so choose “All of the above.” Verification / Alternative check: Test with simple text files and different drives; observe successful copies and concatenations. Use DIR to verify results. Why Other Options Are Wrong: Each single option is incomplete; COPY indeed supports all listed operations. “None” is incorrect. Common Pitfalls: Confusing COPY with DISKCOPY; forgetting to quote or escape special characters in filenames where required; overwriting files unintentionally without /-Y prompts in later variants. Final Answer: All of the above

Q: FORMAT command parameters: In MS-DOS, which parameter lets you specify the target disk's capacity explicitly when formatting (for example, 1.44 MB on a 3.5-inch floppy)?

Introduction / Context: The FORMAT utility prepares a disk for use by creating the file system structures. Several switches allow the user to tailor capacity and labeling, especially when formatting floppy disks of varying sizes or densities. Given Data / Assumptions: You are formatting removable media such as a floppy disk. You want to specify an overall capacity (e.g., 1.44M, 720K). Alternative switches set low-level geometry details or volume labels. Concept / Approach: FORMAT /F:size sets the capacity directly (e.g., /F:1440 or /F:1.44) depending on DOS version syntax. /N and /T specify sectors-per-track and number of tracks (low-level geometry). /V assigns a volume label. Therefore, if the goal is to declare the disk size in one parameter, /F is appropriate. Step-by-Step Solution: Identify the goal: specify capacity succinctly.Match goal to parameter: use /F:size.Avoid geometry-specific switches unless needed; /N and /T are more granular. Verification / Alternative check: Run “FORMAT /?” to view supported parameters for your DOS version; observe examples showing /F values for common capacities. Why Other Options Are Wrong: /N, /T: control sectors/track and tracks; they do not directly express total capacity. /V: only sets volume label. None: incorrect because /F exists for capacity selection. Common Pitfalls: Using /N and /T without matching media; mis-typing size units in older DOS variants; accidentally formatting the wrong drive letter. Final Answer: FORMAT /F:size

Q: Device drivers in CONFIG.SYS: What operation does the HIMEM.SYS driver perform in DOS/Windows 9x environments?

Introduction / Context: Legacy DOS systems load device drivers via CONFIG.SYS to extend capabilities. HIMEM.SYS is a well-known driver that enables the system to address memory above 1 MB using the CPU’s protected-mode features exposed through XMS (Extended Memory Specification). Given Data / Assumptions: You are configuring memory management in DOS/Windows 9x. HIMEM.SYS is referenced in CONFIG.SYS (e.g., DEVICE=HIMEM.SYS). You need extended (XMS), not expanded (EMS) memory services. Concept / Approach: HIMEM.SYS is the XMS manager. It provides access to extended memory and the High Memory Area (HMA), enabling loading portions of DOS and drivers high to free conventional memory. EMS (expanded memory) is managed by EMM386.EXE, a different component that uses paging to simulate EMS on 80386+ CPUs. ANSI terminal emulation is handled by ANSI.SYS; code page switching by DISPLAY.SYS/KEYB and related utilities. Step-by-Step Solution: Distinguish memory types: XMS (extended) vs EMS (expanded).Associate HIMEM.SYS with XMS management and HMA usage.Select “Manages the use of extended memory.” Verification / Alternative check: Use MEM /C or diagnostic tools to confirm XMS availability after loading HIMEM.SYS; observe that EMS requires EMM386.EXE. Why Other Options Are Wrong: ANSI emulation: ANSI.SYS does this. Expanded memory on 80386: handled by EMM386.EXE, not HIMEM.SYS. Code page switching: handled by DISPLAY.SYS/KEYB. Common Pitfalls: Confusing extended and expanded memory; forgetting that both HIMEM.SYS and EMM386.EXE may be used together for different purposes. Final Answer: Manages the use of extended memory

Question 1

MS-DOS command types: In DOS, which category describes commands that are stored as individual program files on disk (for example, on the hard drive or a DOS diskette), and are loaded by the command interpreter only when invoked?

Accepted Answer

Introduction / Context: Classic MS-DOS provides two broad categories of commands: internal commands that reside within COMMAND.COM, and external commands that are stored as separate executable files (such as .COM or .EXE) on disk. This question checks your ability to distinguish how DOS provides functionality and how the command interpreter locates it. Given Data / Assumptions: DOS uses COMMAND.COM as the default command interpreter. Some commands are available immediately after boot (internal), while others are loaded from disk when used (external). Examples help clarify the classification. Concept / Approach: Internal commands (for example, DIR, COPY, DEL in many DOS versions) are built into COMMAND.COM and need no separate disk files. External commands are separate programs (for example, FORMAT.EXE, CHKDSK.EXE, XCOPY.EXE) that DOS loads into memory on demand. If the file is not on the current drive/path, the command will not run. Step-by-Step Solution: Identify the definition asked: commands “kept as separate files on the hard disk.”Recall: external commands are stored as .COM/.EXE files, independent of COMMAND.COM.Conclude: the correct term is “External.” Verification / Alternative check: Type HELP or look for a command’s corresponding .EXE/.COM on disk. If present and removable from PATH, the command is external; if removing it breaks the command, it confirms the classification. Why Other Options Are Wrong: Internal: embedded in COMMAND.COM, not separate files. Change/File: not standard DOS command categories. None of the above: incorrect because “External” is the accepted term. Common Pitfalls: Assuming every frequently used command is internal; confusing availability with classification; forgetting that different DOS versions may classify a few commands differently. Final Answer: External

Question 2

MS-DOS DIR formatting: Which switch causes the DIR command to display the directory listing in wide format (multiple filenames per line)?

Accepted Answer

Introduction / Context: The DIR command in MS-DOS lists files and directories. Its behavior is modified by switches that control sorting, pagination, and layout. Understanding these switches is essential for efficient command-line navigation and file management. Given Data / Assumptions: You are using the classic MS-DOS DIR command. You need the “wide” layout that prints several names per line. Other common switches may appear similar but do different things. Concept / Approach: DIR /W switches the output to wide format, suppressing file details and showing multiple columns of filenames. In contrast, /P pauses each screenful, /O sorts according to a specified order (e.g., /O:N by name), and /B uses bare format (names only, one per line). Step-by-Step Solution: Recall each DIR switch’s purpose: /W = wide, /P = pause, /O = order, /B = bare.Match the requirement “wide format” to the correct switch.Select /W as the correct answer. Verification / Alternative check: Run “DIR /W” and compare to “DIR /B” and “DIR /P” to observe differences in width, pagination, and verbosity. Why Other Options Are Wrong: /O: sorting, not formatting width. /P: pagination only. /B: bare format prints a single name per line, not wide columns. None of the above: incorrect, since /W is valid. Common Pitfalls: Confusing /B’s “bare” with “wide,” and assuming sorting switches impact layout; mixing pagination with formatting needs. Final Answer: /W

Question 3

COMMAND.COM search order: After checking the current directory for a requested command, where does DOS search next to locate an executable?

Accepted Answer

Introduction / Context: When you type a command in DOS, the command interpreter (COMMAND.COM) follows a defined search order to find the executable. Knowing how PATH works is crucial for troubleshooting “Bad command or file name” errors and organizing tools across directories. Given Data / Assumptions: You invoke a command that is not internal to COMMAND.COM. The current directory does not contain the executable. System environment variables (especially PATH) may be set. Concept / Approach: After checking for an internal command or a program in the current directory, DOS consults the PATH environment variable. PATH lists directories to search (in order) for .COM, .EXE, and .BAT files. CONFIG.SYS and AUTOEXEC.BAT are configuration/startup files, not places to search; they may define PATH but are not searched per-command. Step-by-Step Solution: Identify that the command is not in the current directory.Recall the next step: search the directories listed in PATH.Therefore, “The PATH statement” is the correct answer. Verification / Alternative check: Use the SET command to view PATH; temporarily remove a directory from PATH and observe that commands in that directory become unavailable unless referenced with a full path. Why Other Options Are Wrong: C:\DOS\UTILITIES: might be a directory in PATH but is not universally searched unless in PATH. Config.sys / Autoexec.bat: not part of per-command search; they simply set environment. Common Pitfalls: Assuming DOS searches the entire drive automatically; relying on full paths for every command instead of maintaining PATH correctly. Final Answer: The PATH statement

Question 4

MS-DOS redirection with SORT: To sort a file's contents in ascending order and write the sorted result to the screen, which form correctly feeds the file to the SORT command?

Accepted Answer

Introduction / Context: DOS commands often use redirection to supply input or capture output. The SORT utility reads lines from standard input and writes sorted lines to standard output by default (ascending order). Choosing the correct redirection operator is essential for the desired behavior. Given Data / Assumptions: You have a text file to be sorted in ascending order. You want SORT to read from the file without changing the file name or creating a new file. Default SORT direction is ascending unless otherwise specified by switches. Concept / Approach: Input redirection in DOS uses the less-than symbol. “SORT < filename” sends the file's content to SORT via standard input. “SORT filename” treats “filename” as a literal string input on some DOS variants or may be rejected; the canonical method is input redirection. “SORT > filename” writes output to a file but does not feed input. Pipes “|” connect outputs to inputs of programs, not files directly. Step-by-Step Solution: Identify the tool behavior: SORT reads from stdin, writes to stdout.Apply input redirection: use “<” to feed the file's contents to stdin.Choose “SORT < filename” as correct. Verification / Alternative check: Run “TYPE filename | SORT” to confirm equivalent behavior. Compare with “SORT > out.txt” which captures output but still requires input via stdin. Why Other Options Are Wrong: SORT filename: not the canonical usage for DOS SORT input. SORT > filename: redirects output only. SORT | filename: invalid piping to a file; pipes connect program to program. Common Pitfalls: Confusing input and output redirection; forgetting that SORT consumes stdin by default; overwriting files unintentionally with output redirection. Final Answer: SORT < filename

Question 5

Modem control with AT commands: Which command from the standard Hayes “AT command set” resets the modem to its default configuration?

Accepted Answer

Introduction / Context: Hayes-compatible modems use a standardized “AT” command set for dialing, configuration, and diagnostics. A reset command is frequently needed to clear prior settings and return the modem to a known good state before establishing a connection. Given Data / Assumptions: You have a Hayes-compatible modem. You want to reset the modem via serial commands. Basic control signals (e.g., DTR) and terms (e.g., DCE) may appear as distractors. Concept / Approach: “ATZ” resets the modem to stored default settings (often profile 0) and clears active configurations. Other commands: “ATD” dials, “ATH” hangs up, “ATI” queries identification, “AT&F” loads factory defaults, and “AT&F” differs from “ATZ” by sourcing defaults from factory rather than stored profile. “DTR” is a hardware control line; “DCE” denotes the modem device type. Step-by-Step Solution: Identify the desired action: reset to defaults.Recall: “ATZ” performs a soft reset using stored profile.Choose ATZ as the correct modem command. Verification / Alternative check: Sending “ATZ” in a terminal emulator typically returns “OK,” after which querying “ATI” or “AT&V” shows a default profile. Why Other Options Are Wrong: ATR: not a standard reset command. DTR: a signal line, not an AT command. DCE: device role term, not a command. None: incorrect because ATZ is valid. Common Pitfalls: Confusing “ATZ” with “AT&F”; both reset, but from different default sources (stored vs factory). Final Answer: ATZ

Question 6

AUTOEXEC.BAT control: Which command can you place in AUTOEXEC.BAT to make the batch file pause and wait for a key press before continuing execution?

Accepted Answer

Introduction / Context: Batch files in DOS execute sequentially. Sometimes you need to halt processing to read messages or confirm settings before proceeding. DOS provides a built-in command to wait for user input in batch scripts such as AUTOEXEC.BAT. Given Data / Assumptions: You are editing AUTOEXEC.BAT or another .BAT file. You want a simple, built-in way to pause execution. No external utilities should be required. Concept / Approach: The PAUSE command displays “Press any key to continue . . .” and waits for a key press. It is an internal command (part of COMMAND.COM). There is no native HALT or WAIT command in classic DOS that accepts seconds; timing delays typically require external tools (e.g., CHOICE with /T in later DOS/Windows) or looping tricks. Step-by-Step Solution: Identify the need: stop, display a prompt, continue when user is ready.Recall the correct internal command: PAUSE.Insert PAUSE in the desired location in AUTOEXEC.BAT. Verification / Alternative check: Run the batch file and observe that execution stops with the standard prompt until a key is pressed. Why Other Options Are Wrong: HALT / WAIT x.xx seconds / WAIT until Files="x": not standard DOS batch commands. None of the above: incorrect because PAUSE exists and is intended for this use. Common Pitfalls: Expecting a built-in timed delay; forgetting PAUSE pauses indefinitely until keypress. Final Answer: PAUSE

Question 7

DOS filename extensions: Which extension commonly indicates that a file is a backup copy created by an application or utility?

Accepted Answer

Introduction / Context: Many DOS and Windows utilities create backup copies of files before overwriting or updating them. Recognizing standard backup extensions helps you restore previous versions and manage files safely during maintenance tasks. Given Data / Assumptions: Legacy and many modern tools save backups in the same directory. Extensions vary by tool, but .BAK has long been a convention. We differentiate .BAK from other common extensions. Concept / Approach: The .BAK extension is traditionally used for backup copies of configuration files, documents, and program data. Other extensions here serve different purposes: .BAS indicates a BASIC source file, .COM is a binary executable (command file), and .TXT is a plain text file. While tools may also use .OLD, .TMP, or timestamped names, .BAK remains a widely recognized backup convention. Step-by-Step Solution: Identify the question’s cue: “backup copy.”Match to the conventional extension: .BAK.Select BAK as the correct answer. Verification / Alternative check: Inspect directories after running editors or setup utilities; backup artifacts commonly appear with .BAK or .OLD. Why Other Options Are Wrong: BAS: BASIC source code. COM: executable command file. TXT: plain text, not specifically backup. None: incorrect since .BAK is standard. Common Pitfalls: Assuming backups always use the same extension—tools vary; forgetting to check timestamps or original filenames when restoring. Final Answer: BAK

Question 8

Understanding the MS-DOS COPY command: What can the COPY command accomplish in standard DOS usage?

Accepted Answer

Introduction / Context: The MS-DOS COPY command is a versatile tool for file operations. While DISKCOPY clones entire disks, COPY focuses on files and can operate across drives, directories, and even concatenate files. Understanding these capabilities prevents misuse and streamlines maintenance tasks. Given Data / Assumptions: You are moving or duplicating files, not entire disk images. Both source and destination paths can reference different drives (e.g., A: to B:). Concatenation uses the “+” operator in COPY. Concept / Approach: COPY supports copying from one drive to another (e.g., COPY A:FILE.TXT B:), copying multiple files (wildcards), and concatenating files (e.g., COPY FILE1+FILE2 OUTPUT.TXT). It cannot create a sector-by-sector disk copy—that is DISKCOPY’s job—but it can certainly copy files between floppy disks if drives and paths are specified correctly. Step-by-Step Solution: Confirm that file-level copying is required (vs disk cloning).Recognize COPY can target another drive letter for cross-disk transfers.Remember concatenation syntax: COPY file1+file2 newfile.All listed actions are supported by COPY, so choose “All of the above.” Verification / Alternative check: Test with simple text files and different drives; observe successful copies and concatenations. Use DIR to verify results. Why Other Options Are Wrong: Each single option is incomplete; COPY indeed supports all listed operations. “None” is incorrect. Common Pitfalls: Confusing COPY with DISKCOPY; forgetting to quote or escape special characters in filenames where required; overwriting files unintentionally without /-Y prompts in later variants. Final Answer: All of the above

Question 9

FORMAT command parameters: In MS-DOS, which parameter lets you specify the target disk's capacity explicitly when formatting (for example, 1.44 MB on a 3.5-inch floppy)?

Accepted Answer

Introduction / Context: The FORMAT utility prepares a disk for use by creating the file system structures. Several switches allow the user to tailor capacity and labeling, especially when formatting floppy disks of varying sizes or densities. Given Data / Assumptions: You are formatting removable media such as a floppy disk. You want to specify an overall capacity (e.g., 1.44M, 720K). Alternative switches set low-level geometry details or volume labels. Concept / Approach: FORMAT /F:size sets the capacity directly (e.g., /F:1440 or /F:1.44) depending on DOS version syntax. /N and /T specify sectors-per-track and number of tracks (low-level geometry). /V assigns a volume label. Therefore, if the goal is to declare the disk size in one parameter, /F is appropriate. Step-by-Step Solution: Identify the goal: specify capacity succinctly.Match goal to parameter: use /F:size.Avoid geometry-specific switches unless needed; /N and /T are more granular. Verification / Alternative check: Run “FORMAT /?” to view supported parameters for your DOS version; observe examples showing /F values for common capacities. Why Other Options Are Wrong: /N, /T: control sectors/track and tracks; they do not directly express total capacity. /V: only sets volume label. None: incorrect because /F exists for capacity selection. Common Pitfalls: Using /N and /T without matching media; mis-typing size units in older DOS variants; accidentally formatting the wrong drive letter. Final Answer: FORMAT /F:size

Question 10

Device drivers in CONFIG.SYS: What operation does the HIMEM.SYS driver perform in DOS/Windows 9x environments?

Accepted Answer

Introduction / Context: Legacy DOS systems load device drivers via CONFIG.SYS to extend capabilities. HIMEM.SYS is a well-known driver that enables the system to address memory above 1 MB using the CPU’s protected-mode features exposed through XMS (Extended Memory Specification). Given Data / Assumptions: You are configuring memory management in DOS/Windows 9x. HIMEM.SYS is referenced in CONFIG.SYS (e.g., DEVICE=HIMEM.SYS). You need extended (XMS), not expanded (EMS) memory services. Concept / Approach: HIMEM.SYS is the XMS manager. It provides access to extended memory and the High Memory Area (HMA), enabling loading portions of DOS and drivers high to free conventional memory. EMS (expanded memory) is managed by EMM386.EXE, a different component that uses paging to simulate EMS on 80386+ CPUs. ANSI terminal emulation is handled by ANSI.SYS; code page switching by DISPLAY.SYS/KEYB and related utilities. Step-by-Step Solution: Distinguish memory types: XMS (extended) vs EMS (expanded).Associate HIMEM.SYS with XMS management and HMA usage.Select “Manages the use of extended memory.” Verification / Alternative check: Use MEM /C or diagnostic tools to confirm XMS availability after loading HIMEM.SYS; observe that EMS requires EMM386.EXE. Why Other Options Are Wrong: ANSI emulation: ANSI.SYS does this. Expanded memory on 80386: handled by EMM386.EXE, not HIMEM.SYS. Code page switching: handled by DISPLAY.SYS/KEYB. Common Pitfalls: Confusing extended and expanded memory; forgetting that both HIMEM.SYS and EMM386.EXE may be used together for different purposes. Final Answer: Manages the use of extended memory

Question 11

MS-DOS utilities — understanding FDISK:  What does the FDISK command in DOS actually do to a hard drive before formatting and installing an operating system?

Accepted Answer

Introduction / Context: Before a hard disk can be formatted and used by MS-DOS or Windows 9x era systems, it must be divided into logical sections called partitions. The classic DOS tool for this job is FDISK. Understanding what FDISK does (and does not do) is essential for vintage system setup and exam preparation. Given Data / Assumptions: We are working in a DOS environment or DOS-mode utility set. The disk has not yet been partitioned or its partitions must be redefined. Subsequent steps like formatting occur after partitioning. Concept / Approach: Disk preparation traditionally occurs in stages: partitioning, formatting, and then installing the file system and OS. FDISK performs the partitioning stage by creating, deleting, and setting active partitions (primary, extended, logical). Formatting (FORMAT) comes afterward to create file system structures in the chosen partition(s). Step-by-Step Solution: Identify the action needed: define how the disk space is divided into one or more partitions.Select the tool: FDISK is the standard DOS utility for creating/deleting partitions and setting the active one.Acknowledge the sequence: after FDISK, reboot if prompted, then run FORMAT on each partition.Conclude that FDISK's role is partitioning, not formatting or repairing. Verification / Alternative check: Historical DOS manuals list FDISK options such as Create DOS partition, Set active partition, and Delete partition. None of these options perform low-level format or cluster repair, confirming the specific purpose. Why Other Options Are Wrong: Fixes erroneous hard drive: repair utilities are separate (e.g., SCANDISK/CHKDSK). Formats data sectors: FORMAT performs this, not FDISK. Checks for lost clusters: SCANDISK/CHKDSK handle file system issues, not FDISK. None of the above: incorrect because partitioning is exactly FDISK's job. Common Pitfalls: Confusing partitioning with formatting; skipping a reboot after FDISK; forgetting to set the active partition, which prevents booting. Final Answer: Partitions the hard drive for use

Question 12

MS-DOS RESTORE utility — restoring only files changed since the last backup:  Which RESTORE command switch restores from drive A only those files that have been modified since the most recent backup?

Accepted Answer

Introduction / Context: DOS backup/restore workflows rely on switches to control what gets restored. Efficient incremental recovery uses a switch that returns only files changed since the last backup. Knowing these switches speeds up recovery and reduces wear on legacy media. Given Data / Assumptions: The source media is drive A (typically a floppy disk). We want to restore files modified since the last backup, not every file. We are using the classic RESTORE command syntax. Concept / Approach: Different RESTORE switches target different behaviors. The key is recognizing that /M stands for “Modified since last backup”. Other switches (like /S for subdirectories, /N or /L) do not express this incremental-restore requirement. Step-by-Step Solution: Understand requirement: restore only changed files.Map requirement to switch meanings: /M equals Modified since last backup.Construct valid command: RESTORE A: . /M to target all files by pattern and filter on modification status.Confirm no other switch matches this behavior. Verification / Alternative check: Contemporary DOS references document /M as “restores files modified since the last backup.” This aligns with incremental strategies common in tape and floppy workflows. Why Other Options Are Wrong: /S: includes subdirectories, not modification-based selection. /N: typically relates to prompting or new files behavior depending on DOS version; not the modified-only filter. /L: used for logging or listing in some variants, not modification filtering. None of the above: incorrect because /M is correct. Common Pitfalls: Confusing backup switches between BACKUP and RESTORE; forgetting wildcard patterns; mixing up /S with selective criteria. Always confirm syntax for your DOS version. Final Answer: RESTORE A: . /M

Question 13

DOS memory managers — enabling Upper Memory Blocks (UMBs):  Which CONFIG.SYS directive allows device drivers and TSR programs to be loaded into Upper Memory Blocks (so they can later be placed there using DEVICEHIGH or LOADHIGH)?

Accepted Answer

Introduction / Context: Conventional memory (first 640 KB) is precious in DOS. To free more conventional memory, we load eligible drivers and TSRs into Upper Memory Blocks (UMBs) in the upper memory area. This requires both enabling UMBs and then placing programs there with the right commands. Given Data / Assumptions: We are editing CONFIG.SYS and AUTOEXEC.BAT in a DOS environment. We want the system to allow usage of UMBs. We will subsequently use DEVICEHIGH and/or LOADHIGH to place items into UMB. Concept / Approach: The enabling step is DOS=UMB in CONFIG.SYS (with HIMEM.SYS and an upper memory manager such as EMM386.EXE /UMB). After UMBs are enabled, DEVICEHIGH= loads device drivers high, and LOADHIGH (or LH) loads TSRs high. Without DOS=UMB, attempts to use DEVICEHIGH/LOADHIGH may not allocate into UMBs. Step-by-Step Solution: Enable memory management: load HIMEM.SYS, then EMM386.EXE /UMB (where applicable).Activate UMBs: add DOS=UMB to CONFIG.SYS so DOS manages and exposes UMBs.Place components high: use DEVICEHIGH=driver.sys in CONFIG.SYS and LOADHIGH prog.exe in AUTOEXEC.BAT.Verify with MEM /C /P to confirm programs are resident in upper memory. Verification / Alternative check: Classic DOS optimization guides show that the trio HIMEM.SYS, EMM386.EXE /UMB, and DOS=UMB enable UMB usage; only then do DEVICEHIGH and LOADHIGH accomplish loading high. Why Other Options Are Wrong: DOS=HIGH: moves DOS kernel into the HMA, not UMB enabling. DEVICEHIGH and LOADHIGH: these perform the loading but require UMBs to be enabled first; they do not themselves enable UMBs. None of the above: incorrect because DOS=UMB is correct. Common Pitfalls: Using LOADHIGH without first enabling UMBs; forgetting EMM386.EXE /UMB; confusing HMA (via DOS=HIGH) with UMBs. Always confirm memory map with MEM or MSD. Final Answer: DOS=UMB

Question 14

DOS filename extensions — executable identification:  Which filename extension is used by DOS to identify executable program files?

Accepted Answer

Introduction / Context: DOS recognizes programs by their filename extensions. Knowing which extensions are executable helps when launching software, diagnosing path issues, and writing batch files. Given Data / Assumptions: DOS executes files whose extensions are in the PATHEXT-like behavior for the era: COM, EXE, and BAT. Question asks for the extension that identifies an executable program. We assume default DOS behavior without shell replacements. Concept / Approach: In DOS, commands can be internal (within COMMAND.COM) or external (COM, EXE, BAT). Among the listed extensions, EXE is the standard portable executable format for DOS programs, alongside COM (simpler binary) and BAT (batch scripts). SYS files are typically drivers or configuration components, not directly executed via the shell like standard applications. Step-by-Step Solution: Identify known executable extensions: COM, EXE, BAT.Compare against options: only EXE appears in the list.Confirm that EXE files are directly runnable from the DOS prompt.Select EXE as the correct answer. Verification / Alternative check: DOS manuals note search order when you enter a command name: internal commands first, then look for .COM, .EXE, and .BAT files in that order on the current directory and PATH. Why Other Options Are Wrong: INF: informational files; not executable. PRO: not a standard DOS executable extension. SYS: device drivers or system settings; typically loaded by CONFIG.SYS. None of the above: incorrect because EXE is correct. Common Pitfalls: Forgetting that .COM is also executable; however, since it is not listed, EXE is the best answer given. Confusing .SYS driver loading with normal program execution. Final Answer: EXE

Question 15

Sorting text in DOS — reversing alphabetical order:  Which DOS command line correctly sorts the contents of a file in reverse order and sends the result to the screen (or can be redirected)?

Accepted Answer

Introduction / Context: The DOS SORT filter reads from standard input and writes sorted text to standard output. Mastering its switches lets you quickly reorder data without external tools. Reversing the sort requires a specific flag. Given Data / Assumptions: The input is a text file, referenced via standard input redirection. We want reverse (descending) sort order. We are using the native DOS SORT options. Concept / Approach: By default, SORT sorts ascending. The /R switch reverses the sort order. DOS typically uses redirection (<) to feed a file into SORT. Therefore, the correct pattern is SORT /R < filename. You can also redirect output to a new file with > out.txt if needed. Step-by-Step Solution: Choose SORT as the filter tool.Apply reverse order switch: /R.Use input redirection: < filename.Optionally redirect output to a file with > newfile. Verification / Alternative check: Typing SORT /? in DOS lists switches; /R is documented as reverse sort order. Test with a small file to observe reversed output. Why Other Options Are Wrong: SORT > filename: attempts to write SORT's output but provides no input; it does not reverse order. SORT < filename: correct for ascending, but not reverse. SORT /V: not a standard reverse-order switch in DOS SORT. None of the above: incorrect because a correct solution exists. Common Pitfalls: Forgetting redirection, assuming SORT takes the filename as a direct argument in all DOS versions; omitting /R and wondering why the order is ascending. Final Answer: SORT /R < filename

Question 16

DOS command interpreter — which file executes user commands?  Identify the DOS system file that functions as the command interpreter (shell) responsible for executing commands typed at the prompt and running batch files.

Accepted Answer

Introduction / Context: Classic DOS relies on a command interpreter to process internal commands and dispatch external programs. Knowing the role of each system file helps in troubleshooting boot problems and customizing startup behavior. Given Data / Assumptions: We are discussing MS-DOS/PC-DOS era systems. System files include IO.SYS (or IBMBIO.COM), MSDOS.SYS (or IBMDOS.COM), and COMMAND.COM. The question asks specifically for the component that executes commands. Concept / Approach: COMMAND.COM is the DOS shell. It implements internal commands (DIR, COPY, DEL, etc.), parses the command line, sets up environment variables, and launches external .COM/.EXE/.BAT files. CONFIG.SYS configures drivers and settings at boot; MSDOS.SYS is part of the DOS kernel; SYSTEM.INI is a Windows 3.x/9x configuration file, not a DOS shell. Step-by-Step Solution: Identify the shell: COMMAND.COM.Differentiate kernel files (IO.SYS/MSDOS.SYS) and configuration files (CONFIG.SYS) from the shell.Confirm COMMAND.COM handles the prompt and batch execution.Select COMMAND.COM as the correct answer. Verification / Alternative check: Typing VER or internal commands without any external programs loaded demonstrates the presence of COMMAND.COM. If missing or corrupted, DOS typically fails to provide a command prompt. Why Other Options Are Wrong: MS-DOS.SYS: part of the DOS kernel, not the interpreter. CONFIG.SYS: boot-time configuration file, not an executable shell. SYSTEM.INI: Windows configuration file; irrelevant to DOS command execution. None of the above: incorrect because COMMAND.COM is correct. Common Pitfalls: Confusing CONFIG.SYS device directives with command execution; assuming Windows COMMAND.COM behavior is identical to NT's CMD.EXE. Final Answer: COMMAND.COM

Question 17

Printer redirection in DOS:  Which DOS command is used to redirect devices (for example, assigning a serial port to act as a printer port or changing display/print modes)?

Accepted Answer

Introduction / Context: Legacy DOS environments often needed device redirection—for instance, routing LPT output through a serial port or adjusting communications parameters. The system utility that configures such device modes and mappings is crucial for compatibility with older printers and terminals. Given Data / Assumptions: We aim to redirect printer output or change port settings. We are using native DOS commands, not network client tools. We may need to set baud rate, parity, or map LPT to COM. Concept / Approach: MODE is the DOS command that sets device modes and can redirect printer output (e.g., MODE LPT1:=COM1:) and adjust serial parameters (MODE COM1:9600,N,8,1). PRINT is a spooling utility; TYPE displays file contents; CAPTURE is a Novell NetWare utility, not a standard DOS command. Step-by-Step Solution: Identify need: reconfigure ports or redirect printing.Use MODE to assign LPT to COM or set serial parameters.Optionally combine with PRINT for spooling after redirection is configured.Confirm with a test print to verify mapping. Verification / Alternative check: Running MODE without arguments lists current settings; documentation shows syntax for device mapping and serial configuration. Why Other Options Are Wrong: TYPE: outputs file text to screen; doesn't redirect printers. CAPTURE: NetWare client tool, not core DOS. PRINT: queues files to a printer but doesn't perform device remapping. None of the above: incorrect since MODE is correct. Common Pitfalls: Assuming PRINT can change ports; it relies on existing device mappings. Forgetting to specify both direction and colon notation (e.g., LPT1:=COM1:). Final Answer: MODE

Question 18

Recovering deleted files in DOS — previewing what can be restored:  Which MS-DOS UNDELETE command option displays a list of deleted files that DOS is capable of restoring before you perform the actual undelete?

Accepted Answer

Introduction / Context: In classic DOS, accidental deletions could sometimes be reversed using UNDELETE, provided directory entries were still available. Safely previewing recoverable files helps avoid mistakes and confirms what will be restored. Given Data / Assumptions: We are operating in a DOS environment that supports UNDELETE (e.g., DOS 5/6 or MS-DOS with supplemental tools). We want a list of files that can be undeleted before taking action. Directory entries have not been overwritten. Concept / Approach: The option /LIST instructs UNDELETE to show candidates for recovery. Other options perform undeletes automatically or prompt per file. Using /LIST is a safe first step, akin to a dry run. Step-by-Step Solution: Run UNDELETE with /LIST to enumerate recoverable files.Review names and paths to confirm selection.If satisfied, rerun UNDELETE with appropriate options to restore.Avoid writing new files before recovery to prevent overwriting directory entries. Verification / Alternative check: Help screens (UNDELETE /?) show /LIST as a non-destructive listing mode in several DOS versions and add-on utilities. Why Other Options Are Wrong: UNDELETE .: attempts actual recovery across matches; no preview list. UNDELETE /ALL: restores everything it can without selective review. UNDELETE (no switch): usually interactive but not strictly a listing-only mode. None of the above: incorrect because /LIST exists for this purpose. Common Pitfalls: Continuing to use the disk after deletion (overwrites metadata); assuming long file names are supported in pure DOS UNDELETE; forgetting that recovery success depends on directory entry preservation. Final Answer: UNDELETE /LIST

Question 19

Copying text files from a floppy — correct DOS syntax:  Which command copies all files with the .TXT extension from drive A to the current directory on the currently logged drive?

Accepted Answer

Introduction / Context: Copying groups of files in DOS relies on wildcard patterns and correct source/destination ordering. A common task is moving all text files from a floppy disk (drive A) to the current working directory on the hard disk. Given Data / Assumptions: Source is drive A (floppy). We want to copy every file with extension TXT. Destination is the current directory (no explicit path provided). Concept / Approach: DOS COPY syntax is COPY source destination. When the destination is omitted, COPY assumes the current directory on the current drive. To match all text files on A:, combine the drive specifier and wildcard: A:.TXT. Case is not significant in DOS file systems. Step-by-Step Solution: Specify the correct source: A:.TXT to target all text files on the floppy.Provide destination: omit to default to current directory, or explicitly use ..Run the command: COPY A:.TXTVerify copies with DIR to confirm successful transfer. Verification / Alternative check: Test by creating sample files on A: and executing the command; observe that all matching files appear in the current directory. DOS usage guides show identical syntax examples. Why Other Options Are Wrong: COPY *.TXT A:: reverses source and destination; would copy from current directory to A: instead. COPY .TXT C:: copies to C:, not to the current directory unless that is C: and current path matches; also source would be current drive, not A:. COPY .TXT ALL.TXT: concatenates or overwrites into a single file named ALL.TXT, not a multi-file copy from A:. None of the above: incorrect because COPY A:.TXT is valid. Common Pitfalls: Leaving out the drive specifier (which changes the source); forgetting wildcard behavior; unintentionally overwriting files with the same names in the destination. Final Answer: COPY A:.TXT

Question 20

Concatenating files with DOS COPY — creating a new file:  Which DOS command correctly combines FILE1 and FILE2 into a brand-new file named FILE3 (without altering the originals)?

Accepted Answer

Introduction / Context: Older DOS workflows often required concatenating text or binary segments into a single file. The COPY command can join files using the plus sign, provided the syntax is correct and you understand implications for text versus binary data. Given Data / Assumptions: We have two source files: FILE1 and FILE2. We want to create a new file named FILE3 that contains the contents of FILE1 followed by FILE2. We do not want to modify the original files. Concept / Approach: The DOS COPY concatenation syntax is COPY fileA+fileB destination. This writes the combined stream into the destination file. For text files, ensure proper end-of-file markers and line endings. For binary files, be cautious: concatenation is meaningful only when specific formats support it. Step-by-Step Solution: Identify correct concatenation form: COPY FILE1+FILE2 FILE3.Run the command in the desired directory or include paths.Verify that FILE3 exists and includes both file contents sequentially.Keep originals intact, as COPY reads without altering FILE1 or FILE2. Verification / Alternative check: Using TYPE FILE3 for text files will show the merged content. The DOS help for COPY demonstrates the plus syntax for joining files just as shown. Why Other Options Are Wrong: COPY FILE3 FILE1+FILE2: reverses operands; COPY expects sources before destination. COPY FILE1+FILE2+FILE3: missing destination; this would attempt to copy into the current directory and may be invalid or misinterpreted. COPY FILE2 FILE1+FILE3: mixes source and destination incorrectly. None of the above: incorrect because (b) is exactly right. Common Pitfalls: Concatenating binary files without understanding format; forgetting that COPY may add end-of-file characters for text in some DOS versions; overwriting an existing FILE3 unintentionally. Final Answer: COPY FILE1+FILE2 FILE3

Disk Operating System (DOS) Questions