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,476 of 4,255    |
|    mutazilah@gmail.com to All    |
|    Re: windows    |
|    22 Nov 22 05:46:35    |
      From: muta...@gmail.com              On Tuesday, November 22, 2022 at 5:36:12 PM UTC+8, JJ wrote:              > > I need to at least translate those specific names if I want       > > to rename the physical DLL for some reason.       > >       > > What is the 16-bit equivalent?              > There is none.              Ok, that's an eye opener.              > In 16-bit Windows platform, all console related features are       > handled by the kernel via Interrupt services. CON is only usable when       > there's a console window open.              > > Apparently there was a somewhat common technique to       > > write to a console in the Win16 days, which was opening       > > a con pipe and writing to it.              > It's DOS days, to be precise. CON in Windows is same as DOS' CON.              > > I tried doing a search for win16 con pipe but didn't find       > > a reference.              > CON is a character device, but it works like a pipe and can be implemented       > as a pipe.              My interpretation of the above is that a Win 16 NE executable       can call INT 21H and write to handle 1 and the output will       appear so long as there's a console window open.              I'm not sure what a console window is - I believe 16-bit Windows       allowed multiple DOS prompts.              If I write via INT 21H as above, from a Windows NE executable,       did it start writing to a random MSDOS window?              Or perhaps whichever one was in focus? So you needed to       start the Windows NE executable and then quickly switch       to the DOS prompt? Or did you simply start the Windows NE       executable from the DOS prompt and it stayed with that?              That's simple enough. I didn't know you could do that.              And these Windows NE executables - they presumably were       able to use more than 640k of memory on an 80286, because       they ran in PM16 even though they called INT 21H?              If so, that's fantastic. That's exactly what I'm after.              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