3]PROTECTION BITS
There are 8 protection bits that can be used to protect files. 
They are ... 
            H ... (Hidden) Controls the visibility of certain files.
            S ... (Script) Controls starting script files without Execute.
            P ... (Pure) Controls program loading using the resident command.
            A ... (Archived) Controls the option of copying files under 1.3.
            R ... (Read) Allows a file to be read.
            W ... (Write) Allows a file to be written to.
            E ... (Execute) Allows a file to be executed.
            D ... (Delete) Allows a file to be deleted.
E.G. To protect the file called LETTERS, 

Type in the CLI "Protect df0:Letters -d" (without the quotes). 

To restore it to the normal unprotected state.

Type in the CLI "Protect df0:Letters +d"
  
3]DELETING FILES ON DISCS!
One of the quickest ways to delete a lot of files from disks is by opening a
CLI and typing
             
              Dir opt ai

This will list everything individually on the disk.  As each file is listed 
all you need type is "Del" and your file will be deleted as quick as a flash.  
You can also view the file by typing "T" (for type). 
Note: You need to delete everything from the subdirectory before you can 
      delete the root directory.


3]THE CLI COPY COMMAND
The COPY command is one of the most used of all, but quite a few people are 
typing more than they need to. IE, you can copy more than one file at a time. 
So if you're copying a number of CLI commands, for example, to ram: in your 
startup-sequence, you can do the following:
COPY cd|dir|endcli|type ram:c
instead of doing it in 4 separate lines. Note that you need to be in the
directory that you're copying from, ie, you can't do something like
COPY c:cd|c:dir|etc  from another directory.


3]JOYS OF MULTI-TASKING
If you're in the middle of a massive file copy and receive a system message 
saying "Disk Full", pull up another CLI, delete some unwanted files on your 
target disk, and then do a RETRY in the System Message. It will carry on 
quite happily.


3]ASSIGN COMMAND
As you all know (don't you?) you can assign logical volume/device names to 
physical disk drive names such as:
        assign Source: df0:
        assign Destination: DF1:
        diskcopy source: to destination:

Useful?, yes, for some things.

Did you know you can also assign logical volume/device names to 
subdirectories?  Such as:

        assign from: df0:devs/printers
        assign to: ram:
        copy from: to to:

*BUT*  the *FUN* one you may not have noticed is that you can assign
to FILE NAMES (read commands).  For example:

        assign x: c:execute
        assign e: c:ed
        assign cc: df1:c/LC

then use them like:

        x: startup-sequence
        e: my_text_file
        cc: foo -i df1:include

Assigns are SYSTEM WIDE, NOT unique to each window.


3]PROTECT AND HIDE
The PROTECT command can be used to hide files and drawers when using the 
Workbench environment.

To hide a file or drawer
   PROTECT filename.info -r
To show a file or drawer
   PROTECT filename.info -r

Where filename.info is the name of the .info file or drawer you wish to hide


3]1.3 INSTALL COMMAND VIRUS CHECKER
How many people realise that the INSTALL command issued with the 1.3
Workbench is in fact also a BootBlock/Virus checker. To use this handy little
command, simply type

INSTALL DF0: CHECK

The install command will then check the bootblock in DF0: and let you know 
what it finds with a message like:-

Appears to be a normal V1.2/1.3 bootblock
               or
May not be standard V1.2/1.3 bootblock

You can also REMOVE a BootBlock from a disk with the command

INSTALL DF0: NOBOOT


3]TRICKS WITH RENAME 
Say you have double-clicked an icon and it asks for a program off another 
disk, and that this may happen again, as for example a Basic program asking 
for the EXTRAS disk so it can load AmigaBasic. One way to speed things up is
to simply copy Amigabasic to the Ram disk (if you've got a meg of memory or 
more) and then rename the Ram disk to EXTRAS. Saves all that disk-grinding, 
and is speedier too.


3]SETTING THE DATE
If your Amiga lacks a battery backed up clock and you get fed up using
preferences to set the date, try this in your startup sequence ...
DATE
ECHO " "
DATE ?
ECHO " "
This will prompt you to enter the correct time and date and should save a bit
of time.