Thanks, Istvan and Steven, for your replies.

I think most users will very much look forward to GUI installer versions of
Csound5 that deal automatically set the environment variables.

Certainly Csound4 for Windows in several incarnations - including flCsound,
CsoundAV and MyCsound4 - were all user-friendly, and it's my hope that
Csound5 will become so as well - in good time. (I guess this is what is
meant by "front-end" development. I'd also guess that front ends, such as
those in flCsound and CsoundAV, are very important to anyone but the
long-time and technically sophisticated user.)

Art Hunkins

----- Original Message -----
From: "Istvan Varga" 
To: 
Sent: Thursday, September 01, 2005 5:28 PM
Subject: Re: [Csnd] One last MIDI Csound question


> Art Hunkins wrote:
>
> > It would be ***very*** helpful for there to be defaults for all these
> > directory variables, so that most users wouldn't even have to bother
with
> > (or even know about) them. It is very confusing, especially considering
the
> > fact that Istvan's versions are the only Windows Csound (to my
knowledge)
> > that requires the user to supply these variables(??).
>
> The Gogins releases also require OPCODEDIR/OPCODEDIR64, but the GUI
> installer automatically sets environment variables. You may want to use
> that instead if you have problems with setting the environment variables.
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk