From: jj4public@outlook.com   
      
   On Sun, 20 Nov 2022 13:02:01 -0800 (PST), muta...@gmail.com wrote:   
   >   
   > Are you saying there aren't enough bits to assign one   
   > in the executable header, or that Microsoft simply   
   > didn't assign one?   
      
   There is none. There's nothing in 16-bit Windows NE module which is similar   
   to PE module's subsystem field which define a console. Microsoft doesn't   
   define any for 16-bit Windows NE module. 16-bit Windows NE module is always   
   a GUI program.   
      
   > If the latter, I would be happy to assign one myself to   
   > say "console".   
      
   You can add one for your own OS as long as there still an unused module type   
   number or flag.   
      
   > But instead of having a DOS application waiting on the   
   > other end of the "con" pipe, that is something that   
   > PDOS/86 provides as standard (and in fact, only).   
   >   
   > Is that feasible?   
      
   Yes, the CON pipe would be precreated for each application process created.   
   And if the module is of your console type, the system would automatically   
   create the console window and connect it to the CON pipe for the   
   application.   
      
   > And later I may wish to run that in CM16. But I'll   
   > start with RM16.   
   >   
   > Unless I'm missing something?   
      
   Real mode is not possible in CM16, since V86 is absent in CM16. CM16 is pure   
   protected mode. The closest thing is Unreal Mode.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)