MS>
  > MS>> just do what MS suggest to do. change the startup code.
  >
  >  PE> The real objective is to fix the C program called CL!
  >  PE> Which obviously doesn't come with source code.
  >
  > ???? whats the problem with CL.EXE ????
  >
  > you should NOT confuse CRT with a codeTranslator. CL.EXE
  > (which in reality is just the compiler front end - when you
  > want to patch the compiler you must path the compiler back
  > end!) is just the codeTranslator. it has nothing to do with
  > the crt.
MS>

  He's having problems compiling a program with a lot of #include
  statements in, because CL.EXE runs out of file handles as it is
  compiling.

  This can be traced to the fact that CL.EXE is itself linked to
  Microsoft's RTL, and so has the same restrictions on open files that
  compiled C programs have.

  Interestingly enough, Microsoft is not the only compiler vendor whose
  tools suffer from limitations in their own runtime library.  Borland's
  command-line compiler and linker for DOS have massive efficiency
  problems if you redirect their output through a pipe -- the same
  problems that programs compiled in Borland C++ for DOS have.

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