Jonathan de Boyne Pollard wrote in a message to Mike Bilow:

 JdBP> One question that I've always meant to ask.  What happens to 
 JdBP> the process context that is used for device driver 
 JdBP> initialisation?   Process 2 is (usually) PMSHELL.EXE, but what 
 JdBP> becomes of Process 1?

It starts the first half of PMSHELL and dies.  Here is my Maximus system:

  PID  PPID   SID MHNDL THRDS  MODS  SEMS  SSEG COMMAND
  112     0    17  1013    18     0     1     0 C:\MAX\MCP.EXE
    3     1     1   478    20    27     9    10 D:\OS2\PMSHELL.EXE
 1201     3    23   953     1    11     2     2 D:\OS2\CMD.EXE
 1290  1201    23  1032     1     0     2     0 C:\UTIL\OS2\AIX\PS.EXE
   34     3    17   953     1    11     3     2 D:\OS2\CMD.EXE
 1264    34    17  1638     3     8     2     3 C:\BINK\BT32.EXE
    8     3    19   930     3    13     2     2 D:\UTIL\OS2\MEMSZ\MEMSIZE.EXE
    7     3    18   478    13    28     3     3 D:\OS2\PMSHELL.EXE
    5     3    16   716     4     9     2     2 D:\OS2\PMSPOOL.EXE
    4     3     0   578     3     4     3     4 D:\OS2\SYSTEM\HARDERR.EXE

MCP is detached, which is shown by the Parent PID 0.  On my system, PID 2
is consumed by something executed by a CALL statement in CONFIG.SYS, which
occurs before PMSHELL is started, so PMSHELL becomes PID 3.
 
-- Mike


---