Installing Gnat 'out of environment space'

Installing Gnat 'out of environment space'

[Nick Sharples]

I'm having trouble running out of environment space when I try to run the 'setpath.bat' file with the latest 
release of Gnat for Win95.

How do I solve this little problem?

Re: Installing Gnat 'out of environment space'

[David Shochat]

>>>>> "Nick" == Nick Sharples <nicnac@dial.pipex.com> writes:
In article <31729998.22F2@dial.pipex.com> 
Nick Sharples <nicnac@dial.pipex.com> writes:


    Nick> I'm having trouble running out of environment space when I
    Nick> try to run the 'setpath.bat' file with the latest release of
    Nick> Gnat for Win95.

    Nick> How do I solve this little problem?

This should be an FAQ (I remember how frustrating it was the first time I ran 
into it...)

Anyway, go into the Explorer and navigate to C:\Windows\Start Menu\Programs.
Click the right mouse button on MS-DOS Prompt, and choose Properties from the 
popup. Select the memory tab and change "Initial environment" to 1024.
-- 
David Shochat
dshochat@logicon.com  shochat@roosevelt.logicon.com

Re: Installing Gnat 'out of environment space'

[Bob Crispen]

David Shochat <shochat@ROOSEVELT.LOGICON.COM> sez:

>    Nick> I'm having trouble running out of environment space when I
>    Nick> try to run the 'setpath.bat' file with the latest release of
>    Nick> Gnat for Win95.
>
>    Nick> How do I solve this little problem?
>
>This should be an FAQ (I remember how frustrating it was the first time I ran
>into it...)
>
>Anyway, go into the Explorer and navigate to C:\Windows\Start Menu\Programs.
>Click the right mouse button on MS-DOS Prompt, and choose Properties from the
>popup. Select the memory tab and change "Initial environment" to 1024.

There is a slightly more elegant solution.  Make a copy of the MS-DOS
prompt shortcut that's in c:\Windows\Start Menu\Programs and put it in
another folder in that same tree structure and then set the properties
in the copy.  Following David's advice sets the properties for the default
MS-DOS prompt, which may not always be a good idea, especially if they
issue a fix that makes selecting "Auto" actually work.

Incidentally, if you do make a copy of the MS-DOS shortcut in another
folder (I've got a folder called Programming) then you can put a new icon
on that shortcut, set the default directory, and, most important of all,
start in a directory of your choice and use the Gnat setpath.bat file as
the initial script!

One more, uh, feature you may run into: if you've got a space in any
of your names in PATH (e.g., you've installed Netscape under Program
Files), then the PATH line that comes with the Gnat-supplied setpath.bat
will fail with a "Too many arguments" error.

This does NOT mean that your PATH is too long, which is what a newbie
to DOS might take that to mean.  Here's the offending line in
setpath.bat (or an approximation to it):

set PATH=D:\Ada\Gnat;%PATH%

The problem comes when the existing PATH on the right-hand side of that
line is expanded; DOS finds the space in the existing PATH and barfs
because now you have too many parameters on the right-hand side of the
SET statement.

Change this line in setpath.bat to:

set PATH="D:\Ada\Gnat;%PATH%"

(or whatever the right syntax is -- just add the quotes), and it works
fine.

The Gnat folks might want to consider modifying setpath.bat, since I
believe the quotes are always harmless if they aren't needed.

Sorry to be so PC-specific, but there are a lot of them out there, all
owned by potential Ada fans.

Bob Crispen
revbob@eight-ball.hv.boeing.com
crispen@hiwaay.net
Speaking for myself, not my company

Re: Installing Gnat 'out of environment space'

[Tom Griest]

Nick Sharples <nicnac@dial.pipex.com> writes:
>I'm having trouble running out of environment space when I try to 
>run the 'setpath.bat' file with the latest 
>release of Gnat for Win95.
>
>How do I solve this little problem?


Too bad the Win95 help is so junky that you can't use it to figure this
out.  Maybe in the next release of Win95....


Anyhow you can try this:
-----------------------------------------------------------------------------

To increase the environment space allocated to a command window in Win95:


You can change either the properties of the "command.com" program
or any shortcut to that program.  The following tells you how to do it
to the command.com program:

Right click on start button.  Click on "explore".

Using the explorer, navigate to the windows directory (normally c:\windows)
and right-click on "command.com" in the right pane.  Click "properties".

Select the "Memory" tab and in the drop down box under "Initial Environment"
choose a size of at least 1024 bytes.

Re: Installing Gnat 'out of environment space'

[Dave McKenna]

Nick Sharples <nicnac@dial.pipex.com> wrote:

>I'm having trouble running out of environment space when I try to run the 'setpath.bat' file with the latest 
>release of Gnat for Win95.

>How do I solve this little problem?

Just ran into this problem;  solved it by:
1) making a shortcut to setpath.bat
2) right-clicking on the shortcut icon & selecting 'properties
3) going to the 'memory' tab & setting the initial environment to
1024.

