Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!oneb!kmcvay From: kmcvay@oneb.UUCP (Ken McVay) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: DR DOS Summary: Sauce for the goose? Keywords: dos,ibm Message-ID: <171@oneb.UUCP> Date: 3 Feb 91 13:44:24 GMT References: <278ab4b6-2430comp.ibmpc@point.UUCP> <1226@prlhp1.prl.philips.co.uk> Followup-To: comp.sys.ibm.pc.misc Distribution: na Organization: 1B Systems Management Limited Lines: 35 In article medici@dorm.rutgers.edu (Mark Medici) writes: >krause@prlhp1.prl.philips.co.uk (krause) writes: [DR DOS failure described] >I haven't seen that problem, but check out these: [DR DOS failure described] >Granted, I am new with DR-DOS, and haven't spent a great deal of time on it. >However, at this point I would not recommend DR-DOS to anyone who doesn't >have a good chunk of time to baby it. Interesting... I bought DR DOS 5.0 this past summer, because the feature list was impressive, and I needed better security for commercial communications installations. I installed it on an existing MS-DOS 4.01 system (Adaptec SCSI bus, Miniscribe 110mb disk) - the process took about 10 minutes, no data was lost, and it's worked flawlessly since. After playing with it for about a month, I began offering it as the 'first choice' o/s for my commercial sales, and have installed several systems similar to mine with no difficulties either during installation or afterwards. I would like to know more about the systems where serious problems have been encountered - maybe we can figure out what's causing the bumps :-) -- Public Access UUCP/UseNet (Waffle/XENIX 1.63) | kmcvay@oneb.wimsey.bc.ca| TB+: 604-753-9960 2400: 604-754-9964 | ..van-bc!oneb!kmcvay | FrontDoor 2.0/Maximus v1.02/Ufgate 1.03 | FidoNet 1:351/190.1 | HST 14.4: 604-754-2928 | IMEx 89:681/1 |