PE>
  > JdeBP> Just use DosSetRelMaxFH to find the size of the per-process
  > JdeBP> file table, N, and loop from 3 to N closing all of the open
  > JdeBP> file handles.  You can expand the table at the same time.
  >
  > That's a rather strange and brave thing for cvp to be doing.
PE>

  Not necessarily.  As you yourself have found, leaving file handles open
  can cause badly written child processes to run out of table space for
  their own file handles.

PE>
  > Do you seriously think that they're doing that, and  if so, why ?
PE>

  My guess is that Microsoft knew of the problem in their own tools, and
  developed the "close all open file handles that we inherited from our
  parent and that we don't actually use" as a kludge to fix it.  I'll bet
  that PWB does exactly the same as CVP does.

  I had to encode the same kludge into Guidelines, because the problem
  still exists in RC.EXE.

PE>
  > I would have thought that device drivers were validly using those
  > file handles.
PE>

  Any device driver that assumes that an arbitrary process will have a
  specific open file handle is badly broken.

  From actual experience, it's just poor device driver code.  As far as I
  could determine, the file handle that Netware Client for OS/2 uses up is
  from where the device drivers are opening NET.CFG to perform boot-time
  configuration, and simply forgetting to close it again.  They don't
  actually have any reason to use NET.CFG after the system has completed
  booting.

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