🚀 go-pugleaf

In article <905799824snz@dsl.co.uk>
           bhk@dsl.co.uk "Brian {Hamilton Kelly}" writes:

> In article <905629239snx@ogham.org> robm@ogham.org "Robert Mortimer" writes:
> 
> > Have you tried cispa /* I think that's what it was called */[2] I never
> > had any luck getting cFos working but cispa did the job quite nicely.
> > 
> > [2] *rummage* nope it was ISPA, which comes with instructions for KA9Q
> 
> Umm, might one see the results of your rummaging, please?  (I.e. URLs or
> whatever.)  Is there an OS/2 version of [c]ispa?

Robert's memory isn't all that bad. There are two versions of this
ISDN packet driver. One is called ISPA.EXE and requires CAPI 1.1.
THe other one is called CIPA.EXE and requires CAPI 2.0. The last time I
looked current versions where to be found at

<URL:http://www.biochem.mpg.de/~heha>

The author is Herbert Hanewinkel <URL:mailto:heha@biochem.mpg.de>.
The software is distributed as shareware (DEM 70). I have tried ISPA on
my Multiuser DOS machine but I wasn't satisfied with the results. That
had nothing to do with ISPA or Elsa's CAPI 1.1 or the DIS suite but
rather the combination of the three in the same small conventional 
memory space. NET.EXE failed me every once in a while when it ran out
of memory retrieving/sending mail and fetching news at the same time.
Perhaps OS/2 provides more conventional memory to this combination.

I now have setup the DIS-suite on the Multiuser DOS machine with a packet
driver for the ethernet board. I have configured NET.EXE to use the Linux
machine as the gateway/nameserver/smarthost [1]. The packet driver for the
NE2000 board occupies only a few kB, as opposed to (I think) 100 kB for
the CAPI TSR and 80 kB for ISPA [2]. I can now easily accomodate lots
of mail and news flowing back and forth without memory problems.

The Linux machine has direct support for the ISDN board; it is compiled
into the kernel (in a compact HiSax-driver) and also 'conventional
memory' isn't really an issue with this 32-bit OS. This won't surprise
an average OS/2 user. I also have this dialing daemon...

In other words: the simple solution in my case was to simply 'add more
hardware [3]' to solve the problem.

[1]  Well, I'm still reading the bat book and haven't yet achieved
     the 'perfect' sendmail configuration.
[2]  Sorry, no detailed figures anymore. It was a while ago. However,
     I recall that CAPI 2.0 and CIPA made memory problems worse... :-(
[3]  I happened to have (well, ok, I bought) a P120 with 80 MB RAM
     and 1 GB disk. However, I am quite confident that a more modest PC
     would be more than enough; almost any old clunker would do. I now
     enjoy an uptime of some 48 days and almost transparent access to
     the Demon.
     
--Peter Fokker