Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!ncar!gatech!mcnc!beguine!bbs.acs.unc.edu
From: Kin.Fung@bbs.acs.unc.edu (Kin Fung)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: MD-DOS/IP
Message-ID: <3653@beguine.UUCP>
Date: 7 May 91 04:39:20 GMT
Sender: usenet@beguine.UUCP
Organization: Extended Bulletin Board Service
Lines: 26

In Article 2965 (58 more) in comp.protocols.tcp-ip.ibmpc:
dan@lclark.UUCP (Dan Revel) said:

> Subject: MD-DOS/IP
> Keywords: PC/IP
> Date: 30 Apr 91 15:16:11 GMT
> Reply-To: dan@lclark.UUCP (Dan Revel)
> Organization: Lewis & Clark College, Portland OR
>
> We are considering getting the University of Maryland Communications Package
> (MD-DOS/IP) to provide TCP/IP network support for campus PCs.  Does anyone
> have experience with this package and care to comment on it?  Will it work
> with Windows?

The current MD-DOS/IP is not designed to run with Windows, though that is
rumored to be in the planning for future releases.  i am able, however, to
run any one tcp application inside Windows 3.0 without much crashing.
However, any time you have more than one tcp application running, you sure
invite crashing.  A key procedure is to start "kstart up" before you invoke
windows.  You do not want MD-DOS/IP software to expand their memory
requirements after Windows is started.  --kin fung, rtp NC
--
=============================================================================
	Extended Bulletin Board Service, Research & Development
Office of Information Technology, University of North Carolina at Chapel Hill
	      internet: bbs.oit.unc.edu or 128.109.157.30