Thanks for the explanations for the different files, I feel wiser now ;-)
Only one thing remains unclear as of now:

2007/11/2, Victor Lazzarini <Victor.Lazzarini@nuim.ie>:
> csnd.dll is all the interfaces code that the
> python module uses. I suppose it can go where
> you keep your csound binary or anywhere else
> in your path that is not in the way.
>
but you said earlier (2007/10/30):
"""
> The problem is that there is a file called csnd.dll in the directory,
> which is not a python module, import csnd tries to import it,
> when it should be importing csnd.py instead.
>
> Solution: move csnd.dll out of there.
"""
And out of "there" refered to the csound/bin folder (where I keep the
csound binary.
Your previous advise (of 10/30) worked well, I'm just confused that
you now seem to say it's allright to keep csnd.dll in the /bin folder
(as this caused problems loading csnd in python).

best
Oeyvind

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net