Question 1

MS-DOS startup troubleshooting During a DOS boot, which single function key allows you to step through CONFIG.SYS and AUTOEXEC.BAT line-by-line with confirmation for each command?

Accepted Answer

Introduction / Context:When diagnosing startup issues in classic MS-DOS systems, the ability to execute boot files line-by-line is extremely valuable. DOS provides special function keys at boot to bypass or step through CONFIG.SYS and AUTOEXEC.BAT. Knowing the correct key improves troubleshooting speed and safety.Given Data / Assumptions:The environment is MS-DOS (or DOS mode in Windows 9x).CONFIG.SYS and AUTOEXEC.BAT contain device drivers and TSR (terminate-and-stay-resident) utilities.We want to confirm or skip each line interactively.Concept / Approach:At boot, DOS watches for specific keys. F5 bypasses startup files entirely, while F8 triggers step-by-step confirmation. This lets you execute, skip, or modify behavior interactively to isolate failing lines.Step-by-Step Solution:Power on or reboot the PC.When “Starting MS-DOS…” appears, press F8.For each line in CONFIG.SYS, respond Y to execute or N to skip.After CONFIG.SYS completes, DOS repeats the process for AUTOEXEC.BAT.Note which line produces errors to target your fix.Verification / Alternative check:Compare F8 with F5 on the same machine: F5 loads DOS without processing the files, whereas F8 prompts before each line. This validates the step-through functionality of F8.Why Other Options Are Wrong:a: F1 repeats last command in the DOS command processor, not a boot-time step function.b: F3 recalls previous command line in the shell; unrelated to boot stepping.c: F5 bypasses startup files completely; it does not step through them.e: Not applicable because F8 is correct.Common Pitfalls:Pressing the key too late; you must hit F8 when the “Starting MS-DOS…” prompt appears. Also, confusing F5 (bypass) with F8 (step).Final Answer:F8

Question 2

Viewing resident programs in DOS Which single command at the DOS prompt quickly shows memory usage and currently loaded TSRs (Terminate-and-Stay-Resident programs)?

Accepted Answer

Introduction / Context:Terminate-and-Stay-Resident programs (TSRs) and device drivers occupy precious conventional and upper memory in DOS. When applications fail due to low memory or conflicts, technicians inspect memory maps to identify what is loaded and where. DOS provides a built-in diagnostic for this purpose.Given Data / Assumptions:The user is at a DOS prompt.Goal: list memory blocks and identify TSRs/device drivers.Common DOS utilities include MEM and MEMMAKER.Concept / Approach:The MEM utility displays a memory summary. With switches like /C or /D, it lists conventional, upper, and high memory usage along with the modules occupying them. Even without switches, MEM presents useful totals, and technicians often start there before drilling down.Step-by-Step Solution:At the DOS prompt, type MEM and press Enter.Review the memory summary to see free and used regions.For detailed module lists, run MEM /C or MEM /D to display TSRs and device drivers by name and size.Identify large or suspicious TSRs for temporary removal during troubleshooting.Iterate: unload or disable entries, then re-check MEM output.Verification / Alternative check:Cross-check MEM results against CONFIG.SYS and AUTOEXEC.BAT. Each loaded driver or TSR should correspond to an entry, confirming the utility’s accuracy.Why Other Options Are Wrong:a: “Memory” is not a DOS command.c: SYS is used to make a disk bootable; /M is not a standard switch for listing TSRs.d: MEMMAKER optimizes memory usage interactively; it does not simply display current TSRs.e: Not applicable because MEM is correct.Common Pitfalls:Forgetting to use switches (/C or /D) for module listings; misreading UMB versus HMA; assuming MEMMAKER is harmless—always back up before optimization.Final Answer:MEM

Question 3

Memory managers in DOS HIMEM.SYS manages which type of memory resource on DOS-based systems?

Accepted Answer

