Hello Bob.

03 Jul 03 22:57, you wrote to me:

 RT>> That is understood, also as Bob mentioned Maximus has its own
 RT>> user authentication, and user data base, so this is not really a
 RT>> requirement, and I hope he is correct, in that Bink XE can handle
 RT>> a hot commport from mgetty or similar.

 BJ> Guess I'm going to have to dig out the BinkleyTerm 2.60 documentation
 BJ> and see if I can find the way to set Bink up to receive a hot comm
 BJ> port....  Or find that I'm remembering some other (old) package......

Hmmm ..., I will probably also dig out the BinkleyTerm documentation 
sometime, but after completing my current task of building a clean system to 
play with Maximus/Squish on, just too many clashes with MBSE BBS/BinkD, that 
I don't want to have to fix, before being able to play with Maximus. They are 
fixable, just that I don't like some of the fixes, and would rather not 
implement the others, on my BBS system.

 BJ> Unfortunately, for some  of my thoughts -- which include Max running
 BJ> under mgetty, Wes is correct....  Max won't run in that environment
 BJ> any time soon....  I keep forgetting about the console side of
 BJ> Max.....  Once we have other things working, I do have a trick up my
 BJ> sleave that I want to try thou that might allow for mgetty to
 BJ> work.....  But it basically tosses the console side of max to the bit
 BJ> bucket.....  With out maxpipes working that will leave max running
 BJ> blind to the sysop.....

I also would prefer the BBS to run under mgetty/ifcico, or a varient thereof, 
but I also understand/agree with Wes, that Max won't run/function in that 
enviroment, especially due to cross platformand backwards compatability 
considerations.

Also, I don't have much appreciation, for the thought that has just occurred 
to me, that the "Maximus" developer group, might run into the need of 
"adopting" and developing the BT XE code, to achieve the cross platform 
goals. :-((

Russell

--- GoldED+/LNX 1.1.4.7