View Full Version : DRIVEPRAM in config.sys in PCDOS 7

IBM Portable PC
January 25th, 2014, 08:45 PM
Does anyone know who to make DRIVEPRAM work in PCDDOS?

There is a bug that prevents it's from working and a subsequent workaround.

>driveparm=^A^A^A/d:X /c /f:Y
> ^
> /|\ Refer to your DOS manual for the proper values of X and Y.
> |
> |
> +--- insert three control-A characters here. Edlin works best.

“The proper syntax for the undocumented ^A's in the DRIVPARM
command in config.sys for IBM DOS 3.20 and higher is as follows:
(in config.sys)
The control-A must be entered with an editor such as EDLIN that will put
the character ^A in config.sys . A caret followed by an "A" will not work.”

DRIVPARM is undocumented only for PC-DOS. The line you need in
config.sys is this:
Notes: 1) following the = sign, that is a single ^A, Control-A. No
space, or you'll get an "unrecognized command" error.
2) above line assumes B: drive is the 3 1/2"; change /D:1 to /D:0
for A: drive

January 26th, 2014, 09:29 AM
There's no "e" in DRIVPARM.

IBM Portable PC
January 26th, 2014, 01:51 PM
There's no "e" in DRIVPARM.

Interesting that Google returns many pages on DRIVPARM and DRIVEPARM.........

No wonder so many can't get it to work! Personally, I don't believe I used it back in the day, or else it's long forgotten.

January 26th, 2014, 02:08 PM
That's because illiteracy is RAMPANT!

If you can't spell it you certainly can't get it to work. :-)

January 26th, 2014, 03:03 PM
haha, I had the same problems. I'd end up with DRIVEPRAM or DRIVPARAM etc etc.The choosing of which letters to remove didn't follow any logic in my head. If I was doing it, it'd be DRVPRM or DRIVEPRM. It'll be my partner who drives the pram, not my XT.

January 26th, 2014, 04:04 PM
The quoted text was written by me many years ago in my list of undocumented DOS commands (as featured in the November 1996 issue of "DOS World" magazine). The part about putting in Ctrl-As to make the DRIVPARM command work only applies to DOS 3.2x and 3.30. As of MS-DOS 3.30A and IBM DOS 4.00 and higher, DRIVPARM became a fully documented and functional command, without requiring that hack to make it work.

Microsoft even mentions it here:

"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."

Also some OEM versions of MS-DOS 3.2 and 3.3 patched the DRIVPARM command to make it work properly.