Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!purdue!bu-cs!bloom-beacon!primerd!ENI!ENR!LANDON
From: LANDON@ENR.Prime.COM
Newsgroups: comp.windows.ms
Subject: Re: MS-Windows and networking software
Message-ID: <237700001@ENR.Prime.COM>
Date: 12 Aug 89 11:08:00 GMT
References: <3769@cps3xx.UUCP>
Lines: 25
Nf-ID: #R:cps3xx.UUCP:-376900:ENR:237700001:000:1074
Nf-From: ENR.Prime.COM!LANDON    Aug 12 11:08:00 1989


>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