home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!srg!rharmon
- From: rharmon@uucp (Bob Harmon x4964)
- Subject: Re: POSIX interface/Access to WIN32 calls
- Organization: /home/server/rharmon/.organization
- Date: 28 Jan 93 09:53:16
- Message-ID: <RHARMON.93Jan28095316@muon.uucp>
- In-Reply-To: alistair@microsoft.com's message of 28 Jan 93 00:52:40 GMT
- References: <1993Jan22.232051.28262@microsoft.com> <727810939snz@chrism.demon.co.uk>
- <1993Jan25.190746.4106@mkseast.uucp>
- <1993Jan28.005240.10823@microsoft.com>
- Sender: news@srg.srg.af.mil (Usenet news user)
- Lines: 25
-
- In article <1993Jan28.005240.10823@microsoft.com> alistair@microsoft.com (Alistair Banks) writes:
-
- Win32, OS/2 & Posix are the only subsystems in Windows NT - the Win16
- and MS-Dos support are virtual machines written to use the Win32
- API (plus some helper functions) - they're not subsystems in of
- themselves.
- POSIX compatibility and upwards compatibility from Windows are
- mutually exclusive options....
-
- #include <std.grovel>
- Could someone explain the difference between a 'subsystem' and a DLL?
- A had thought POSIX compatibility on NT would be a library that
- translated POSIX to NT microkernel calls. Then merely linking
- with POSIX and Windows would achieve the desired result. This seems
- to be naive.
-
-
-
-
-
- --
- rharmon%srg@uunet.uu.net |
- Robert B. Harmon ms: 5-230 | Ahhhhhhh....Choo!
- Arinc Research: 2551 Riva Rd |
- AnnaInvalid MD 21403 |
-