Introduction / Context:DOS memory is historically segmented into conventional, upper, high, expanded (EMS), and extended (XMS). HIMEM.SYS is a High Memory Manager that enables DOS and applications to utilize memory above the first megabyte via the XMS standard.Given Data / Assumptions:HIMEM.SYS is loaded in CONFIG.SYS.We distinguish extended (XMS) from expanded (EMS).Other drivers like SMARTDRV.SYS (disk cache) depend on XMS availability.Concept / Approach:HIMEM.SYS implements the XMS API, controlling access to extended memory and the High Memory Area (HMA). It allows DOS to move parts of itself “HIGH” (via DOS=HIGH), but the manager itself is responsible for brokering XMS blocks to clients such as disk caches and Windows 3.x.Step-by-Step Solution:Load HIMEM.SYS in CONFIG.SYS to enable XMS services.Enable DOS=HIGH to place DOS kernel in HMA (requires HIMEM.SYS).Optional: load EMM386.EXE to create EMS using XMS and provide UMBs.Applications call XMS functions to allocate extended memory blocks.Verify with MEM to see XMS availability.Verification / Alternative check:Without HIMEM.SYS, commands referencing XMS (for example, SMARTDRV) either fail or run in reduced capability. Adding HIMEM.SYS restores XMS reporting and usage, confirming its role.Why Other Options Are Wrong:a: DOS=HIGH is a CONFIG.SYS directive that leverages HIMEM.SYS; it is not what HIMEM.SYS “controls.”b: RMDRIVE.SYS is unrelated to XMS management.c: SMARTDRV.SYS is a disk cache that consumes XMS; it is not the memory manager.e: Not applicable because Extended Memory is correct.Common Pitfalls:Confusing EMS with XMS; assuming EMM386 replaces HIMEM—EMM386 depends on HIMEM to access XMS.Final Answer:Extended Memory

Question 4

DOS file and directory maintenance Which single DOS command removes a directory and all of its contents (files and subdirectories) in one operation?

Accepted Answer

Introduction / Context:In DOS, deleting a directory tree recursively can be tedious if done file-by-file. DOS introduced a command to remove an entire directory and everything beneath it, simplifying cleanups and uninstalls.Given Data / Assumptions:The target is a directory possibly containing files and subdirectories.User has appropriate permissions and no files are read-only or in use.Standard DOS command set is available (DOS 6.x or similar).Concept / Approach:DELTREE performs recursive deletion from the specified path downward. It prompts for confirmation unless overridden by switches. This is distinct from DEL (which deletes files) and RD (which removes only empty directories).Step-by-Step Solution:At the prompt, type DELTREE path (for example, DELTREE C:\OLDAPP).Confirm the prompt to proceed with recursive removal.Wait for the command to remove files and subdirectories.Verify with DIR that the directory no longer exists.Optionally use switches to suppress prompts in scripts (use with caution).Verification / Alternative check:Attempting RD on a non-empty directory will fail, proving the necessity of a recursive command like DELTREE for bulk removal.Why Other Options Are Wrong:a: DEL . deletes files in the current directory only and not subdirectories.b: RD (RMDIR) removes only empty directories.d: CD changes the current directory; it does not delete anything.e: Not applicable because DELTREE is correct.Common Pitfalls:Accidentally running DELTREE on the wrong path; always double-check the target and ensure backups exist.Final Answer:DELTREE

Question 5

Understanding internal DOS commands Which statement correctly describes internal commands in MS-DOS?

Accepted Answer

Introduction / Context:MS-DOS provides two classes of commands: internal (built into the command interpreter) and external (separate executables). Knowing which are internal helps when booting from minimal media or troubleshooting path and file issues.Given Data / Assumptions:COMMAND.COM is the DOS command interpreter.Internal commands include DIR, COPY, DEL, CD, CLS, and others depending on version.External commands include FORMAT.EXE, DISKCOPY.EXE, and MEM.EXE.Concept / Approach:Internal commands reside in memory as part of COMMAND.COM, so they are available whenever the interpreter is running. They do not require separate files in the path once the shell is loaded.Step-by-Step Solution:Load DOS to a prompt (COMMAND.COM is active).Run an internal command such as DIR without needing an external file.Observe that external commands fail if their .EXE or .COM is missing from the path.Identify internal versus external by consulting documentation or by removing the external file temporarily (not recommended in production).Conclude that internal commands are always available at the prompt.Verification / Alternative check:Boot from a minimal DOS disk containing only system files and COMMAND.COM; internal commands still run, while external ones do not unless their executables are present.Why Other Options Are Wrong:b: Internal commands are for all users, not restricted to programming.c: They can run interactively; batch files are not required.d: The opposite is true—internal commands are embedded within COMMAND.COM.e: Not applicable because option a is correct.Common Pitfalls:Assuming MEM or FORMAT are internal; they are external and require their executables.Final Answer:Internal commands can be run whenever the DOS prompt is displayed

