On Mon, 24 Aug 2020 11:43:27 -0400, "Rick C. Hodgin"   
    wrote:   
   >...   
   >All of these were off the top of my head, with minimal testing.  I find   
   >Open Watcom somewhat difficult to wield as I'm used to Visual Studio.   
   >One flaw is if CAPS LOCK is on, your function keys to step into and over   
   >code doesn't work in the version I have.   
   >   
   >I have Visual Studio 2003, and I tried to get it to compile a 16-bit   
   >DOS application but it's not supported in that version.  I think I have   
   >to go back to VS98 for that.   
   >...   
   For old DOS stuff I have TASM (with Turbo Debugger), MASM (with PWB   
   and CV), and NASM installed in my DOSBox.   
      
   If you replace the   
      
   org 100h in a nasm file with:   
      
   section	.text   
   resb 100h   
   ..start   
      
   you can do:   
   nasm -w-orphan-labels -g -f obj file.asm   
   tlink /v file.obj (you get a warning no stack here, but can ignore it)   
   tdstrip -s -c file.exe (that converts the exe to com and puts the   
                           debug symbols in file.tds   
   td file.com   
      
   finally gives you Source level debbuging with a COM file.   
   --   
   aen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)