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,454 of 4,255    |
|    mutazilah@gmail.com to All    |
|    Re: windows    |
|    18 Nov 22 13:37:57    |
      From: muta...@gmail.com              On Saturday, November 19, 2022 at 3:25:48 AM UTC+8, JJ wrote:              > > Ok, in that case, could Microsoft support CM16 if they       > > wanted to?              > Yes, they could if they want to.              Ok, thanks. In that case, maybe I'll get a 64-bit PDOS       running, and add 16-bit support, with the knowledge       that Microsoft can do it themselves if they wish.              > > And if so, what sort of things could I run under it? Would       > > it need a new API or would the OS/2 1.0 API be suitable       > > for the task at hand?              > Any code which is designed for pure 16-bit protected mode.              A C-generated executable normally doesn't manipulate       segment registers/selectors. That's what I'm interested       in. Large memory model is the main thing I want. I assume       lds still works to load a selector instead of a segment.              > > Again, I'm only interested in console mode applications.              > 16-bit windows platform doesn't have a native console. Console support are       > provided for real mode programs. Same thing applies to OS/2.              I only used OS/2 2.0, and I could do this:              unsigned long hfile; /* OS/2 file handle */              rc = DosWrite(stream->hfile, (VOID *)ptr, towrite, &tempWritten);              Did this function not exist in 1.0?              If it did exist, that's all I need, isn't it?              Windows 12/13 could support a 16-bit DosWrite that writes       to a console and supports ANSI controls for both input and       output, couldn't it?              Any other existing option besides DosWrite? Did 16-bit       Windows have nothing the equivalent of that?              > > Does that run at native speed?              > No. 16-bit code is run using interpreter. Although it includes support for       > using Intel HAXM where 16-bit code is run using virtualization, it seems       > that it's not fully working yet.              My desire is to run an unkludged executable on that CM16       at native speed.              I'm just wondering what sort of things I can stick on that.       Is anyone currently using it for anything?              Some people climb mountains because they exist.              I want to exercise CM16 because it exists.              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