Question 6

Reformatting checks in MS-DOS Which FORMAT option forces DOS to recheck all disk clusters during a reformat, including those previously marked bad?

Accepted Answer

Introduction / Context:Formatting media in DOS can either trust existing bad-cluster maps or retest all clusters. When verifying media health, technicians may force a full recheck to ensure no latent defects are missed.Given Data / Assumptions:We are using the DOS FORMAT utility.Goal: retest clusters, including those previously marked bad.We compare common switches: /B, /S, /8, /C.Concept / Approach:FORMAT /C directs DOS to examine clusters that were previously marked bad and recheck the surface, updating the bad-cluster list as needed. Other switches serve different purposes (system transfer, boot area, legacy geometry).Step-by-Step Solution:Insert the disk and run: FORMAT drive: /CAllow the utility to scan and retest clusters.Review the final summary for total disk space and bad sectors.If errors persist, retire the media from critical use.Optionally combine with other switches (for example, /U for unconditional) when appropriate.Verification / Alternative check:Compare a run with and without /C on media with known bad clusters; /C triggers a recheck and may clear falsely marked clusters or confirm genuine defects.Why Other Options Are Wrong:a: /B reserves space for system files or boot tracks; not a cluster retest directive.b: /S copies system files to make the disk bootable; unrelated to cluster checking.c: /8 formats for 8 sectors per track (legacy); not a testing option.e: Not applicable because /C is correct.Common Pitfalls:Confusing /U (unconditional format) with surface retesting; /U affects UNFORMAT recovery, not the retest behavior itself.Final Answer:FORMAT /C

Question 7

Clearing the DOS screen Which internal DOS command clears the screen and places the command prompt at the upper-left corner?

Accepted Answer

Introduction / Context:Console housekeeping commands improve readability during long troubleshooting sessions. Clearing the display quickly resets the view, aiding focus and reducing confusion from previous output.Given Data / Assumptions:The environment is a DOS command prompt.We want to clear the screen entirely.We prefer a built-in, quick command.Concept / Approach:CLS (clear screen) is an internal DOS command that clears the text display buffer and repositions the cursor at row 1, column 1 (upper-left). It requires no external executable and works immediately at any standard DOS prompt.Step-by-Step Solution:At the prompt, type CLS and press Enter.Observe that prior text disappears; the prompt is at the top-left.Continue with subsequent commands on a clean screen.Use as needed to maintain clarity during diagnostics.Optionally recall previous commands with F3 if needed after clearing.Verification / Alternative check:Run TYPE on a long file, then run CLS; the screen resets. This confirms function without side effects on files or settings.Why Other Options Are Wrong:b: “close” is not a DOS command.c: “quit” is not the DOS command to clear the screen; some programs use it to exit.d: “exit” closes the command interpreter (in some environments) rather than clearing the screen.e: Not applicable because CLS is correct.Common Pitfalls:Expecting CLS to clear scrollback in graphical shells—it only clears the visible console buffer.Final Answer:cls

Question 8

Comparing floppy disks in DOS Which DISKCOMP syntax compares the disk in drive A with the disk in drive B, limiting the comparison to the first side and only the first 8 sectors of each track?

Accepted Answer

Introduction / Context:When verifying floppy disks, DISKCOMP compares two disks sector-by-sector. Technicians may narrow the scope to only the first side and specific sectors to save time or target suspected problem areas.Given Data / Assumptions:Drive A and B are floppy drives.Switch /1 means “compare only side 1” (single-sided comparison).Switch /8 means “compare only the first 8 sectors per track.”Concept / Approach:DISKCOMP syntax accepts drive letters followed by switches. Combining /1 and /8 restricts the comparison, reducing time and head movement while still checking the specified subset.Step-by-Step Solution:Insert source disk in A: and target disk in B:.Run: DISKCOMP A: B: /1 /8Follow prompts to swap disks if you have only one drive.Review the report for any mismatched tracks/sectors.If differences are found, consider a full comparison without limits.Verification / Alternative check:Run DISKCOMP A: B: without switches, then compare runtime and reported coverage; the limited command executes faster and reports only the subset, confirming correct switch interpretation.Why Other Options Are Wrong:a: DISKCOPY copies disks; it does not compare.c: Missing /1; it would compare both sides for the first 8 sectors only.d: Missing /8; it would compare full sectors per track on side 1 only.e: Not applicable because the combined /1/8 syntax is correct.Common Pitfalls:Confusing the numeral “1” with the letter “l” in documentation; ensure you use /1 not /l. Also, ensure disks share the same format.Final Answer:DISKCOMP A: B:/1/8

