Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,474 of 4,255    |
|    mutazilah@gmail.com to All    |
|    Re: windows    |
|    21 Nov 22 05:01:53    |
   
   From: muta...@gmail.com   
      
   On Monday, November 21, 2022 at 7:53:09 PM UTC+8, JJ wrote:   
      
   > > Ok, cool. So what does my Windows NE module need   
   > > to do to write to that pre-allocated CON pipe to   
   > > display a "hello world"?   
   > >   
   > > Is it still a call to WriteFile?   
      
   > Implement the concept of standard input, output, and error handles. Add more   
   > if needed. IIRC, *nix has more than 3 standard handles.   
      
   Sorry, I don't understand.   
      
   First, I'm only interested in C90, so there's only the 3 handles   
   to be concerned with, and the concept already exists.   
      
   What I want to do is make use of existing practice to give   
   applications somewhere to write to.   
      
   It is my C library, PDPCLIB, that will do the actual writing.   
   Actual C90 applications will not be aware that a named   
   pipe is involved. There is no need to provide applications   
   with a GetStdHandle API or any such thing. It's all hidden   
   in the C library.   
      
   Existing practice is a "con" pipe that ends up on a DOS   
   window. That's an interesting setup.   
      
   But I only need to know the interface that the Windows   
   NE executable sees in such an arrangement.   
      
   I will be marrying the fairly-standard 16-bit Windows NE   
   executable up to something completely different.   
      
   Let's start with PDOS/PM16.   
      
   When operating in this "con pipe" mode, what does the   
   NE executable see/do? Does it call a DLL? What's the   
   name of the DLL?   
      
   PDOS/PM16 will provide an artificial DLL to satisfy that.   
      
   But what is the actual DLL call? Is it OpenFile("pipe:con")   
   or an INT 21H or what?   
      
   > It's best to have the main OS kernel in the execution mode where it has   
   > access to all memory address space. Otherwise it would take more effort to   
   > access all of them. Or worse, be limited.   
      
   Sure. Let me start with PM16 and I'll see if CM16 is   
   useful another day. At least I'll actually have something   
   to be backward-compatible with when I get there!   
      
   Thanks. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca