From: nimbus@nospicedham.XXX.invalid   
      
    Rugxulo wrote in news:6f9b7acc-b2dd-481d-b10a-05b273cdeaf4   
   @googlegroups.com:   
   > On Wednesday, June 28, 2017 at 4:11:03 AM UTC-5, NimbUs wrote:   
   >> [...] I can't even   
   >> remember where I got the g77 compiler bundle from,   
      
   FWIW, it was a port/packaging of g77 for use on PCs running   
   Win32 (9x or NT), made by K. Kourakis, circa 1999.   
      
   >> I'm just   
   >> positive that it compiles Fortran programs to regular   
   Windows-   
   >> console-subsystem executables   
      
   > Windows uses PE/COFF while DOS/DJGPP uses MZ/COFF. MinGW-based   
   > stuff usually needs Windows' own proprietary MSVCRT.DLL.   
   > DJGPP (and OpenWatcom) don't rely on that at all.   
      
   Precisely, I /have/ a recent version of the MSVCRT permanently   
   residing in my HX\BIN\ folder...   
      
   > HX is interesting but not something to rely upon. And if   
   > you're using MS' MSVCRT.DLL there anyways, then you're   
   > basically missing the whole point. It is normally not   
   > included there by default (obviously??). (There was partial   
   > compatibility you could get with old ReactOS 0.3.14's   
   > MSVCRT.DLL, but your mileage may vary.)   
      
   Would you please develop, explaining in what way it's "missing   
   the whole point" ? Sincere honnest question as the anwer is not   
   "obvious" to me.   
      
   > It's probably wiser to trust a native DOS compiler for DOS   
   > use, even if it PE mostly (accidentally) works under HX.   
   > (The whole point was that XP also works well with DJGPP.)   
      
   >> In other words, it just works (TM) !   
      
   > I tried under QEMU (FreeDOS 1.2 + some networking tools   
   > for downloading), it seems to work fine (DJGPP's G77 + NASM).   
      
   > Of course most people would rather suggest you use latest   
   > "gfor710b.zip" instead.   
      
   Not that I need Fortran 95 ATM.   
      
   Here's my point : I usually write, compile and test programs   
   while multitasking under Windows, for obvious reasons; but for   
   /running/ long (overnight) computations, I'd rather do it under   
   DOS, without the bulk of background schedulking processes and   
   "services" and whatever MS Windows likes to do behind our backs   
   needlessly consuming CPU (and other) resources.   
      
   > Again, just FYI. Use whatever you want.   
      
   "Obviously" :=)   
      
   --   
   Ninho   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)