From: floydb@rpi.edu
Subject: Win-Sockets (Windows-native Network standards)
Date: Wed, 11 Nov 1992 17:18:52 GMT

In article <1992Nov11.063238.25583@microsoft.com> blakeco@microsoft.com (Blake Coverett) writes:
>>>>rick@sjsumcs.sjsu.edu (Richard M. Warner) writes:
>>>>
>>>>>Until Microsoft decides to use a multi-protocol stack for WFWG it will be
>>>>>a no go - unless you load one (e.g., NDIS, ODI, etc.) before entering
>>>>>Windows and can get the drivers to work with all the pieces.
>
>It is terrible netiquette to barge in when you haven't followed the previous
>content of a thread and so I apologize in advance, however I felt obliged
>to correct this misconception.
>
>WFW most certainly does use NDIS and as such supports multiple protocol
>stacks on the same card.  In fact it comes with two stacks (NetBEUI and
>IPX) which run concurrently when you choose NetWare support.  I have
>successfully used Microsoft's TCP/IP stack with WFW and I strongly
>suspect that QVT/NET could be persuaded to work with the NDIS packet
>driver shim.
>
>Opps, lost the attribution for this entirely:
>>To the best of my knowledge and from personal experience you can NOT
>>run two protocol stacks at the same time on the same adapter.
>
>This I'm afraid is patently false.
>

I stand/sit corrected. My experiences are from a few years ago to very
recently. I may be missing something here, but several threads on
comp.protocols.nfs seem to concur with my experiences. Newer software
and/or versions may have eliminated this problem.


>>I have read various articles about a Win TCP/IP standard in the
>>works with Microsoft et al backing it. It would seem that they are
>>looking to implement a DLL for TCP/IP calls in Windows, thus limiting
>>applications compatibility DLL calls. 
>>
>>Anyone heard anything new about this initiative?
>
>"Windows Sockets"  This is a middleware standard that defines a binary
>interface to which application programs can be developed and that can
>be provided by any TCP/IP vendor.  It is basically Berkeley sockets with
>a few extensions to facilitate Windows.  It was hashed out by representatives
>from pretty much every company involved in TCP/IP on PC platforms.  The spec
>is designed for both Win16 and Win32.  For Win16 the implementation must
>be provided by a third party (and the likely suspect are mostly doing so now.)
>With Win32 on Windows NT it is included as part of the base OS.  (Because TCP
>is on the the protocols included with the base OS.)  You can pick up a complete
>copy of the spec from the Microsoft directory on UUNET.
>
>-Blake
>-- 
>#include <std/disclaimer.h>                       blakeco@microsoft.com
>Mail Flames, Post Apologies.                      ...!uunet!microsoft!blakeco


I once got the spec from an anonymous ftp site and read it with interest. I
am not a Windows programmer so it had limited value to me. However, as a 
customer of Sun Microsystems and Microsoft and QPC (makers of QVT/NFS) I
am interested in seeing products based on a Windows-native standard. 
Regardless of how it is done, I would like to see the elimination (and 
requisite local support) of lingering DOS-Windows (e.g. Sun's telnet, ftp,
net stat, etc. are all DOS-Windows). Some things you can't even do in 
Windows (e.g. load and un-load TSR's such as pcnfslpd - PC print server deamon).

thanks
 
barry

Newsgroups: comp.os.ms-windows.apps