From: gneuner2@nospicedham.comcast.net   
      
   On Wed, 20 Jan 2021 09:41:17 +0100, "R.Wieser"   
    wrote:   
      
   >Paul,   
   >   
   >> I press the Windows key & the "r" key, and then I type "cmd"   
   >> and then I press the "enter" key. Whatever CLI that happens to   
   >> be called, is what I want the program I assemble to work inside of.   
   >   
   >The problem is that you can run true (16-bit) DOS programs[1] (using INT 21h   
   >and whatnot) as well as CLI (Command Line Interface - Windows Console)   
   >programs (using the full gamut of Windows DLLs) in there.   
   >   
   >[1] Caveat emptor: I'm using Win XP myself.  I have no idea if still works   
   >under Win10.   
      
   Win10 does not natively run 16-bit software.   
      
   There *was* an XP subsystem - separate from the "compatibility"   
   settings - available for Win7 Professional (or higher).  It still   
   works on Win10 ... but most people who could have installed it on Win7   
   never did, and it won't install on Win10 - the only way to have it is   
   via in-place upgrade of Win7 to Win10.   
      
   Best to set up a VM and run an older version of Windows (or DOS).   
      
   George   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)