

             Why (1.3, 2.x, 3.x in C:)


      NAME
          Why - Used to get additional information about failing
                commands.

      SYNOPSIS
          WHY

      DESCRIPTION
            AmigaDOS has this little command that MSDos and 
        System 7 users can only dream about. MSDos nor System 7 
        gives the user any kind of feedback when a command fails 
        to run. The few messages they do send you are confusing 
        and make sense only to Bill Gates (maybe). When AmigaDOS 
        hits a problem, what happens? You get a nice little 
        requestor telling you what was wrong and probably a 
        suggestion on how to fix it. If you send the Why command 
        right after this happens, you can get additional info on 
        the command failure and more details (in simple English) 
        on what can be done to correct it.
 
            Sometimes, Why will send back a failure code in the 
        form of a number. You can use the Fault command to 
        analyze this number and investigate more fully the fault 
        code.

            If you issue Why after a command that executed 
        successfully (or did the failed command has issued all 
        the information available) you will get the message: "The 
        last command did not set a return code."


    KEYWORDS

            There are no keywords.

    EXAMPLES

            1. What happens when a Why is issued after a RUN 
        command fails to run:

              1> RUN GrooveyGame
                 
              RUN: Can't run GrooveyGame

              1> WHY

              Last command failed because file not found



