Hi Istvan, I think perhaps that if it is a bit more noticable it would perhaps help people realize more that it isn't set. I don't think it should be a fatal warning as it doesn't prevent Csound itself from running, but should be a warning message. it seems to me that after a year or so having OPCODEDIR around that information isn't being picked up by users, old and new. If there already is a message in there, then somehow making it more visible as suggested would help get people new to csound5 to realize there is something there. steven On 9/15/05, Istvan Varga wrote: > Steven Yi wrote: > > > Since OPCODEDIR and OPCODEDIR64 being set is coming up as an issue > > over and over again, what does everyone think about displaying a > > message to the user when they run Csound and it is not set, something > > like: > > Actually, there is already a message with a second of delay to make it > more noticeable, but it can be changed as you suggested, and perhaps > it could be a fatal error instead of just a warning. > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net