🚀 go-pugleaf

>Now, you _can_ use multiple TCP/IP applications, as long as they interface
>at the TCP or UDP levels.  You just need applications that will work together
>and that will operate efficiently under the Windows environment.
>

Novell's Lan Workplace for DOS comes with a suite of windows programs that
are very nice.

I highly recommend them.

They also provide a developers toolkit that provides libraries for both DOS
and windows development.

For more information, call 1-800-RED-WORD (or something like that)

Disclaimer:  I've been using a pre-release copy for a while, and it's really
great!

>I'm planning to solve the problem the following way -- A TCP/IP kernel is
>loaded as a TSR before Windows is started.  (The same TSR provides TCP/IP
>services to both DOS and Windows applications.)  Windows versions of the
>normal applications (telnet, FTP, mail, and news) are created, speaking
>to the kernel through a DLL.  The DLL handles the job of getting some
>memory mapped in the real 640K address space, copying the data to and from
>that address space, and calling the kernel to provide the protocol services.

This is how Lan Workplace works as well.

>Your dealers are going through the same steps I'm going through, except
>that they may be using some more sophisticated techniques.  I don't have
>the DDK, so I'm working based on what I can find in the SDK and a little
>info from the last chapter of _Undocumented DOS_.

>-- 
>Stephen Trier                        Work: trier@ins.cwru.edu
>Case Western Reserve University      Home: sct@seldon.clv.oh.us
>Information Network Services

Eliel Mamousette
Brown University Computing & Information Services
Eliel_Mamousette@Brown.Edu