From: kifox AT hotmail DOT com (kifox) Newsgroups: comp.os.msdos.djgpp Subject: Re: why won't my .exe program run properly until I set env var? Date: 29 Jan 1998 14:22:03 GMT Organization: Your Organization Lines: 27 Message-ID: <6aq3ab$opd$1@winter.news.erols.com> References: <34CFCEC3 DOT 6C89 AT cs DOT com> NNTP-Posting-Host: user30.firstsaga.com Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk In article , davep AT hagbard DOT demon DOT co DOT uk says... > >On Wed, 28 Jan 1998 19:35:15 -0500, John M. Aldrich wrote: > >> > 1. Start up a DOS window from windows95 >> > 2. Run the batch file (which has >> > set djgpp=c:\djgpp\djgpp.env >> > set path=c:\djgpp\bin;%path%) >> > 3. Start programming >> >> This is silly. If you plan to do a lot of programming in DJGPP, you >> should set the environment variables in your autoexec.bat so they always >> exist. I can't think of any possible reason why this wouldn't work >> better. > >While, on the whole, I'd agree with you (DJGPP is my DOS C compiler of >choice) there are times when you don't want to do it. For example, if you >have more than one GNU development environment (DJGPP, GCC-Win32, >GCC-Win32-prc, ...). Also, it's a way of getting around the "out of enviroment space" error msg without actually increasing the size of it, since you're only creating the varibles that you're actually using at the time. It also avoids having to edit the autoexec.bat if you want to make changes in your DJGPP setup.