Question 9

Loading CD-ROM support in DOS In classic DOS setups, where is the device driver for the CD-ROM (for example, OAKCDROM.SYS) typically loaded so that MSCDEX can attach the drive?

Accepted Answer

Introduction / Context:Enabling CD-ROM access in DOS requires a device driver and an extension. The low-level hardware driver is loaded early during boot so that higher-level services can bind to it.Given Data / Assumptions:Hardware driver file such as OAKCDROM.SYS is available.MSCDEX.EXE (CD-ROM Extensions) provides drive letter and file system integration.We are working with DOS 5/6 or Windows 9x DOS mode.Concept / Approach:The device driver must be loaded in CONFIG.SYS using a DEVICE= or DEVICEHIGH= line. Afterward, AUTOEXEC.BAT loads MSCDEX.EXE to assign a drive letter and complete access to ISO 9660 file systems.Step-by-Step Solution:Edit CONFIG.SYS to add: DEVICEHIGH=C:\CDROM\OAKCDROM.SYS /D:MSCD001Edit AUTOEXEC.BAT to add: LH MSCDEX /D:MSCD001 /L:EReboot to load the driver before MSCDEX.Verify the new drive letter appears with DIR E:Optionally load both entries high to conserve conventional memory.Verification / Alternative check:If the driver is missing from CONFIG.SYS, MSCDEX will report no device driver found, confirming that CONFIG.SYS is the correct location for the driver itself.Why Other Options Are Wrong:a: AUTOEXEC.BAT loads MSCDEX.EXE (the extension), not the low-level device driver.b: Control Panel applies to Windows; pure DOS uses text configuration files.c: “Into Upper Memory” describes placement, not the file to edit. DEVICEHIGH in CONFIG.SYS achieves this.e: Not applicable because CONFIG.SYS is correct.Common Pitfalls:Mismatching the /D: identifier between OAKCDROM.SYS and MSCDEX; forgetting to load HIMEM/EMM386 to create UMBs for DEVICEHIGH.Final Answer:CONFIG.SYS

Question 10

Copying a specific file between disks in DOS Which DOS command do you use to transfer a particular named file from one disk to another (for example, from A: to C:)?

Accepted Answer

Introduction / Context:Routine file management in DOS includes copying individual files between drives or directories. Selecting the correct command prevents accidental whole-disk operations and ensures precise control over what is moved.Given Data / Assumptions:We need to copy a specific file (for example, A:\REPORT.TXT) to another location (for example, C:\DOCS).DOS command-line interface is available.User has read permission on source and write permission on destination.Concept / Approach:The COPY command duplicates one or more specified files to a target path, preserving the original. Wildcards are supported, and directory paths can be included. This differs from DISKCOPY, which duplicates entire floppy disks sector-by-sector.Step-by-Step Solution:Insert the source disk into drive A: if applicable.Run: COPY A:\REPORT.TXT C:\DOCSConfirm the “1 file(s) copied” message.Verify by listing the destination: DIR C:\DOCSOptionally use wildcards (for example, COPY A:\*.TXT C:\DOCS)Verification / Alternative check:Attempt DISKCOPY and note it requires identical floppy formats and copies an entire disk; this validates that COPY is the correct command for single-file operations.Why Other Options Are Wrong:b: DISKCOPY clones entire diskettes, not single files.c: TIME sets or displays system time; unrelated to file transfers.d: RENAME changes a file’s name/path; it does not copy.e: Not applicable because COPY is correct.Common Pitfalls:Overwriting existing files without the /-Y prompt; forgetting quotes around paths with spaces in later DOS shells; mixing up source and destination order.Final Answer:COPY

Question 11

