On 8/29/06, <b class="gmail_sendername">fd0man™—The Magical Floppy Man</b> &lt;<a href="mailto:fd0man@gmail.com">fd0man@gmail.com</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>


  
  

<div></div><div><span class="q">
On Tue, 2006-08-29 at 19:34 -0600, ShadowFlare wrote:<br>
<blockquote type="CITE">
    <font color="#000000">Hmm, I'm not sure if it is really even necessary to directly support DOS programs.&nbsp; One thing I thought of that I should mention here is that Microsoft doesn't even support DOS programs at all with their latest Windows versions (Windows XP and Server 2003 x64 Editions).&nbsp; However, that isn't really a problem since there are alternatives to Windows' DOS support (which wasn't really even that great in some ways in Windows 2000 or XP to begin with anyway). 
</font><br>
    <br>
    <font color="#000000">I don't know why, but for some reason I'm thinking it would just kind of be a waste of time to implement NTVDM for ReactOS if the developers working on it would be able to work on other parts of ReactOS.&nbsp; Hmm, it might be at least somewhat worthwhile to work on a NTVDM alternate that could run on both ReactOS and Windows (possibly even x64 editions), though. 
</font><br>
    <br>
    <font color="#000000">Well, just my opinions on the matter.</font><br>
    <br>
    <font color="#000000">-ShadowFlare</font><br>
    <br>
</blockquote></span></div><div>
<br>
Doesn't NTVDM also handle WOW (Windows on Windows) sessions with 16-bit Windows applications?&nbsp; I seem to recall when I worked at AT&amp;T having (quite a few) applications that the only way they could be killed was to kill NTVDM and another process (old[something]app or something?) and then restart the application.&nbsp; In any case, there are still quite a bit of software applications that are available online that would make use of these types of subsystems—and it would be nice, I think, to continue supporting something that Microsoft does not, and improve upon it, because that would just be another point in favor of getting people to use free software.&nbsp; Right?&nbsp; :-)
<br>
<br>
&nbsp;&nbsp;&nbsp; — Mike<br></div></div></blockquote></div><br>Heh, I still think that an actual NTVDM implementation might not necessarily be the best solution, though.&nbsp; Well, if it could run on x64 editions of Windows then it would be fine, but if it couldn't, then that's why I was suggesting an alternative.&nbsp; Of course, the alternative still wouldn't have to be just for DOS programs either, it could also be for 16-bit Windows applications as well.
<br><br>Hmm, if there could be an implementation with no kernel-mode code or at least something that could somehow work when running AMD64 CPUs in a 64-bit OS, then that would be a good thing to work toward.&nbsp; Then if ReactOS was later made to support the API for Windows x64, then it could have 16-bit app support, while Microsoft's 64-bit OS doesn't. :)
<br><br>-ShadowFlare<br>