Kicking the programming in TrueSpace can around 2005-06-02 - By KMKrieger
Back
Lars, thank you for this info. Ironically, I undsertand the part about
M$'s .net being it's own version of, and evidently therefore replacement
for, Sun's JavaVM. That's the first thing anyone has said about it that I
understood =:-o !!
So if I do upgrade my machine (and tS), I can at least try W2KPro and see
how it handles the additional RAM (I'm looking to be able to have 4GB,
since I've heard it operates best in pairs).
Re: the "open source" OS's to which you referred - do any run Window$
programs, specifically tS? I never heard of these so I'm wondering whether
they can handle the new GB-lvel RAM and new video drivers (such as for
NVidia 6000 series)...
I get so fed up with being TOLD that I should and *will* <!!> love the XP
interface; I've used it, and I *loathe* it. Additionally, the person whose
computer I'd used it on had continual problems with XP - to the extent of
just putting the XP machine back into the packing box, and going back to
the old machine! So I don't believe the tales of how stable it supposedly
is - that was said about *every* version of Window$, and it has always
turned out to be just smoke'n'mirrors...which is why I'm wondering about
other OSes.
- Kris
At 09:36 AM 02-06-05, Lars Nilsson wrote:
>On 6/2/05, David Stubbs <hawksridge@(protected)> wrote:
> > Although - Win 2000 and the like is .net capable - to what degree I do not
> > know when compared with XP ?
>
>Quoted from the download page[1] for the .NET framework redistributable
>package:
>
>[snip]
>System Requirements
>Supported Operating Systems: Windows 2000, Windows 98, Windows ME,
>Windows NT, Windows XP
>
>Microsoft Windows NT 4.0 requires Service Pack 6a.
>[snip]
>
>"Supported operating system" means .NET programs will work as expected
>on these operating systems. Notice how ME, despite being a total
>abomination, is supported. None is considered better as far as
>supporting .NET is concerned. Normal hardware drivers (not .NET
>related) would IMHO play a greater role in running a .NET program on a
>particular OS (particularly thinking of graphics drivers).
>
>Having clarified what operating systems are capable of running .NET
>programs (using Microsoft's .NET framework, see below for
>alternatives), it should also be said that the .NET framework is
>pretty much Microsoft's answer to a Java VM and its associated
>libraries. An interpreter (a just-in-time compiler and related
>technologies are involved) runs your .NET programs, just like a JVM
>(from Sun or others) interpret/just-in-time-compiles Java class files.
>
>Final words, .NET does not replace any particular operating system, or
>make it impossible to use on the common platforms available. Also,
>since Microsoft went through the trouble of standardizing .NET to a
>certain extent, it has presumably also made life easier for those that
>reverse-engineer/follow-the-spec when implementing a new
>.NET-compatible framework (like Mono[2] and DotGNU[3]). The
>open-source varieties of .NET have no problem whatsoever (not counting
>bugs and unimplemented functionality) running .NET programs compiled
>with Microsoft tools. They also function quite well on the various
>open-source operating systems, and MacOS X, etc.
>
>Lars Nilsson
>
>[1]
>http://www.microsoft.com/downloads/details.aspx?FamilyID=262D25E3-F589-4842
-8157-034D1E7CF3A3&displaylang=en
>[2] http://www.mono-project.com/Main_Page
>[3] http://www.dotgnu.org/
>
>__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ______
>****************************************************************************
>********
>This message has been checked for all known viruses by the Cable & Wireless
>E-mail Virus Protection service, powered by MessageLabs.
>
>To purchase this service, please contact your Cable & Wireless Account
>Manager.
>****************************************************************************
>********
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ ______
****************************************************************************
********
This message has been checked for all known viruses by the Cable & Wireless
E-mail Virus Protection service, powered by MessageLabs.
To purchase this service, please contact your Cable & Wireless Account
Manager.
****************************************************************************
********
|
|
