Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ll-xn!mit-eddie!uw-beaver!microsoft!leefi From: leefi@microsoft.UUCP (Lee Fisher) Newsgroups: comp.sys.ibm.pc Subject: Re: DOS 3.3 feature vaporware? Message-ID: <1387@microsoft.UUCP> Date: 14 Apr 88 07:33:47 GMT References: <3860@cbterra.ATT.COM> Organization: Microsoft Corp., Redmond, WA Lines: 31 Summary: DRIVPARM does not work in MS-DOS v3.30, it does in v3.30A > esd@cbterra.att.com (Eric S. Deese) writes: > > dpz@athos.rutgers.edu (David P. Zimmerman) writes: > > > > I was looking through my MS-DOS 3.30 manual and found a nifty feature > > called "drivparm" that you can stick in your CONFIG.SYS file. > > However, try as I might (and try as another DOS wizard here might), > > all that I can get spit out at boot time is a complaint about > > "drivparm" being an unrecognized command. Anybody get this to work, > > or is this truly nifty feature a truly nifty vapor? > > I have spent several hours with it also, as I thought I might have a > use for it. Like yourself, DOS kept telling me that it didn't like > the drivparm command. I tend to believe that it is "truly nifty vapor. DRIVPARM does not work in MS-DOS v3.30. There is a new release of the MS-DOS v3.30 "packaged product" called v3.30A which has fixed this. It has been sent to manufacturing and will be available soon. OEMs already have this update. If you have an OEM version of DOS, contact them for availability of a fix. If you have the "packaged product" version, call Microsoft at 206-882-8089 and tell them that you have this problem; they'll take your name/address, and send you this update when it becomes available. -Lee ________ 01001100 Lee Fisher, Microsoft Corp., Redmond, WA. 01000101 {uw-beaver,decvax,decwrl,trsvax,sun,attunix,uunet}!microsof!leefi 01000101 leefi@microsof.uucp 01000110 leefi@microsof.beaver.washington.edu 01001001 disclaimer: My opinions are my own, not those of my employer.