From: mutazilah@gmail.com   
      
   So a side-effect of creating z/PDOS-generic to use a pseudo-bios   
   is that in under 2000 lines of code I was able to create a S/370   
   emulator plus pseudo-bios sufficient to produce this:   
      
   D:\devel\pdos\util>mfemul ..\generic\pdos.exe fba1b1.vhd   
   memory starts at 00420020   
   welcome to PDOS-generic   
   running as prog   
   before printing parm   
   argv1 is !BOOT   
   about to open   
   done open   
   lba is 1f8   
   fat type is   
   got request to open :pcomm.exe   
   about to call app at address 00301928   
   welcome to pcomm   
   type help for help   
      
   enter a command   
   help   
   help   
   commands that might be available are:   
   exit, type, dir, md, rd, cd, date, time, del, copy   
   fill, fzap   
      
   enter a command   
   dir   
   dir   
   PDOS   
   TEST    TXT   
   COMMAND EXE   
   CONFIG  SYS   
   BIOS    EXE   
   PDOS    EXE   
   TEST2   TXT   
   XXX     TXT   
   TEST    C   
   TEST    S   
   DOS   
      
   enter a command   
   exit   
   exit   
   return from app is hex 0   
   branched below - terminating   
   branched below - terminating   
   program returned with hex 0   
      
   D:\devel\pdos\util>   
      
      
   That means I can have a mainframe OS anywhere that a C90   
   compiler exists - ie basically anywhere.   
      
   Currently it runs PDOS-generic apps, and those channel things   
   like fopen into PosOpenFile.   
      
   My intention is to change that to channel fopen into os_fopen   
      
   Basically people have created a Unix API, a DOS API, a   
   Windows API, but all you actually need is a subset of C90.   
      
   ie fprintf etc all end up as just the primitives - fopen, fread,   
   fwrite, fseek, fclose.   
      
   My intention is to allow the alternative APIs - including   
   PosOpenFile, to continue to exist, but they will be channeled   
   right back into the C90 primitives.   
      
      
   Also note that an advantage of passing the text/binary status   
   up to the OS (similar to Cygwin O_TEXT) is that it also   
   allows ASCII to EBCDIC auto-translation if that is desired.   
      
   Oh - another development is that I have a Win64 ARM64   
   mini-clone now (that runs under UEFI, Linux or Android).   
   So all 4 Windows environments (x86, x64, ARM32, ARM64)   
   have been cloned to a sufficient extent to stand up a toolchain -   
   except ARM64 hasn't been proven because I don't have my   
   own ARM64 toolchain and instead build using Visual Studio.   
      
   All available at https://pdos.org   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)