Quote:
Originally Posted by DMcCunney
Thanks for the clarification. MSDOS code would present challenges in porting to an NT environment.
|
Well, it didn't really have to deal with DOS code at all, since NT was written by a few VAX programmers.

And it didn't run on top of the Win32 subsystem, but parallel to it. That was actually it's biggest limitation in the initial releases -- it couldn't easily talk to the Win32 subsystem. The Interix subsystem could, for example, do symbolic links. But the Win32 subsystem couldn't interpret them. And if you had an application in the Interix subsystem, it was isolated from Windows, making it difficult to pass data back and forth.
Quote:
I ran Services for Unix at one point, and also ran Cygwin and AT&T's UWIN package that Dr. David Korn developed. These days I run a set of the Gnu utilities built "native" for Win32 with MinGW. I never encountered the early OpenNT flavor.
|
I've run most of those at one time or another, but finally gave the whole thing up as irrelevant to the real world.
Quote:
I've looked at PowerShell, but haven't done a lot with it so far. I'm intrigued by the notions of manipulating fully qualified .NET objects in scripts, but thus far haven't needed to do it.
|
PowerShell is now my primary language. At one point, I "thought" in Korn Shell, but that has changed. Not without a struggle. But the ability to pass objects down a pipeline is just so compellingly powerful.
Oh, and FWIW -- my PowerShell editor is gVim.
______
Dennis[/QUOTE]