Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!asuvax!ncar!boulder!scholes
From: scholes@boulder.Colorado.EDU (SCHOLES MARTIN LEE)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Avoid mangling your hard drive with DMDRVR.BIN
Message-ID: <18696@boulder.Colorado.EDU>
Date: 22 Mar 90 03:39:44 GMT
References: <18605@boulder.Colorado.EDU> <10343@portia.Stanford.EDU> <G0KGPZ@drivax.UUCP>
Sender: news@boulder.Colorado.EDU
Reply-To: scholes@boulder.Colorado.EDU (SCHOLES MARTIN LEE)
Organization: University of Colorado, Boulder
Lines: 15

In article <G0KGPZ@drivax.UUCP> liberato@drivax.UUCP (Jimmy Liberato) writes:
>dhinds@portia.Stanford.EDU (David Hinds) writes:

>Not exactly related to the problem at hand, but what is the advantage of
>using DMDRVR.BIN if, let's say, I DIDN'T need to have patitions > 32 meg?
>I know the low-level format features of Disk Manager are nice so I might
>want to use it for that but then why would I not just use FDISK for the
>partitioning which doesn't need a driver (DMDRVR.BIN) like Disk Manager does?

  I personally prefer not using device drivers for hard drives, because then
when something goes wrong, that's just one more thing you need on the backup
DOS boot disk to get happening.  The answer to your question, at least in my
case, is that I'm running a miniscribe 3085, which has 1170 cylinders.  The
way I understand things, the BIOS allows for a max of 1024 cylinders, so the
driver steps in and does some translations to make it all work out.