KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q60091: Using 720K or 1.44 MB 3.5-Inch Disk Drive with MS-DOS

Article: Q60091
Product(s): Microsoft Disk Operating System
Version(s): MS-DOS:3.x,4.x,5.0
Operating System(s): 
Keyword(s): 
Last Modified: 17-DEC-2000

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft MS-DOS operating system versions 3.1, 3.2, 3.21, 3.3, 3.3a, 4.0, 4.01, 5.0 
-------------------------------------------------------------------------------

SUMMARY
=======

Many users wish to install 3.5-inch floppy disk drives in their systems.
Currently, there are two popular varieties of the 3.5-inch floppy disk drive.
MS-DOS Version 3.30 supports the 720K and 1.44 MB 3.5-inch floppy disk drives.
Listed below are some general guidelines to remember when selecting a 3.5-inch
floppy disk drive.

MORE INFORMATION
================

The disk controller for your computer must support the type of floppy disk drive
you want to install.

The ROM BIOS also needs to support the floppy disk drive. Many of the ROM BIOS
versions available today DO NOT support the 1.44 MB floppy disk drives. (This is
because the 1.44 MB floppy disk drive was first introduced by IBM on their PS/2
systems, and the ROM BIOS of IBM's PC/AT systems do NOT support 1.44 MB floppy
disk drives.) More versions of the ROM BIOS do support the 720K floppy disk
drive. Check with the original equipment manufacturer (OEM) of your computer to
find out what version of the ROM BIOS is required to support a 1.44 MB or 720 MB
3.5-inch floppy disk drive.

With an AT system, a setup program is run to tell the ROM BIOS what types of
floppy disk drives are hooked up. If the setup program supports the floppy disk
drive, the DRIVPARM command (or the DRIVER.SYS command) is not necessary. This
is the preferred way to install the floppy disk drive.

If the floppy disk drive is being installed on an XT system, or if the drive type
is not supported under the AT setup program, you must use either the DRIVPARM or
DRIVER.SYS command. Under MS-DOS Version 3.30, the DRIVPARM command is not
functional, and therefore, the DRIVER.SYS command must be used. An update to
MS-DOS Version 3.30a is available that allows the use of the DRIVPARM command.

The following are some examples of using DRIVPARM and DRIVER.SYS:

  DRIVPARM=/d:01 /f:02           ; For a 720K floppy disk drive on B:
  DRIVPARM=/d:01 /f:07           ; For a 1.44K floppy disk drive on B:
  DEVICE=DRIVER.SYS /d:01 /f:02  ; For a 720K floppy disk drive on B:
  DEVICE=DRIVER.SYS /d:01 /f:07  ; For a 1.44K floppy disk drive on B:

The DRIVER.SYS device driver creates an external reference to the floppy disk
drive if it is configured correctly. DO NOT REFERENCE Drive B; otherwise, the
floppy disk drive will be installed incorrectly. If you have a hard disk Drive C
and you set up DRIVER.SYS, it will create a reference of D: to the 1.44 MB disk
in Drive B. Use Drive D to access the 1.44 MB floppy disk drive.

Additional query words: 3.20 3.21 3.30 3.30a 4.00 4.01 noupd

======================================================================
Keywords          :  
Technology        : kbMSDOSSearch kbMSDOS321 kbMSDOS400 kbMSDOS320 kbMSDOS330a kbMSDOS310 kbMSDOS500 kbMSDOS330 kbMSDOS401
Version           : MS-DOS:3.x,4.x,5.0

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.