DOS Boot Order and Startup Files  On a classic DOS-based PC, which of the following lists shows the correct sequence of system startup batch/configuration files processed during the boot process?

Accepted Answer

Introduction / Context:DOS systems follow a predictable boot sequence that initializes device drivers and sets environment variables before handing control to the command interpreter. Understanding this order helps troubleshoot boot issues and configure memory managers and drivers correctly.Given Data / Assumptions:The machine boots to MS-DOS or DOS-compatible environment.Standard system files are present: IO.SYS (or IBMBIO.COM), MSDOS.SYS (or IBMDOS.COM), CONFIG.SYS, COMMAND.COM, and AUTOEXEC.BAT.No third-party boot managers alter the default flow.Concept / Approach:After the DOS system core is loaded, the operating system processes CONFIG.SYS to load device drivers and configure memory managers. Only after CONFIG.SYS completes does COMMAND.COM start and run AUTOEXEC.BAT to set environment variables, execute TSRs, and run startup utilities.Step-by-Step Solution:Power on → BIOS POST completes.Boot sector loads DOS system files (IO.SYS and MSDOS.SYS).DOS reads and executes directives in CONFIG.SYS (e.g., DEVICE=HIMEM.SYS, DEVICE=EMM386.EXE, FILES=, BUFFERS=).DOS loads COMMAND.COM (the command interpreter).COMMAND.COM automatically runs AUTOEXEC.BAT to configure PATH, PROMPT, mouse/keyboard TSRs, etc.Verification / Alternative check:Rename CONFIG.SYS temporarily and observe that device drivers are not loaded before AUTOEXEC.BAT runs. Conversely, editing CONFIG.SYS changes behavior before AUTOEXEC.BAT executes, confirming the order.Why Other Options Are Wrong:Option A and C contain misspelled or malformed filenames and reverse the proper order.Option D references CONFIG.BAT, which is not a standard DOS configuration file.Option E is wrong because a correct sequence appears in Option B.Common Pitfalls:Confusing AUTOEXEC.BAT (batch file) with CONFIG.SYS (configuration directives).Assuming COMMAND.COM runs before CONFIG.SYS; in reality, COMMAND.COM is loaded after CONFIG.SYS processing.Forgetting that some DOS variants add extra options, but the core order remains.Final Answer:CONFIG.SYS, AUTOEXEC.BAT

Question 12

DOS File Types and Extensions  In MS-DOS, which filename extension specifically identifies batch command files that the command interpreter executes line by line?

Accepted Answer

Introduction / Context:DOS uses filename extensions to distinguish how a file should be handled. Executable programs and batch scripts each have conventional extensions that determine the load and execution method used by COMMAND.COM.Given Data / Assumptions:Standard DOS command interpreter: COMMAND.COM.Common executable-related extensions: COM, EXE, and BAT.System configuration files such as CONFIG.SYS use the SYS extension but are not executed as programs.Concept / Approach:Batch command files are plain text scripts processed by the command interpreter. DOS identifies these by the .BAT extension and executes their commands sequentially. In contrast, .COM and .EXE are binary executables loaded directly into memory and executed by DOS.Step-by-Step Solution:Recognize that batch files are script-like and editable in a text editor.COMMAND.COM searches for executables in the order COM → EXE → BAT unless configured otherwise.Files ending in .BAT are treated as batch scripts and executed line by line.Verification / Alternative check:Create TEST.BAT with a few echo commands and run TEST; DOS will execute the lines, demonstrating batch behavior. Rename it to TEST.COM or TEST.EXE to see the difference; it will not execute as a binary program.Why Other Options Are Wrong:COM and EXE (Options A and C) denote compiled binaries, not command scripts.SYS (Option D) is a system or driver file type and not a batch command file.Common Pitfalls:Assuming .COM contains commands; it actually indicates a compact binary format.Misunderstanding search order and expecting .BAT to run before .COM or .EXE.Final Answer:BAT

Question 13

DOS Drive Letter Assignment  A PC has two IDE hard drives. Each drive has a primary partition and an extended partition. Which drive letter is assigned to the primary partition of the second (slave) drive under standard DOS letter assignment rules?

Accepted Answer

