<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16587" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Jay:</DIV>
<DIV> </DIV>
<DIV>Not sure exactly what you are doing and how my answer will impact what you are doing, but here is my 2 cents. If there is stuff out there to deal with these old computers, we shouldn't remove it just because they are old. </DIV>
<DIV> </DIV>
<DIV>I still have Modula-3 code that is running on old computers. Indeed, the government tends to have some interesting requirements to keep alive certain systems that use old technology. I have delivered many systems over the course of my career whose actual lifetime was much longer than what anyone projected in the beginning. If we remove support for the old stuff, then we shoot ourselves in the foot for any type of support on these old systems. </DIV>
<DIV> </DIV>
<DIV>Indeed, I've recently been approached about making some changes to a system that I first developed back in the late 1990's. It is still around and working. One of the system components has been upgraded and they want me to make software changes to let the Modula-3 code work with the new component. This software controls and monitors satellite radio communications systems. </DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy<BR><BR>>>> Jay <jayk123@hotmail.com> 2/11/2008 4:35 AM >>><BR>ps: I will point out that NT 3.1 doesn't have have good compatibility with things like VMware or Virtual PC (or vice versa), not sure it will even run on modern hardware (the problem is probably these virtual machines exposing too much?)<BR> <BR>also what processors do people care about?<BR> 386? <BR> 486? <BR> Pentium I? <BR> (Pentium's with the FDIV bug? I still see remnants of the workaround for that..)<BR> <BR>The newer processors have some nice seeming instructions. Like read timestamp counter, interlocked compare exchange 64, interlocked increment/decrement (on circa 386, those Win32 functions don't return the new value, only <0, 0, or >0), conditional mov, etc. And there is MMX, XMM (SSE?), SSE2/3/4..the instruction set advances don't seem to ever stop.. Nice thing about AMD64 is it establishes a new baseline.<BR> <BR>I can't claim to have done any profiling with or without these instructions used.. nor that the integrated backend will ever advance in these areas..<BR> <BR> - Jay<BR></DIV>
<BLOCKQUOTE>
<HR id=EC_stopSpelling>
From: jayk123@hotmail.com<BR>To: m3devel@elegosoft.com<BR>Date: Mon, 11 Feb 2008 09:15:50 +0000<BR>Subject: [M3devel] FW: [M3commit] CVS Update: cm3<BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass EC_body.hmmessage
{font-size:10pt;font-family:Tahoma;}
</STYLE>
Aren't we better off with more VAR parameters and fewer UNTRACED REFs?<BR>That way more interfaces/modules can be "safe", as this one changed?<BR> <BR>(Does anyone care about NT 3.1 or, gasp, Win32s compat? :) )<BR>(Maybe a "DJGPP" target will satisfy? :) )<BR> <BR> - Jay<BR><BR><BR>
<HR id=EC_stopSpelling>
<BR>> Date: Mon, 11 Feb 2008 10:13:41 +0000<BR>> To: m3commit@elegosoft.com<BR>> From: jkrell@elego.de<BR>> Subject: [M3commit] CVS Update: cm3<BR>> <BR>> CVSROOT: /usr/cvs<BR>> Changes by: jkrell@birch. 08/02/11 10:13:41<BR>> <BR>> Modified files:<BR>> cm3/m3-libs/m3core/src/time/WIN32/: Time.m3 <BR>> cm3/m3-libs/m3core/src/win32/: WinBase.i3 <BR>> <BR>> Log message:<BR>> at the expense of NT 3.1 compatibility use GetSystemTimeAsFileTime<BR>> instead of GetSystemTime + SystemTimeToFileTime<BR>> <BR><BR><BR>
<HR>
Need to know the score, the latest news, or you need your HotmailŪ-get your "fix". <A href="http://www.msnmobilefix.com/Default.aspx" target=_blank>Check it out.</A> </BLOCKQUOTE><BR>
<HR>
Climb to the top of the charts! Play the word scramble challenge with star power. <A href="http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan" target=_new>Play now!</A> </BODY></HTML>