I've never used DRIVPARM before (never needed it), so have pretty much ignored
it even though I've glanced over references to it before. What Steve said
makes sense, though. Here's what I think is happening (best guess, could be
wrong). The problem is not really DOS, it's the BIOS. Whatever machine he's
running on has such an old BIOS that it doesn't understand 1.44 MB 3.5 in
floppies. DOS normally gets is information about the disks from the BIOS, so
if the BIOS doesn't understand the disk then it won't tell DOS about it. What
appears to be happening is that when DOS asks the BIOS about the disk it
basically says, "There's a disk here but I don't know how it works." so DOS
just gives up and ignores the disk altogether and pretends it isn't even there.
The DRIVPARM in CONFIG.SYS tells MS-DOS to go ahead and use the disk the BIOS
doesn't understand and provides the parameters DOS needs to access the disk
(the parameters that the BIOS should have told it about but couldn't). If
that's the case, this probably needs to be something that happens early on in
CONFIG.SYS processing, before DOS ever tries to access the disk for data. I
don't think it's anything you can do with a TSR or even a CONFIG.SYS device
driver.
____________________________________________________________
We Say Goodbye To Kelly Ripa
risingstarnewspaper.com
http://thirdpartyoffers.juno.com/TGL3141/5b2af74e1e7ae774e225ast01vuc
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
