1) Have you installed Csound5?

  2) Are you environment variables set up correctly?

     A good way to check is to open up a DOS prompt.  cd to some directory other
     than the Csound5 bin directory.  Run the command "csound".  If that fails,
     then your environment variables need to be set properly.

     Right-click on "My Computer", select "Properties".  Switch to "Advanced" tab.
     Click "Environment Variables" button.  Look for "PATH" and check to see if
     your Csound5 bin directory has been appended to it.  Look for "OPCODEDIR" or
     "OPCODEDIR64", depending on which version of Csound5 you installed.  If they
     are not present, then add them.

     When modifying the "PATH" environment variable, it's a good idea to modify
     the user variable rather than the system variable.  

  3) If you installed the 32bit version of csound~, then you must have 32bit Csound5 installed
     in order for csound~ to run.  The same goes for 64bit csound~ and 64bit Csound5.  
  
     Consult the installation instructions for tips on which Csound5 installers to use.

  csound~ cannot run Csound4.  Max is loading Matt Ingalls' csound~ rather than
  my csound~.mxo.  To fix this problem, remove Matt Ingalls' csound~ object from
  the externals directory.  If it's not there, then it is somewhere else within Max's search path.

  Search all directories within Max's search path (including ones that you have added
  via the Options->File Preferences... menu item).  Remove any files named "csound~".

  1) If you're using an absolute pathname in the "csound" message, then you have 
     made a mistake.  Correct the pathname.

  2) If you're using relative pathnames in the "csound" message, and the relative
     pathname is correct, then the directory that contains your patch is within
     Max's search path.  
    
     Move the directory containing your patch to another location outside Max's
     search path, or use absolute pathnames in your "csound" message.

  This problem is usually caused by dll files not being found.

  1) Make sure the version of csound~ you are using is compatible with the version of
     Csound5 that is installed.  See the installation instructions for details.

  2) Navigate to your Csound\bin\ directory and look for csound32.dll.5.1 or
     csound64.dll.5.1.  If you're using 32bit csound~, then csound32.dll.5.1
     should be there.  If you're using 64bit csound~, then csound64.dll.5.1
     should be there.

  If csound~ has been successfully loaded, but crashes when you send start/bang to
  begin the performance, check to see if csound~.mxo or csound~.mxe is in the same
  directory as your patch and csd/orc file.  If so, remove it and try again.

  This is caused by the denormals problem usually associated with Intel CPU's.  When numbers
  get really small, Intel CPU's tend to "spike".  This usually happens when you're using opcodes
  that implement feedback (filters, reverb, flange, etc...).

  Typically, you'll start out by feeding these opcodes with zeros (which are not denormals).
  Then you'll feed them some nice chunky numbers (still not denormals).  Then you stop feeding
  them chunky numbers, but the feedback loops within the opcodes continually generate smaller
  and smaller numbers until they become denormals.  This is when the CPU starts to "spike".

  Quick solution: use the denorm opcode before any opcodes that implement feedback loops.
  denorm will mix very small numbers into your audio data to keep numbers from becoming
  denormals.  Once should be enough if you have several offending opcodes chained together.

  This problem has been fixed; please download and install v1.0.1 again, or upgrade to a
  later version.  

  This has been a problem for MaxMSP 4.5 users on PPC architecture.  I think I've solved
  the problem.  Please download and install v1.0.1 again (or upgrade to a later version).

  If you still have the same problem, navigate to /Library/Frameworks.  MaxAPI.framework and
  MaxAudioAPI.framework should be there.  If not, they can be found in the 4.5.5 SDK.

  This is not a fatal error; just click "OK" to continue working.  If you want to get rid
  of this error message, download and install Python v2.4.