Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!oliveb!pyramid!hplabs!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: multiplexing interfaces (was 'ethernet over pcnet')
Message-ID: <8807011952.AA01024@vax.ftp.com>
Date: 1 Jul 88 19:52:47 GMT
References: <8807011304.aa24836@Louie.UDEL.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25


   From: Jim Howard <KGJHH%ASUACAD.BITNET@cunyvm.cuny.edu>

   How much additional memory do these multiplexing drivers use? In many LAN's
   memory can be pretty tight unless you add expanded or extended memory and
   move some drivers or TSR's there (at a fair amount or additional cost).

Our PC/TCP product comes in two versions:  In 1.1, the entire protocol
stack is linked into each program (like PC-IP), and so the only permanent
memory usage is for the two device drivers that hold the configuration
(about 2K bytes).  In 2.0, the TCP/IP has been moved into a TSR module,
which is about 88K in the current production version (2.02).  Say 90K
for 2.02, including the configuration device drivers.  More is needed when
a TCP/IP utility is in use.  Of course, our TSR can be unloaded, but this
is still cumbersome.

We have been selling both versions since late last year, and plan to
continue selling them side by side, because each has its benefits:  The
disk-resident version is aimed at people concerned with memory issues,
and the TSR for people who want things like RFC-conforming NETBIOS,
where the TCP/IP needs to be shared amongst multiple programs.  I am
also working on making 2.03 smaller, but it won't be dramatic...

James VanBokkelen
FTP Software Inc.