From: james.harris.1@nospicedham.gmail.com   
      
   On 26/05/2021 23:33, luser...@nospicedham.gmail.com wrote:   
   > On Monday, May 24, 2021 at 8:40:27 PM UTC-5, anti...@nospicedh   
   m.math.uni.wroc.pl wrote:   
   >> luser...@nospicedham.gmail.com  wrote:   
      
   ...   
      
   >> Basic question is what do you want to emulate? 8086 by itself can not   
   >> do file I/O. You may do PC emulator in style of Bochs, that is   
   >> emulate common hardware. You may do BIOS emulator. You may   
   >> do DOS emulator, that is emulate file I/O at DOS level. Or   
   >> you may emulate different system. For example QEMU 386 emulates   
   >> Linux system calls. If you want your emulator to be simple,   
   >> you may define your own system calls (say using something like INT 0x80h),   
   >> thing like open, close, read, write. Advantage is simplicity.   
   >> Disadvantage is that large body of existing 8086 assembler programs   
   >> assumes DOS environment and will not work with different system.   
   >>   
   >   
   > Very good points. Thanks. You're right that the 8086 by itself only has   
   > in/out instructions, ESC instructions, and memory mapped IO, all of which   
   > depend on the rest of the system. It appears that the IBM BIOS operates   
   > at the very low level of clusters, heads, and sectors. But the DOS functions   
   > appear to map pretty closely to stdio.h functions. So that seems to be   
   > the easiest path forward.   
      
   There's a guy on alt.os.development who has been posting about very much   
   the same sorts of thing. Maybe there's value in the two of you getting   
   in touch, if you aren't already.   
      
      
   --   
   James Harris   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)