Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!beach.cis.ufl.edu!khawkes
From: khawkes@beach.cis.ufl.edu (Kurt Hawkes)
Newsgroups: comp.sys.amiga
Subject: Re: NUISANCE OR PROBLEM?
Message-ID: <20491@uflorida.cis.ufl.EDU>
Date: 20 Jun 89 16:22:01 GMT
References: <89061907384711@masnet.uucp>
Sender: news@uflorida.cis.ufl.EDU
Reply-To: khawkes@beach.cis.ufl.edu ()
Organization: UF CIS Department
Lines: 31

In article <89061907384711@masnet.uucp> rob.sudbury@canremote.uucp (ROB SUDBURY) writes:
>With or without the hard drive or controller hooked up I keep getting
>`pure bit not set' feeds on the CLI startup screen with my
>startup-sequence.  WHY?  Here it is:
> 
[stuff deleted]
>;
>Resident C:Resident pure
>Resident C:Assign pure
>Resident C:MakeDir pure
>Resident CLI L:Shell-Seg SYSTEM pure add
>Resident C:Execute pure
>Resident C:CD pure
>;

In AmigaDos 1.3 there are some new file protection bits.  The one your having
trouble withing is the pure bit.  When you copied the V1.3 commands onto
your disk, you must have used a copy program that does not support the 1.3
file extensions.  What you need to do is:

Protect c:resident p add   ;This will add the pure bit to the resident file.

You need to do that with all the resident commands; Assign, Makedir, etc.
Compair you C: directory with the C: directory on you 1.3 dist disk, using
list.  You will see the files that need pure bit set.  

--
--                           //
Kurt Hawkes                 //      khawkes@beach.cis.ufl.edu
University of Florida   \\ //
                         \X/     Amiga 2000