From: jj4public@outlook.com   
      
   On Sat, 19 Nov 2022 08:49:48 -0800 (PST), muta...@gmail.com wrote:   
   >   
   > Also, I assume it was physically possible to create an executable   
   > that did a WriteFile to something resembling stdout. But due to   
   > the absence of a console the output just disappeared.   
      
   16-bit Windows doesn't have standard output/input handles. It only has   
   pipes. DOS devices such as `con` and `aux` are named pipes. They're not   
   recognized as standard output/input. 16-bit Windows doesn't have any   
   `GetStdHandle()` function or constants such as `STD_OUTPUT_HANDLE`.   
      
   > But if I replace 16-bit Windows with my own 16-bit Windows (that is   
   > console mode only), would that executable suddenly start working?   
   >   
   > Or is there something missing from the executable technically?   
      
   16-bit Windows NE module does not support a Console flag for the program   
   type. 16-bit Windows programs can not have their own console(s), by design.   
   Only DOS programs do. Period.   
      
   > I assume any WriteFile to actual files works fine, even if I only   
   > provide a console.   
      
   Yes, but that console would have to be provided by a separate DOS program.   
   If you're developing you own OS, then you can do whatever you want.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)