gli@secola.Columbia.NCR.COM (George Li) (08/24/89)
I have a PC TCP/IP application written in a Microsoft 386 windows environment. So far, I haven't had too much luck getting this program to communicate reliably with a NCR Tower based server. Has anyone out there in netland had any luck writing PC TCP/IP applications in a windows environment? If so, were you able to multitask with another windows application and what pc package did you use? I am using the FTP software native mode library; the socket library definitely doesn't work (according to ftp support folks). Thanks! -- George Li gli@Columbia.NCR.COM ...gatech!ncrats!ncrcae!ncrsec!SCRM2!george
LANDON@ENR.Prime.COM (09/01/89)
This is a short thread from comp.windows.ms which should help answer your question. /* Written 2:52 pm Jul 15, 1989 by usenet@cps3xx.UUCP in ENR:comp.windows.ms */ /* ---------- "MS-Windows and networking software" ---------- */ Over the past several months, I have seen a few postings describing how it is impossible to run networking applications under MS Windows. Several people found various networks incompatible with Windows, evidently due to Windows' habit of stealing the timer interrupt. Well, I have found that Windows and the networking kernel from FTP Software, Inc. get along fine. I have been able to run several copies of TNGLASS (dumb but well-behaved TELNET implementation that comes with the TCP/IP suite from FTP Software) simultaneously, each in its own window, with no problem. This is under Windows/286 v. 2.10, and FTP Software's PC/TCP version 2. (I've heard that versions 1.x of FTP Software's stuff don't get along with Windows.) FTP Software's Development Kit for DOS includes a socket library; I assume this means one could write socket applications under Windows. I hope to test this assumption soon; meanwhile, I'd like to hear from anyone who knows more about this. Mark Riordan Mich State Univ riordanmr@clvax1.cl.msu.edu /* End of text from ENR:comp.windows.ms */ /* Written 11:08 am Aug 12, 1989 by LANDON@ENR.Prime.COM in ENR:comp.windows.ms */ >Well, I have found that Windows and the networking kernel from >FTP Software, Inc. get along fine. I can verify this with Windows/386. Seemed MicroSoft nor FTP could predict whether Windows/386 would work at all within a Windows application. FTP said that it wasn't possible to run their Internet applications from a DOS Window in Win/386. This is due to applications running in a new virtual machine (DOS Window) not being to use the FTP resident kernel correctly (though TSRs are supposed to be replicated in new virutal machines.) The question was whether a Windows application coming up in the first virtual machine would operate correctly. The answer is yes - I've created a client which can talk TCP or UDP from a Windows/386 application. >FTP Software's Development Kit for DOS includes a socket library; >I assume this means one could write socket applications under Windows. It is true, I've tested it. I haven't done extensive application programming to really work it over, but have done enough to verify that it works. Landon Cox landon@enr.prime.com /* End of text from ENR:comp.windows.ms */