MB>
  > [...] how do you determine the necessary stack size [of a 2ry thread] ?
MB>

  Although you could analyse your program and its stack use, it's pretty
  much a waste of effort, since OS/2 only allocates as much memory to a
  stack as it actually used (read the on-line help about guard pages).  So
  you can get away with just allocating a round number such as 64Kb for a
  secondary thread's stack, and let OS/2 handle committing memory as
  required.

  Note:  This approach works everywhere apart from programs compiled with
  Borland C++ for OS/2 using the "thread patch" to the BC++OS2 rutime
  library (which forces the whole stack for each thread to be committed,
  rather than using OS/2's guard page mechanism to commit the stack memory
  on demand).

  > JdeBP <
___
 X MegaMail 2.10 #0:
--- Maximus/2 3.01