Introduction / Context:DOS assigns drive letters in a fixed order: primary partitions first (starting with C: for the first hard disk), followed by logical drives inside extended partitions, then additional physical disks. Knowing this order is essential for troubleshooting multi-drive systems.Given Data / Assumptions:Two IDE drives with both primary and extended partitions.No removable drives or special device mappings interfere.Default DOS letter assignment behavior is used.Concept / Approach:DOS first assigns C: to the active primary partition of the first hard disk. Next, it assigns letters to any other primary partitions on additional hard disks before moving on to logical drives in extended partitions, in physical disk order.Step-by-Step Solution:Primary partition on Disk 1 → C:.Primary partition on Disk 2 → D: (because primaries are assigned before extended/logical drives).Logical drives inside extended partitions are assigned letters after primaries (e.g., E:, F:, etc.).Verification / Alternative check:Boot a DOS system with two disks and run FDISK or DIR on successive drive letters. You will observe the second disk’s primary partition appears at D: if present.Why Other Options Are Wrong:C (Option A) is already the first disk’s primary.E or F (Options C/D) would be assigned after D: under standard ordering.Option E is incorrect because a standard answer exists.Common Pitfalls:Assuming logical drives come before additional primaries—they do not.Forgetting that some OEM tools or network mappings can alter letters, but not in a default DOS-only setup.Final Answer:D

Question 14

Directory Structures in DOS  When you create a subdirectory within an existing directory, what is this hierarchical arrangement called in DOS terminology?

Accepted Answer

Introduction / Context:Operating systems organize files in hierarchical directory trees. Creating folders inside other folders establishes a parent–child relationship, which has a specific term in file-system vocabulary.Given Data / Assumptions:DOS uses a tree-structured directory model.Commands like MD (or MKDIR) create directories.Subdirectories can be created within other directories to organize data.Concept / Approach:When a directory is placed within another, it is said to be “nested.” This reflects the hierarchical nesting of structures from root (e.g., C:\) down to deeper levels (e.g., C:\DATA\PROJECTS\2025).Step-by-Step Solution:Use MD PARENT to create a parent directory.Use MD PARENT\CHILD to create a subdirectory inside PARENT.This arrangement is called nesting because CHILD is nested within PARENT.Verification / Alternative check:Run TREE or DIR /S to visualize that subfolders are contained under their parent, confirming the nested hierarchy.Why Other Options Are Wrong:Directing, making, and backing (Options A/B/C) are not standard DOS terms describing this hierarchy.“None of the above” is incorrect because “nesting” is the accepted term.Common Pitfalls:Confusing the act (creating a subdirectory) with the term that describes the relationship (nesting).Using flat directory structures that become hard to manage; nesting improves organization when used judiciously.Final Answer:Nesting

Question 15

Executable Search Order in DOS  When you type a command at the DOS prompt without an extension, in what order does COMMAND.COM search for executable files?

Accepted Answer

Introduction / Context:Command resolution is the process the shell uses to find and start the program you request. DOS’s COMMAND.COM follows a consistent search order for extensions when none is specified at the prompt, which affects which file actually runs if multiple variants exist.Given Data / Assumptions:Standard COMMAND.COM behavior.PATH variable may direct the search across directories, but the extension priority stays the same.Files of the same base name may exist with different extensions in the same directory.Concept / Approach:COMMAND.COM first looks for a .COM file, then for a .EXE file, and finally for a .BAT file. This means a tiny .COM utility can shadow an .EXE or .BAT with the same name, leading to different behavior than expected.Step-by-Step Solution:User types FOO at the prompt.COMMAND.COM checks for FOO.COM; if present, it runs.If not found, it checks for FOO.EXE; if present, it runs.If neither is found, it checks for FOO.BAT and runs it if available.Verification / Alternative check:Create FOO.COM, FOO.EXE, and FOO.BAT in the same directory with distinctive output. Typing FOO will execute FOO.COM first, verifying the order COM → EXE → BAT.Why Other Options Are Wrong:Options A, B, and D list orders that contradict DOS’s documented behavior.Option E is incorrect because there is a definitive, standard order.Common Pitfalls:Unexpectedly running a .COM utility when intending to run a .BAT script with the same name.Security implications: placing a rogue .COM earlier in PATH can hijack execution.Final Answer:COM, EXE, BAT

Question 16

DOS Boot Configuration Ordering  At initial power-on, which of the following configuration lines would be executed earlier in the DOS boot sequence (before the others)?

