Michael's latest installer *does* indeed SET all the relevent variables in
autoexec.bat in my WindowsME machine. (About 7 or 8 changes are made,
including additions to PATH.)

The only variable it did *not* replace/change was OPCODEDIR, which remains
that of the previous most recent installation.

Is this correct?

I've copied my autoexec.bat below. Csound5.00 is the latest installation;
Csound5new is the previous installation.

Art Hunkins

SET BLASTER=A220 I5 D1 H1 T4
SET windir=C:\WINDOWS
SET winbootdir=C:\WINDOWS
SET COMSPEC=C:\WINDOWS\COMMAND.COM
SET PROMPT=$p$g
SET TEMP=C:\WINDOWS\TEMP
SET TMP=C:\WINDOWS\TEMP
SET OPCODEDIR=C:\Csound5new
SET
PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\VargaCsound5\bin;C:\PROGRA~1\CSOUND~1;
C:\CSOUND~1;C:\CSOUND5.00\BIN
SET CSOUNDRC=C:\Csound5.00\.csoundrc
SET OPCODEDIR64=C:\Csound5.00\plugins64
SET RAWWAVE_PATH=C:\Csound5.00\samples
SET PYTHONPATH=;C:\Program Files\Csound5new;C:\Csound5new;C:\Csound5.00\bin
SET SFOUTYP=WAV

----- Original Message -----
From: "Istvan Varga" 
To: 
Sent: Friday, February 03, 2006 11:22 AM
Subject: Re: [Csnd] Csound 5 Woes for Csound 5 Newbie


> On Friday 03 February 2006 16:53, David Akbari wrote:
>
> > A potential problem could be that the mechanism with which a user sets
> > an environment variable differs on Win2k than on WinXP (which appears
> > to be the default deployment target for the Csound5 Windows Installer).
> >
> > Does the CsoundVST Windows installer implement the mechanism to change
> > the AUTOEXEC.BAT file in versions of Windows prior to Microsoft's use
> > of the NTFS ?
>
> I think Windows 2000 should behave the same way as XP with respect
> to environment variables. Technically, Windows 2000 is NT 5.0, while
> XP is NT 5.1. Editing AUTOEXEC.BAT is needed on 95/98/Me which are
> DOS based.
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk