home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!warwick!uknet!yorkohm!minster!ken
- From: ken@minster.york.ac.uk
- Newsgroups: comp.os.ms-windows.programmer.win32
- Subject: Re: TCP/IP access into NT
- Message-ID: <724346304.7050@minster.york.ac.uk>
- Date: 14 Dec 92 15:18:24 GMT
- References: <Bz3LoF.DC7@ansoft.com>
- Organization: Department of Computer Science, University of York, England
- Lines: 28
-
- Greg Kochaniak (greg@ansoft.com) wrote:
- : In article <723981859.12122@minster.york.ac.uk> ken@minster.york.ac.uk writes:
- : >James 'J' Allard (jallard@microsoft.com) wrote:
- : >
- : >I have a more thorny problem: I thought the winsock API was visible to 16bit
- : >windows apps? I have an X windows client (vista eXceed) which will talk to
- : >about 15 different transports, one of which is the winsock protocol. But I
- : >can't get it to work (I've tried "TCP" in the services control panel) -
- : >whenever I run eXceed I just get a message box moaning about "no transport".
- :
- : I don't think Vista eXceed/W is compatible with the winsock protocol yet.
- : I have here ver. 3.0.1 and an offer to upgrade to 3.2. The offer specifies
- : 15 different TCP/IP transport implemented by different companies, but does
- : not mention Winsock at all. But I would love to discover that I'm mistaken
- : about that and that eXceed/W can run under NT. Were you or anybody else
- : able to run other Winsock 16 bit application under NT?
-
- Well, I asked it to use MS DOS TCPIP, and it tried to bind to WINSOCK.DLL
- (eXceed installed this in the \EXCEEDW\MS directory). It binds to it, but
- then says "network not up" or something close.
-
- --
- Ken Tindell Internet : ken@minster.york.ac.uk
- Computer Science Dept., Local FTP site: minster.york.ac.uk
- York University, Tel. : +44-904-433244
- YO1 5DD, UK Fax. : +44-904-432708
- --
- "The Gulf War won't be like a Rambo film; it will be long, bloody and terrible"
-