home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.win32
- Path: sparky!uunet!microsoft!hexnut!jallard
- From: jallard@microsoft.com (James 'J' Allard)
- Subject: Re: TCP/IP access into NT
- Message-ID: <1992Dec15.213340.29432@microsoft.com>
- Date: 15 Dec 92 21:33:40 GMT
- Organization: Microsoft Corporation
- References: <1992Dec07.173823.10833@microsoft.com> <723981859.12122@minster.york.ac.uk>
- Lines: 22
-
- In article <723981859.12122@minster.york.ac.uk> ken@minster.york.ac.uk writes:
- >James 'J' Allard (jallard@microsoft.com) wrote:
- >:
- >: Then, from Windows Terminal (or possibly other terminal emulators supporting
- >: alternate COM drivers), do Settings->Communications->Connector and
- >: choose TELNET. The telnet> prompt should appear in the terminal window
- >: allowing standard telnet commands to be entered. "?" will give you a list
- >: of commands supported.
- >
- >I discovered all this playing around with the telnet and terminal stuff. But
- >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".
-
- We *will* offer Windows Sockets 16-bit support under the final release of
- Windows NT. This support was not fully tested to make it into the October
- beta/SDK. You should be able to use eXceed in future releases of Windows
- NT without problem.
- --
- _______________________________________________________________
- J. Allard jallard@microsoft.com
- Program Manager of TCP/IP Technologies work: (206)882-8080
- Microsoft Corporation home: (206)860-8862
-