Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!helios.ee.lbl.gov!nosc!cod!baird
From: baird@cod.NOSC.MIL (John M. Baird)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Does DRIVPARM actually work?
Message-ID: <1715@cod.NOSC.MIL>
Date: 4 Dec 89 16:22:28 GMT
References: <18968@watdragon.waterloo.edu>
Distribution: na
Organization: Naval Ocean Systems Center, San Diego
Lines: 31

From article <18968@watdragon.waterloo.edu>, by thfisher@lion.waterloo.edu (Terry Fisher):
> I have been trying to get the DRIVPARM command to make a clone recognise
> the 3.5" drive as 720K.  I keep getting an error message about an
> unrecognized command in config.sys.  Does this command work, or am I
> doing something wrong.
Depending on the supplier and the version of DOS, it should work. See the
attached comments from HELPSB.

John Baird, Naval Ocean Systems Center, San Diego, CA USA
---------
Under Microsoft's version of DOS 3.3 and later (and most OEM's):
DRIVPARM= /D:n [/T:t] [/S:s] [/H:h] [/F:f] [/N] [/C]

Each DRIVPARM line configures a device on your computer and tells DOS to
assign a unique drive name (letter) to it. Diskette drive names will follow
the "standard" A: and B: (if present). Hard drive names will follow C: (and
any other drive names assigned to partitions on the drive C: occupies). 

Under IBM's version of DOS 3.3 and later (and a few OEM's):
DEVICE=[d:][pathname]DRIVER.SYS /D:n [/T:t] [/S:s] [/H:h] [/F:f] [/N] [/C]

Each DEVICE line installs a device driver for a disk on your computer and
assigns a unique drive letter to the disk. The assigned drive name will
follow C: (and any other drive letters assigned to partitions on the drive C:
occupies). 

Also a hint for those systems apparently without DRIVPARM:
	DRIVPARM lines	if available on your system. [Actually, most DOS 3.3
			and later systems have it, though some don't document
			it. To use it on those systems, try putting a Ctrl-A 
			character between the DRIVPARM= and the first option.]