Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!shelby!portia!dhinds
From: dhinds@portia.Stanford.EDU (David Hinds)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Avoid mangling your hard drive with DMDRVR.BIN
Message-ID: <10343@portia.Stanford.EDU>
Date: 20 Mar 90 05:55:42 GMT
References: <18605@boulder.Colorado.EDU>
Sender: David Hinds <dhinds@portia.stanford.edu>
Organization: Stanford University
Lines: 18

In article <18605@boulder.Colorado.EDU>, scholes@boulder.Colorado.EDU (SCHOLES MARTIN LEE) writes:
> 
>   Dreary-eyed, I just resolved my mega-baked boot drive.  I have a 386 with
> QEMM, and I load a BUNCH of drivers into high memory.  I recently loaded
> the DMDRVR.BIN driver into high memory, and many, many problems came from
> it.  It took me forever to reconstruct my data (English Paper and Programming
> Assignment kinda disappeared), and even longer to diagnose the problem.  The
> moral of the story is to NEVER, under any circumstances load DMDRVR.BIN into
> high ram, leave it in conventional.  I think I have properly diagnosed the
> problem, if anyone disagrees, please let me know.

    That's strange.  I have always loaded DMDRVR.BIN high, and have never
had a problem.  Did you have any other disk-related things loaded up there,
like a cache or FASTOPEN, or some DOS buffers?  Maybe one of your other
drivers randomly trashed some other stuff that was also loaded high.

 -David Hinds
  dhinds@popserver.stanford.edu