home *** CD-ROM | disk | FTP | other *** search
- Commands in this section:
- STATUS
- BREAK
- FAULT
- PROTECT
- VERSION
- WAIT
- WHY
- BINDDRIVERS
- CHANGETASKPRI
- DISKCHANGE
- DISKDOCTOR
- EDIT
- SETDATE
- SETMAP
- ________________________________________________________________________________
-
- STATUS
-
- displays information about the tasks that are currently being performed.
-
- >> STATUS ?
- PROCESS,FULL/S,TCB/S,CLI=ALL/S:
-
- There's another mouthful. "PROCESS" is a task by number. "TCB" gives
- information about the task priorities, stack, and global vector size. "CLI"
- displays the currently loaded programs. /* STATUS alone displays this
- information */. "FULL" gives all the information
-
- >> STATUS
- >> STATUS FULL
-
- ________________________________________________________________________________
-
- BREAK
-
- sets the "attention" flag[s] in a given task.
-
- This is similar to typing <CTRL>C to escape from a task that's being
- run, but you can send a task either <CTRL>C, <CTRL>D, <CTRL>E, or <CTRL>F.
-
- >> BREAK ?
- task/a,all/s,c/s,d/s,e/s,f/s:<RETURN>
- Bad args to BREAK
-
- OK, look at the help line. We have to give BREAK a task number /* can
- be obtained with STATUS */, and the letter for the flag we want to send or all.
-
- Let's set-up a demo situation:
-
- >> NEWCLI
-
- /* take note of the number that's at the prompt. If you've changed it,
- work in the new window and just change the new window's prompt so it gives you
- the current task. /* PROMPT "%N" if you don't remember */. Now in your new
- window, type:
-
- NEWWINDOW_#> TYPE CLI_tutorial.1
- /* and use <SPACE> to stop it from scrolling */
-
- Go to your work CLI and type in:
-
- >> BREAK NEWWINDOW_# C
-
- Go back to NEWWINDOW_# and press <BACK SPACE> to start the scrolling
- again. But now instead of continuing, you get a line:
-
- **BREAK
-
- See how it works? You can perform the same experiment and pass the
- BREAK with the ALL option if you want. If you don't, just:
-
- NEWWINDOW_#> ENDCLI
-
- ________________________________________________________________________________
-
- FAULT
-
- displays error message for the code you supply.
-
- Up to 10 numbers may be supplied.
-
- >> FAULT 218
- Fault 218: device (or volume) not mounted
-
- ________________________________________________________________________________
-
- PROTECT
-
- sets a file's protection status
-
- Although LIST will display "rwed" /* r=read, w=write, e=execute, and
- d=delete */ as the status for a command and changing them with PROTECT will
- make them appear changed, AmigaDOS only pays attention to the "d" flag in the
- current /* 1.2 */ release.
-
- ________________________________________________________________________________
-
- VERSION
-
- displays the version numbers for the kickstart and workbench disks
- the system is currently using.
-
- This is a "file-seperately" command. Use it once, write the results on
- the kickstart and workbench disks you're using, and move this command to an
- area for storing rarely used things...somewhere other than your WB.
-
- >> VERSION
- /* a message with the aforementioned numbers in it */
-
- ________________________________________________________________________________
-
- WAIT
-
- puts everything on hold for a specified period of time.
-
- >> WAIT ?
- ,SEC=SECS/S,MIN=MINS/S,UNTIL/K:
-
- Followed by a number, the current process will wait for that number of
- seconds unless the word MINS is used.
-
- Waiting UNTIL can take quite a while if you don't set your clock on a
- regular basis, but if that's what you want to do, you can:
-
- BS> WAIT UNTIL HH:MM
-
- By itself, WAIT waits 1 second
-
- ________________________________________________________________________________
-
- WHY
-
- gives a brief explanation of why a command failed
-
- This command probably belongs in the same ultimate directory as VERSION.
- But, if a command fails, WHY will, if the command sets a return code, let you
- know what happened. These comments are often cryptic to those who need to use
- this command /* after you've had a few of the same error codes, you'll begin to
- KNOW what happened */ or they simply don't tell you enough. This isn't
- necessarily that the command is written poorly, it's just that it can't do your
- thinking for you.
-
- ________________________________________________________________________________
-
- BINDDRIVERS
-
- binds the device driver for add-on hardware.
-
- I guess I could be wrong, but it seems to me this command is left
- overfrom the 1.1 days, when things wouldn't auto-configure.
- This command would be used in the startup-sequence and, if it finds
- icons for expansion hardware in the sys:expansion directory, will auto-configure
- them.
-
- ________________________________________________________________________________
-
- CHANGETASKPRI
-
- changes the priority of the specified task.
-
- AmigaDOS uses the priority number to determine which task to attend to
- in it's environment. Most tasks have a priority number of 0 and this allows the
- CPU to alternate between tasks. CHANGETASKPRI sets the priority number of your
- CLI to the number you specify, the range is -127 to 127. Tasks begun from this
- CLI will inherit this property.
- It is suggested that you stick within the range of -5 to 5, since
- AmigaDOS will assume you know what you're doing and it's possible to lock
- critical tasks out of the CPU by using the hamfist approach.
-
- ________________________________________________________________________________
-
- DISKCHANGE
-
- informs AmigaDOS that you've changed disks in a 5¼" drive.
-
- If you don't have a 5¼" drive, move this command to external storage, if
- you do have one. You'll need to tell AmigaDOS whenever you change a disk in it
- by:
-
- BS> DISKCHANGE df?:
-
- ________________________________________________________________________________
-
- DISKDOCTOR
-
- attempts to repair a corrupted disk.
-
- If a disk gets corrupted, AmigaDOS will display a requester imforming
- you of the fact and will suggest that you use DISKDOCTOR to repair it.
- Corrupted disks can happen through mechanical damage or sometimes by
- magic(?).
- DISKDOCTOR will attempt to restore as much of the data as it can. After
- DISKDOCTORing a disk, you should copy everything you want off of it and to
- another disk.
- After moving the files to a new disk, you can attempt to salvage the old
- disk by formatting it again to clean it up.
-
- BS> DISKDOCTOR df?:
-
- ________________________________________________________________________________
-
- EDIT
-
- is a line editor, as opposed to ED which if full-screen.
-
- To be honest, I have never had much luck getting it to work. /* I read
- somewhere that Carolyn Scheppner of CATS claims that the only person she knows
- that can use it is Andy Finkel... */ If you want to use it, refer to one of
- your reference manuals for the instructions. There's whole chapters devoted to
- it's use. If you are or become adept at it, let me know and I'll update this
- entry.
-
- ________________________________________________________________________________
-
- SETDATE
-
- changes the date stamp of a file or directory.
-
- AmigaDOS maintains a date stamp that contains the time of creation for
- disks, directories, and files. SETDATE allows you to change this date.
-
- ________________________________________________________________________________
-
- SETMAP
-
- changes the key map that the Amiga uses.
-
- In the devs:keymaps directory are stored various keyboard mapping
- configurations. You can use the SETMAP command to set your keyboard to the key
- maps of different countries. This is handy if you have to do documents in a
- different language.
- Bear in mind that while your screen display will reflect these changes,
- your printer might not. Ofttimes there will be "dip switches" in the printer to
- configure it to different international characters. You'll have to refer to your
- own printer manual to find out how to do this and what the combination of switch
- positions has to be.
-
- ________________________________________________________________________________
- OK! We've finished another one. That pretty well some up the general
- stuff. In the next section, we'll start going over the big guns of the CLI.
-
- You know the routine:
-
- READER CLI_tutorial.5
-