From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,15239bed02372eea X-Google-Attributes: gid103376,public From: Joe DeKeyrel Subject: Re: GNAT 3.04a & Environment space Date: 1996/08/16 Message-ID: <32152B67.253@telis.org>#1/1 X-Deja-AN: 174695246 references: <4v0q0e$cbq@newsbf02.news.aol.com> content-type: text/plain; charset=us-ascii organization: TELIS mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.02Gold (Win95; I) Date: 1996-08-16T00:00:00+00:00 List-Id: Robert A Duff wrote: > > In article , > I wrote: > >I also had luck with putting "call ...\setpath" in my autoexec.bat file. > >I don't know if this solves the env space problem, ... > > Well, it does seem to. On a different computer, running windows 95, I > put "call c:\gnat304a\setpath" in my autoexec.bat file, and I am now > able to run gnatmake just fine. I did not fiddle with the "initial > environment" settings (i.e. I disobeyed the README) -- I left it set to > "Auto" (whatever that means). > > - Bob I run a similar setup myself (when I'm not running linux). You really MUST increase the size of the environment to allow for all the environment virables that setpath requires. i.e. right mouse select the shortcut you've created -- I'll assume you have choose properties on the memory tab, dropdown the environment list box select 1024 -- works on my machine that should do it... -- Joe DeKeyrel Systems Integration Engineer Ft Irwin, CA (619) 386-2572