Accepted Answer

Introduction / Context:During DOS boot, CONFIG.SYS directives are processed before AUTOEXEC.BAT commands. Memory managers have a specific load order: the extended memory manager (HIMEM.SYS) must load before the expanded memory manager (EMM386.EXE), and both load before environment settings in AUTOEXEC.BAT (such as PROMPT).Given Data / Assumptions:Standard DOS boot with CONFIG.SYS and AUTOEXEC.BAT.HIMEM.SYS and EMM386.EXE appear as DEVICE= lines in CONFIG.SYS.PROMPT is typically set in AUTOEXEC.BAT.Concept / Approach:The order is: process CONFIG.SYS (DEVICE lines first) → load COMMAND.COM → run AUTOEXEC.BAT (PROMPT and other commands). Within CONFIG.SYS, HIMEM.SYS (XMS manager) must be loaded before EMM386.EXE (EMS / UMB provider) because EMM386 depends on extended memory services.Step-by-Step Solution:CONFIG.SYS begins processing on boot.DEVICE=c:\dos\himem.sys loads first to provide XMS services.DEVICE=c:\emm386.exe may load next to enable EMS/UMBs.After CONFIG.SYS completes, COMMAND.COM runs AUTOEXEC.BAT where PROMPT=pg executes.Verification / Alternative check:Reorder the lines and observe boot errors or warnings: EMM386 often requires HIMEM.SYS already loaded, confirming the precedence.Why Other Options Are Wrong:Option A (EMM386) should not load before HIMEM.SYS.Option C (PROMPT) resides in AUTOEXEC.BAT and runs later.Option D is not a standard DOS directive.Common Pitfalls:Loading EMM386 without HIMEM causes instability or failure.Assuming PROMPT in CONFIG.SYS; it belongs in AUTOEXEC.BAT.Final Answer:Device=c:\dos\himem.sys

Question 17

Checking the DOS Version  While working in MS-DOS, which command displays the operating system version information at the prompt?

Accepted Answer

Introduction / Context:Knowing the DOS version helps determine available features, compatible drivers, and memory managers. DOS provides a simple built-in command to display this information without external utilities.Given Data / Assumptions:User is at a DOS prompt (COMMAND.COM).Standard internal commands are available.Concept / Approach:The internal command VER prints the DOS version string. It is a quick diagnostic tool to confirm which DOS release is running and sometimes reports related shell/version details depending on the implementation.Step-by-Step Solution:At the C:\> prompt, type VER and press Enter.Observe output such as “MS-DOS Version 6.22”.Use this information when selecting compatible software and drivers.Verification / Alternative check:Running HELP or consulting CONFIG.SYS/AUTOEXEC.BAT may also hint at version-specific utilities, but VER is the authoritative quick check.Why Other Options Are Wrong:DATE (Option A) changes/displays the date, not OS version.DISK (Option C) is not a standard DOS command for version display.FORMAT (Option D) prepares media and will not reveal version information.Common Pitfalls:Confusing VER with external tools that may spoof version info; VER is built-in and consistent.Assuming Windows DOS boxes (NTVDM/Command Prompt) show the same as pure MS-DOS; behavior can differ in later Windows.Final Answer:VER command

Question 18

Understanding Disk Fragmentation  Which option best describes a fragmented hard drive in the context of DOS/Windows FAT file systems?

Accepted Answer

Introduction / Context:Fragmentation affects file access speed because files become split across noncontiguous areas of the disk. Understanding what fragmentation is helps users decide when to run defragmentation utilities and diagnose performance problems.Given Data / Assumptions:FAT/FAT32-style file systems allocate files in clusters.As files grow or free space becomes scattered, files can be split.Hardware is otherwise functioning correctly.Concept / Approach:Fragmentation is a logical placement issue, not a physical hardware failure. When a file is not stored in consecutive clusters, the disk head must seek more, increasing access time.Step-by-Step Solution:Consider a file requiring N clusters.If free space is noncontiguous, the file is written in pieces to multiple separated cluster ranges.Future reads require multiple seeks, slowing performance.Verification / Alternative check:Run a defragmenter (e.g., DOS DEFRAG or Windows Defrag) and view the map: fragmented files show as multiple separated blocks. After defragmentation, files appear contiguous and access is faster.Why Other Options Are Wrong:Bad platters (Option A) indicate physical damage, not fragmentation.Corrupted data (Option B) may be a consequence of other issues, not the definition of fragmentation.Damaged clusters (Option C) refers to bad sectors, again a hardware/media integrity issue, not fragmentation.Common Pitfalls:Confusing fragmentation with disk errors; fragmentation is resolved by defragmenting, not by low-level repair.Believing SSDs need the same defrag treatment; SSDs handle fragmentation differently, and defragging can be counterproductive.Final Answer:Files are not stored in consecutive clusters

