On 29 May 2006 17:13, Christopher Faylor wrote:
> However, when deciding how small to make the windows command line
> buffer, I chose too large a value for filling out the windows command
> line for cygwin processes.
>
> (see http://cygwin.com/ml/cygwin/2006-04/msg00534.html)
>
> I've reduced the size of the windows command line which is sent to
> Cygwin processes still further and that fixes the problem on my game
> computer. That fact that this worked just fine on my normal test
> computer (and presumably on Corinna's computer) is why this problem
> crept back in. So, that leads me to believe that this problem is
> system-dependent. I hope the constant that I chose is small enough
> for all of the systems out there.
Does that mean 31767 ~= (32768 - size of environment) and that's why it
failed?
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
