Re[3]: 3.2 Final?

[Jonathan Pierce <Jo...@seagram.com>]

An alternate technote suggested the following alternate solution:

To resolve this issue, increase the default environment space available for
MS-DOS programs. To do this, use one of the following methods: 

Modify the Environment for All MS-DOS Programs
To increase the default environment space for all MS-DOS programs running in
Windows, edit the Shell command in the Config.sys file. To do this, follow these
steps: 
Click Start, click Run, type sysedit in the Open box, and then click OK.

Click the Config.sys file, and then type a new Shell command or replace any
existing Shell command with the following line 

SHELL=<path>\COMMAND.COM /E:4096 /P 
where <path> is the drive letter and path in which the 


Modify the Environment for a Specific MS-DOS Program
To increase the default environment space for a specific MS-DOS program, follow
these steps: 
Right-click the MS-DOS program icon, and then click Properties.

On the Memory tab, type or click the number of kilobytes (KB) the program
requires in the Initial Environment box, and then click OK.

NOTE: The maximum amount of memory you can allocate for an MS-DOS program is
4096 KB. 


____________________Reply Separator____________________
Subject:    Re[2]: 3.2 Final?
Author: tomcat-dev@jakarta.apache.org
Date:       8/4/00 3:20 PM

Why don't we just include in the instructions how to add additional enviroment
space to the DOS environment. I think this will solve the line length problem
you are having in Win98.  I haven't tested it since Tomcat 3.1 though, since I
am running WinNT.

-Jonathan

According to a Microsoft tech note that I read,

If the MS-DOS-based application requires more than 256 bytes of environment
space and you are running Windows 3.1 or later, add the following line to the
SYSTEM.INI file under the [NonWindowsApp] section: 
   [NonWindowsApp]
   CommandEnvSize=1024 
1024 bytes should work properly; however, the setting can be set as high as
32,768 bytes. The value must be either zero or between 160 and 32768. 

This is a global setting that affects all virtual machines (VMs).



____________________Reply Separator____________________
Subject:    Re: 3.2 Final?
Author: tomcat-dev@jakarta.apache.org
Date:       8/4/00 10:54 AM

Serge Knystautas wrote:

> Why not try the trick ant does?  It does a for loop on another bat file
> which gradually builds a temporary environment variable.

It actually does that, building up the CP environment variable.

>  Then the
> java.exe command can just use the environment variable.  I don't know
> how this would work for a huge number of jar files, but in principle it
> seems to get around having a huge command line.
>

Building up CLASSPATH instead (so you don't have to pass it on the command line)
would help, but the
loop script itself executes a SET command to append each JAR file to the end. 
That command is still
subject to line length restrictions, as far as I know.

Relative paths would shorten the list, but only if your current working
directory is $TOMCAT_HOME.
Otherwise, you still need to spell them out.

A better long-term answer might be an installer program that configures a
launcher (on Windows
platforms) to get around these difficulties, which stem from limitations in
COMMAND.COM.

>
> Serge Knystautas
> Loki Technologies
> http://www.lokitech.com/
>

Craig



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org