Question 19

Printing from DOS to the Standard Printer Device  Which DOS command correctly redirects the contents of REPORT.TXT to the standard printing device (PRN/LPT1)?

Accepted Answer

Introduction / Context:DOS supports device names such as PRN, LPT1, and CON. Redirection and piping allow sending command output to devices or files. Printing from the command line without a dedicated print utility is often accomplished using redirection.Given Data / Assumptions:REPORT.TXT exists in the current directory or PATH.PRN (or LPT1) is properly mapped to a working printer.The TYPE command outputs file contents to standard output (the screen) by default.Concept / Approach:Redirection operator ">" sends standard output to a file or device. Thus, "TYPE filename > PRN" directs text output to the printer device instead of the console, effectively printing the file.Step-by-Step Solution:Use TYPE REPORT.TXT to confirm it displays on screen.Add redirection: TYPE REPORT.TXT > PRN.The printer receives the text stream and begins printing.Verification / Alternative check:Replace PRN with LPT1 if needed: TYPE REPORT.TXT > LPT1. If printing fails, verify printer setup or try PRINT command where available.Why Other Options Are Wrong:Option A uses non-DOS syntax.Options C and D misuse the pipe operator “|”, which connects programs via standard input/output, not directly to device names in this context.Option E is incorrect because Option B is valid and standard.Common Pitfalls:Using pipe instead of redirection for devices that are not programs.Forgetting carriage control characters; plain text prints straightforwardly but large files may need pagination.Final Answer:TYPE REPORT.TXT > PRN

Question 20

Loading Device Drivers in DOS  If you need to load the MOUSE.SYS device driver (a system driver variant for mouse support), in which DOS startup file should you place the directive?

Accepted Answer

Introduction / Context:DOS distinguishes between device drivers loaded during CONFIG.SYS processing and terminate-and-stay-resident (TSR) programs often started from AUTOEXEC.BAT. Knowing where to place each component ensures the driver is available early and consumes the correct type of memory.Given Data / Assumptions:MOUSE.SYS is a device-driver style mouse driver (as opposed to MOUSE.COM which is a TSR).Standard DOS boot with CONFIG.SYS and AUTOEXEC.BAT.Goal: ensure mouse services are initialized before user programs run.Concept / Approach:System (SYS) device drivers must be declared in CONFIG.SYS using DEVICE= or DEVICEHIGH=. This causes DOS to load the driver as part of system initialization, before COMMAND.COM runs AUTOEXEC.BAT. TSR-style drivers (e.g., MOUSE.COM) typically go in AUTOEXEC.BAT instead.Step-by-Step Solution:Edit CONFIG.SYS.Add a line: DEVICE=C:\MOUSE\MOUSE.SYS (path as appropriate).Optionally use DEVICEHIGH= to place the driver in upper memory if available.Reboot to activate the driver before running applications.Verification / Alternative check:After reboot, DOS mouse-aware programs should detect the driver. If using MOUSE.COM instead, placing it in AUTOEXEC.BAT will also provide mouse support but later in the boot process.Why Other Options Are Wrong:AUTOEXEC.BAT (Option B) is for TSRs and commands, not SYS device declarations.WIN.INI (Option C) is a Windows configuration file, not DOS boot-level.IO.SYS and MSDOS.SYS (Options D/E) are core system files, not user-edited loader scripts for third-party drivers.Common Pitfalls:Confusing MOUSE.SYS with MOUSE.COM and placing the wrong one in the wrong file.Loading many drivers low and running out of conventional memory; use DEVICEHIGH when appropriate.Final Answer:CONFIG.SYS

Disk Operating System (DOS) Questions

Questions

Practice smarter