Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!snorkelwacker!apple!amdahl!drivax!liberato From: liberato@drivax.UUCP (Jimmy Liberato) Newsgroups: comp.sys.ibm.pc Subject: Re: Avoid mangling your hard drive with DMDRVR.BIN Message-ID: Date: 21 Mar 90 21:22:51 GMT References: <18605@boulder.Colorado.EDU> <10343@portia.Stanford.EDU> Reply-To: liberato@drivax.UUCP (Jimmy Liberato) Organization: Digital Research, Inc., Monterey, California Lines: 16 dhinds@portia.Stanford.EDU (David Hinds) writes: >In article <18605@boulder.Colorado.EDU>, scholes@boulder.Colorado.EDU (SCHOLES MARTIN LEE) writes: >> ... >> 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.... 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?