Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!decwrl!sgi!omni!bob
From: bob@omni.com (Bob Weissman)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: DRIVPARM: unrecognized command in config.sys
Summary: DRIVPARM is buggy in DOS 3.30; get 3.30A for free from Microsoft
Message-ID: <3095@borabora.omni.com>
Date: 29 Jun 90 21:00:32 GMT
References: <1990Jun27.035428.27845@cunixf.cc.columbia.edu> <198@sc2a.unige.ch>
Organization: OMNI Solutions, Mountain View, CA
Lines: 27

This question should be added to the Frequenly Asked Questions list...

In article <198@sc2a.unige.ch>, fisher@sc2a.unige.ch (Markus Fischer) writes:
> In article <1990Jun27.035428.27845@cunixf.cc.columbia.edu>, ezk@cunixf.cc.columbia.edu (Erez Zadok) writes:
> > ...              I was thinking that the DRIVPARM option of CONFIG.SYS might
> > do it, but when I added the line to my CONFIG.SYS, I got an "unrecognized
> > command in CONFIG.SYS" error(?!)  Has anyone had this problem before?
> 
> Say, are you *sure* that `drivparm' is a DOS 3.30 command ?  My manual doesn't
> list it at all (IBM DOS 3.30), and my on-line help system tells me it's a
> `DOS 4.0 and up' command...

DRIVPARM exists in MS-DOS 3.30, but is buggy.  Fischer's online help
command is wrong.

Call Microsoft at their support line (sorry I don't have it handy)
and explain your problem.  Give them the part number of your original
MS-DOS 3.30 disk and ask for the 3.30A maintenance release.

This release fixes DRIVPARM and several other bugs.  But you have
to have purchased generic MS-DOS for Microsoft to send you a free
upgrade.

-- 
Bob Weissman
Internet:	bob@omni.com
UUCP:		...!{apple,pyramid,sgi,uunet}!omni!bob