PE>
  > PE> Ok, so how do you do this properly?  for (x = 0; x <
  > PE> ULONG_MAX; x++) DosClose(x);
  >
  > JdeBP> I'd use the value obtained by DosQueryRelMaxFH (with a delta of
  > JdeBP> zero) as the highest file handle.  Other than that, yes.
  >
  > Ok, you've convinced me.  Now, can you tell me whether what
  > Peter said (which was "wrong"), is actually right in a
  > difference context? BFN.  Paul.
  >
  > PF> I'll bet it has nothing to do with cvp directly (someone else up the
  > PF> parent tree is using those file handles already),  but has to do with
  > PF> the equivalent of a "start /i".
  >
  > PF> What happens if you start a session with "start /i"
and run your
  > PF> compile from there?
PE>

  I'm not sure of the context of the original discussion, but the /I flag
  to the START command results in the SSF_INHERITOPT_SHELL flag being used
  in the call to DosStartSession, rather than the SSF_INHERITOPT_PARENT
  flag.

  This means that the spawned process is a child of the "shell", rather
  than a child of the process that called DosStartSession.  As a result,
  it inherits the open file handles of the "shell", rather than those of
  the invoking process.

  The internal mechanics of this are obscure.  I assume that there is,
  somewhere, a privileged means of communication between the
  DosStartSession system call and the "shell" process.  (Anyone know?)

  Crank up your favourite process viewer, and watch what happens to the
  process tree when you run different programs with START /I.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.01