home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!bcm!lib!oac.hsc.uth.tmc.edu!snewton
- From: snewton@oac.hsc.uth.tmc.edu (Steven E. Newton)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: FTP & Internet Packages
- Message-ID: <8371@lib.tmc.edu>
- Date: 7 Jan 1993 14:57:19 GMT
- References: <2935457652.3.p00197@psilink.com>
- Sender: usenet@lib.tmc.edu
- Organization: UT Health Science Center Houston
- Lines: 26
- Nntp-Posting-Host: oac.hsc.uth.tmc.edu
-
- In article <2935457652.3.p00197@psilink.com> guthery@slcs.slb.com writes:
- >Recently Mark Bixby posted a list of Internet software packages that
- >are compatible with FTP's PC/TCP TCP/IP stack. The list included
- >trumpet, nupop, dosgofer, oacwais, and achied. At about the same
- >time I sent a query to support@ftp.com asking if they had such a list.
- >The reply I got from FTP was that all these packages would have to
- >be rewritten to work with FTP's TCP/IP.
- >
- >Anybody know the real story? How *DOES* one integrate FTP's
- >software, the Clarkson drivers, and these packages? A config.sys
- >and autoexec.bat example and/or a diagram would be greatly appreciated.
-
- As the programmer who ported dosgofer (A DOS port of the unix gopher),
- oacwais (a PC/TCP port of UNC's Novell wais client), and archied ( a
- simple patch for the standard archie client), I can unequivocally state
- that the three packages all work with PC/TCP versions 2.04, 2.05, and
- 2.11. I'm a bit miffed that the folks at FTP software were ignorant of
- these clients, and in fact I'm sending a copy of this to them.
-
- Steven E. Newton
-
- --
- + + + + + + + |snewton@oac.hsc.uth.tmc.edu
- I can hear you well, |Nobody else speaks for me,
- George Orwell. |and I speak for no one else.
- | + + + + +
-