From: Terence on
I have met the stack overflow problem.
"Stack Overflow: Error 2000"

With me it only occured in two cases, and ONLY in operating systems of
Windows 2000 and XP that had been updated on-line by Microsoft,
applying "security patches".
These apparently carve off some user stack to work with; I calculate
about #4000 hex worth.

Case 1) One program calling another as a daughter process (the caller
fails)
Case 2) A program calling SYSTEM services.

My solution was to take the executable and add another #4000 (hex)
space to the stack.
This worked for me.

From: Mike on
On Oct 9, 6:59 am, Terence <tbwri...(a)cantv.net> wrote:
> I have met the stack overflow problem.
> "Stack Overflow: Error 2000"
>
> With me it only occured in two cases, and ONLY in operating systems of
> Windows 2000 and XP that had been updated on-line by Microsoft,
> applying "security patches".
> These apparently carve off some user stack to work with; I calculate
> about #4000 hex worth.
>
> Case 1) One program calling another as a daughter process (the caller
> fails)
> Case 2) A program calling SYSTEM services.
>
> My solution was to take the executable and add another #4000 (hex)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Can you explain more clearly?
Or, give me an example.

Mike

> space to the stack.
> This worked for me.


From: Mike on
On Oct 9, 6:59 am, Terence <tbwri...(a)cantv.net> wrote:
> I have met the stack overflow problem.
> "Stack Overflow: Error 2000"
>
> With me it only occured in two cases, and ONLY in operating systems of
> Windows 2000 and XP that had been updated on-line by Microsoft,
> applying "security patches".
> These apparently carve off some user stack to work with; I calculate
> about #4000 hex worth.
>
> Case 1) One program calling another as a daughter process (the caller
> fails)
> Case 2) A program calling SYSTEM services.
>
> My solution was to take the executable and add another #4000 (hex)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Can you explain more clearly?
Or, give me an example.

Mike

> space to the stack.
> This worked for me.


From: Mike on
On Oct 9, 6:59 am, Terence <tbwri...(a)cantv.net> wrote:
> I have met the stack overflow problem.
> "Stack Overflow: Error 2000"
>
> With me it only occured in two cases, and ONLY in operating systems of
> Windows 2000 and XP that had been updated on-line by Microsoft,
> applying "security patches".
> These apparently carve off some user stack to work with; I calculate
> about #4000 hex worth.
>
> Case 1) One program calling another as a daughter process (the caller
> fails)
> Case 2) A program calling SYSTEM services.
>
> My solution was to take the executable and add another #4000 (hex)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Can you explain more clearly?
Or, give me an example.

Mike

> space to the stack.
> This worked for me.


From: Mike on
On Oct 9, 6:59 am, Terence <tbwri...(a)cantv.net> wrote:
> I have met the stack overflow problem.
> "Stack Overflow: Error 2000"
>
> With me it only occured in two cases, and ONLY in operating systems of
> Windows 2000 and XP that had been updated on-line by Microsoft,
> applying "security patches".
> These apparently carve off some user stack to work with; I calculate
> about #4000 hex worth.
>
> Case 1) One program calling another as a daughter process (the caller
> fails)
> Case 2) A program calling SYSTEM services.
>
> My solution was to take the executable and add another #4000 (hex)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Can you explain more clearly?
Or, give me an example.

Mike

> space to the stack.
> This worked for me.