A quick puzzle:
When IBM came out with PC-DOS 3.20 (the first version to support 720K
3.5"), it documented DRIVER.SYS, but did not mention DRIVPARM.
MS-DOS did document DRIVPARM.
(NOTE: some OEM versions of 2.11 had direct support of 720K, often INSTEAD
of 360K)
When using MS-DOS on "real" IBM PC, XT, AT, and PS/2, DRIVPARM would
produce "unrecognized command in CONFIG.SYS".
When using PC-DOS on "real" IBM PC, XT, AT, and PS/2, DRIVPARM would
produce "unrecognized command in CONFIG.SYS".
When using PC-DOS on "real" generic clones, DRIVPARM would
work.
When using MS-DOS on "real" generic clones, DRIVPARM would
work.
When I put copies of the IBM BIOS into a generic clone, DRIVPARM would no
longer work.
Although I can't claim that my sample was enough to be truly certain, it
certainly implies that DRIVPARM was incompatible with the IBM BIOS.
The error message that was produced does not seem to be accurate as to
what the problem was.
--
Fred Cisin cisin_at_xenosoft.com
XenoSoft http://www.xenosoft.com
Received on Tue Oct 01 2002 - 15:07:01 BST