home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!decwrl!concert!sas!mozart.unx.sas.com!sasdxk
- From: sasdxk@skyhawk.unx.sas.com (Dave Kolb)
- Subject: Re: Getting DOS TCP/IP software to work with NT
- Originator: sasdxk@skyhawk.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <Bx9sIM.ILr@unx.sas.com>
- Date: Fri, 6 Nov 1992 01:08:45 GMT
- References: <1992Nov5.031150.12271@ucsu.Colorado.EDU> <EBROWN.92Nov5161748@bud_light.kodak.com>
- Nntp-Posting-Host: skyhawk.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 29
-
-
- In article <EBROWN.92Nov5161748@bud_light.kodak.com>, ebrown@bud_light.kodak.com (Eric Brown) writes:
- |> In article <1992Nov5.031150.12271@ucsu.Colorado.EDU> ushomirs@spot.Colorado.EDU (USHOMIRSKIY GRIGORIY) writes:
- ...
- |>
- |> I was under the impression that Microsoft and a couple other vendors
- |> (Sun and FTP Software notably) had come up with the Windows Socket
- |> specification and that that was to be the new TCP/IP standard interface
- |> rather than packet drivers.
-
- WNT has a Transport Driver Interface (TDI) that wraps "streams"
- around tcp/ip, spx, decnet etc. and the streams layer talks NDIS to
- network card drivers.
-
- I think that the Windows socket spec is at a application level and the
- lower levels are vendor dependent. Microsoft just chose to run NDIS
- at the lower levels and interfaces their TCP/IP layer ontop of
- streams and WINSOCKET applications shouldn't care.
-
- "Inside Windows NT" explains this better than I can.
-
- Rgards,
-
- --
- Dave Kolb Opinions are mine not SAS'
- SAS Institute, Inc. EMAIL: sasdxk@unx.sas.com
- SAS Campus Drive - J206 Phone: (919) 677-8000 x6827
- Cary, NC 27513-2414 USA FAX: (919) 677-8123
-
-