HTH.

Re: Installing Gnat 'out of environment space'

[Daryl Siddon]

Nick Sharples wrote:
> 
> I'm having trouble running out of environment space when I try to run the 'setpath.bat' file with the latest
> release of Gnat for Win95.
> 
> How do I solve this little problem?

Another method for Win95 is to place the following in your "config.sys"
file:
SHELL=C:\WINDOWS\COMMAND.COM C:\WINDOWS /P /E:2048
                                           ^^^^^^^
                                           Your Value Here.
              
This option indicates that any MS-DOS shell (from within Win95) will
use 2048 bytes for the environment. You can run "help command" from
a Win95 DOS window for the particulars about the command interpreter
"COMMAND.COM."

NOTE: I had to increase the environment space above 1024 to set all of
      my existing and the new "GNAT for Win95" environment variables.
 
I have since transitioned with success to the approach described
by Tom Griest.

Daryl Siddon

Re: Installing Gnat 'out of environment space'

[Zbigniew Fryzlewicz]

> >
>
> There is a slightly more elegant solution.  Make a copy of the MS-DOS
> prompt shortcut that's in c:\Windows\Start Menu\Programs and put it in
> another folder in that same tree structure and then set the properties
> in the copy.  Following David's advice sets the properties for the default
> MS-DOS prompt, which may not always be a good idea, especially if they
> issue a fix that makes selecting "Auto" actually work.
> 
> Incidentally, if you do make a copy of the MS-DOS shortcut in another
> folder (I've got a folder called Programming) then you can put a new icon
> on that shortcut, set the default directory, and, most important of all,
> start in a directory of your choice and use the Gnat setpath.bat file as
> the initial script!
> 
> One more, uh, feature you may run into: if you've got a space in any
> of your names in PATH (e.g., you've installed Netscape under Program
> Files), then the PATH line that comes with the Gnat-supplied setpath.bat
> will fail with a "Too many arguments" error.
> 
> This does NOT mean that your PATH is too long, which is what a newbie
> to DOS might take that to mean.  Here's the offending line in
> setpath.bat (or an approximation to it):
> 
> set PATH=D:\Ada\Gnat;%PATH%
> 
> The problem comes when the existing PATH on the right-hand side of that
> line is expanded; DOS finds the space in the existing PATH and barfs
> because now you have too many parameters on the right-hand side of the
> SET statement.
> 
> Change this line in setpath.bat to:
> 
> set PATH="D:\Ada\Gnat;%PATH%"
> 
> (or whatever the right syntax is -- just add the quotes), and it works
> fine.
> 
> The Gnat folks might want to consider modifying setpath.bat, since I
> believe the quotes are always harmless if they aren't needed.
> 
> Sorry to be so PC-specific, but there are a lot of them out there, all
> owned by potential Ada fans.
> 
> Bob Crispen
> revbob@eight-ball.hv.boeing.com
> crispen@hiwaay.net
> Speaking for myself, not my company

I've followed your advice and almost successfully installed AdaWin95. But now new problem has occured.
Script file winlibs.ld is invoked when switch mwindows is used in the command line. The contents of the 
winlibs.ld is as follows:
SECTIONS {.text 0x401000 :{
...\gnat301a\lib\comdlg32.lib
...\gnat301a\lib\advapi32.lib
...\gnat301a\lib\gdi32.lib
}}
and above mentioned lib files are sought during linking process. However, such files do not exist. I've found 
only "similiar" files with dll extention, i.e. comdlg32.dll, advapi32.dll, gdi32.dll. 
My question is how to obtain the required lib files ? (I've followed all steps of installation process).


Zbig Fryzlewicz
fryzlewicz@ci-4.ci.pwr.wroc.pl

Re: Windows Lib files (was 'out of environment space')

[Greg Bond]

Tom Griest wrote:
> 
> fryzlewicz@ci-4.ci.pwr.wroc.pl writes:
> [snip]
> >But now new problem has occured.
> >Script file winlibs.ld is invoked when switch mwindows is used in the command line. The contents of the
> >winlibs.ld is as follows:
> >SECTIONS {.text 0x401000 :{
> >...\gnat301a\lib\comdlg32.lib
> >...\gnat301a\lib\advapi32.lib
> >...\gnat301a\lib\gdi32.lib
> >}}
< snip...>
> These files are distributed by a variety of sources, but all of them
> (AFAIK) are pay-for development environements, including MSVC, MS SDK
> (with developer's platform), I believe the Borland SDK has these, and
> we have a low-cost SDK that includes them along with the GNAT compiler
> and the Win32 Ada bindings.



Could you be more specific about who "we" are? There's a programming 
group here that wants a low cost (i.e. lower than MS SDK) alternative to 
accessing the Windows API from Ada 95 (GNAT to be specific).



--
* Greg Bond                         * Dept. of Electrical Eng.  
* email: bond@ee.ubc.ca             * Univ. of British Columbia      
* voice: (604) 822 0899             * 2356 Main Mall                 
* fax:   (604) 822 5949             * Vancouver, BC              
* web: http://www.ee.ubc.ca/~bond   * Canada, V6T 1Z4

Windows Lib files (was 'out of environment space')

[Tom Griest]

fryzlewicz@ci-4.ci.pwr.wroc.pl writes:

[snip]

>But now new problem has occured.
>Script file winlibs.ld is invoked when switch mwindows is used in the command line. The contents of the 
>winlibs.ld is as follows:
>SECTIONS {.text 0x401000 :{
>...\gnat301a\lib\comdlg32.lib
>...\gnat301a\lib\advapi32.lib
>...\gnat301a\lib\gdi32.lib
>}}
>and above mentioned lib files are sought during linking process. However, such files do not exist. I've found 
>only "similiar" files with dll extention, i.e. comdlg32.dll, advapi32.dll, gdi32.dll. 
>My question is how to obtain the required lib files ? (I've followed all steps of installation process).

These files are distributed by a variety of sources, but all of them
(AFAIK) are pay-for development environements, including MSVC, MS SDK
(with developer's platform), I believe the Borland SDK has these, and
we have a low-cost SDK that includes them along with the GNAT compiler
and the Win32 Ada bindings.

-Tom
LabTek Corp.

Re: Windows Lib files (was 'out of environment space')

[Tom Griest]

In article <317ECCC2.6F05@ee.ubc.ca> Greg Bond <bond@ee.ubc.ca> writes:
>Tom Griest wrote:
[snip]
>> we have a low-cost SDK that includes them along with the GNAT compiler
>> and the Win32 Ada bindings.
>
>Could you be more specific about who "we" are? There's a programming 
>group here that wants a low cost (i.e. lower than MS SDK) alternative to 
>accessing the Windows API from Ada 95 (GNAT to be specific).
>

You chopped my signature.  "We" is LabTek Corp.

-Tom Griest
LabTek Corp.