Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ur-tut.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!rochester!ur-tut!pier
From: pier@ur-tut.UUCP (Pierre Darmon)
Newsgroups: net.micro.pc
Subject: Re: DOS 3.xx bugs (BACKUP/RESTORE)
Message-ID: <294@ur-tut.UUCP>
Date: Fri, 13-Dec-85 13:38:23 EST
Article-I.D.: ur-tut.294
Posted: Fri Dec 13 13:38:23 1985
Date-Received: Mon, 16-Dec-85 04:16:22 EST
References: <11170@ucbvax.BERKELEY.EDU> <281@ur-tut.UUCP> <885@ecsvax.UUCP> <11208@ucbvax.BERKELEY.EDU>
Reply-To: pier@ur-tut.UUCP (Pierre Darmon)
Distribution: net
Organization: Univ. of Rochester Computing Center
Lines: 28

In article <11208@ucbvax.BERKELEY.EDU> ucbvax!ucbugs!chapman writes:
>In article <885@ecsvax.UUCP> duccpc!bet@ecsvax.UUCP (Bennett E. Todd III) writes:
>>3.00 and 3.10 have broken backup/restore commands. 
>
>I do software development on an AT running 3.10, and had a similar
>problem with backup/restore.  It turned out that the problem wasn't
>with backup/restore at all, but with one of the memory-resident
>programs (in this case, NOKEY) that I was using.  If I boot without
>loading NOKEY, everything works just fine.  I don't know if other
>programs cause this type of behavior or not.  Sidekick doesn't cause
>any problems.
>
>Hopefully helpfully,
>
>Brent Chapman
>ucbvax!ucbugs!chapman

When I was using DOS 3.0, NOKEY did not cause me any problem (I was not using
BACKUP though, but BACKUP had a bug which was fixed in DOS 3.1). When I
upgraded to 3.1, if NOKEY was loaded and if I was trying to access drive a:
(through a DIR command for instance) the drive would start spinning forever.
I could not even reboot. I had to turn the machine (an AT by the way) down.
Removing NOKEY solved the problem.


Pierre Darmon
University of Rochester
{allegra|decvax|seismo}!rochester!ur-tut!pier