home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.misc
- Path: sparky!uunet!munnari.oz.au!mel.dit.csiro.au!mineng.dmpe.CSIRO.AU!dmssyd.syd.dms.CSIRO.AU!metro!usage!news
- From: troy@cbme.unsw.EDU.AU (Troy Rollo)
- Subject: Re: TCPIP DLLs for Windows: a summary (Correction)
- Message-ID: <1992Sep3.033317.27940@usage.csd.unsw.OZ.AU>
- Sender: news@usage.csd.unsw.OZ.AU
- Nntp-Posting-Host: strummer.cbme.unsw.edu.au
- Organization: University of New South Wales
- References: <715355419.26604@minster.york.ac.uk>
- Date: Thu, 3 Sep 1992 03:33:17 GMT
- Lines: 24
-
- > From schoen@tsfsrv.mitre.org
- >>Yes, Novell's LAN Workplace for DOS provides a TCP/IP stack, a Windows DLL
- >>that you can use for your applications, and several other goodies; however,
- >>you need to be on a LAN running Novell Netware. If that's not a problem,
- >>we`ve been using this product to develop applications for Windows. They
- >>provide a DLL called WLIBSOCK that I believe is conformant to the winsock
- >>protocol.
-
- Two corrections to this one:
-
- 1) You don't need to be on a LAN running Novell Netware,
- although if you are running a LAN that isn't NOVELL
- which must be run concurrently, you will probably
- have to juggle a variety of Clarkson, NDIS and ODI
- drivers with some driver that converts one to the other.
- (Basically you are likely to need to get NDIS and ODI
- running at the same time)
-
- 2) WLIBSOCK.DLL isn't Windows Sockets conforming, however all
- the entry points have a fairly logical behaviour which
- is implied by their names.
- --
- __________________________________________________________________________
- troy@cbme.unsw.EDU.AU Overworked, overcommited and always multitasking.
-