Rasmus wrote on 7/22/99:

>The directories are not regardless, or at least you can't be
>when playing with them. Csound finds files 
>- from a full path, if you give that. 
>- in the directory of the Csound binary
>- in the dir defined by SFDIR/SSDIR/SADIR, depending on what
> the file is to be used for. For input soundfiles SSDIR takes 
>priority, else SFDIR is used.

>What warnings/messages do you get? - does it not find the
>file, or does it find the file faulty or what - you gotta be
>very specific here.

Csound gives the following message:

"cannot open FILENAME.  Not in current dir, SSDIR, or SFDIR as defined"

This, however, is not true.  I can put the target file in any of these
three directories, or specify the full path, and the message remains the
same.
I have also tried running a batch file to refresh the environment
variables right before running Csound.
Also, to eliminate the possibility that the error is caused by a mismatch
between the header type and the .wav extension produced by my sound
editing software (Software Audio Workshop, special edition), I also tried
using .wav files generated by Csound itself -- still no change.
In any case, this problem is only a minor irritation, since everything
else in v3.52 works just fine and keeps me very busy.

Rasmus also wrote:

>Oh, and do get the latest binary from Bath; 3.52 is good 
>enough, but the present one (3.56) is probably even better.

I downloaded Winsound 3.57 on 8/5/99, right before my subscription to my
ISP expired, but it  won't launch correctly.  It skips the main dialog
box, and jumps directly to the "Press OK to exit" box, which normally
appears after rendering.  Is anyone else having this problem?

Kurt

BTW Thank you to everyone for your warm welcome.

___________________________________________________________________
Get the Internet just the way you want it.
Free software, free e-mail, and free Internet access for a month!