Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!UMVMA.BITNET!CHARLIE From: CHARLIE@UMVMA.BITNET (Charlie Turner) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: MD-DOS/IP Message-ID: <9105011022.aa26809@louie.udel.edu> Date: 1 May 91 14:07:01 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 22 On Tue, 30 Apr 91 15:16:11 GMT Dan Revel said: >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? > Our campus (U of Mo Columbia) is site licensing this package from WiscWare. The primary application is for PCs in the student labs to telnet into the campus mainframes (CMS mostly). In my experience with MD-DOS/IP it works well although we did find an incompatibility. When telnet-ing into the host as a 3270 (TN3270) MD-DOS/IP doesn't handle 3270 nulls the way a real 3270 terminal does. This causes problems for a few applications. I reported this to the MD-DOS/IP support group but haven't received any resolution yet. Another of our campuses (UM Rolla) chose the Clarkson modified NCSA package over MD-DOS/IP. Their specific reasons were that Clarkson doesn't require CONFIG.SYS changes and Clarkson does support the BOOTP protocol for dynamically assigning IP addresses to the PCs. I haven't tried running MD-DOS/IP with Windows.