Hey Bo!

Nov 12 22:15 03, Bo Simonsen wrote to Maurice Kinal:

 BS> BUT no one that me has look at it, and I do not have the fully 
 BS> understand for telnet.. But noone seems to take their time just 
 BS> looking at it! It really makes me crazy.

Sure.  I'll look as long as you're not in too big a rush.  I am still
trying to work out a viable way of encorportating some of this into where
I'd like to see it go, or at least play with it to see if I even can go
there, wherever there is.  Like I said, I don't have a phoneline or any
serial communications going other then a mouse that I hardly use.  :-/

 BS> Yes but I want filetransfer in maximus to work, cost what it has to 
 BS> cost. I don't care if it's kermit, xmodem, etc.

I did get kermit to work but as a standalone as I still don't have a Linux
based Maximus going yet.  Once I can get the menuing working right then I
think the rest, including file transfers, should be quite doable, maybe
even zmodem.  I am still not sure how that could be tested to a remote
though but if I can get something suitable working as far as menuing going
then perhaps it will be easier to convince at least one "local"
to try it.  How much zmodeming do you do and is it comparable to other
methods?

 MK>> As for Maximus I'd love to put a text based BBS up but have no need
 MK>> for serial communications or waiting for caller screens.

 BS> Maximus/UNIX doesn't require that.

Then why are we worried about it?  Can I safely remove or ignore the source
dealing with it?

 BS> At the time I don't care about Win32, etc. I just want the 
 BS> filetransfer working on Linux over Telnet.

Okay.  What do you propose?  Do we need a networking library and build a
proper utility for that or do you have another plan in the works?  As far
as I know the standard telnet doesn't handle file transfers on it's own,
however I have seen an example perl script that used 'cat' to transfer a
file using telnet.  The problem with that would be that the remote could
handle such a scheme.

 BS> I wrote a 
 BS> Modem-communication module yesterday, which I might test tomorrow (I 
 BS> were setting BTXE up earlier today, so it might work with Max).

Now this sounds like a plan!  I don't use BTXE myself but if it can be made
to work with that then it seems like it could be modified or outright
written for a Maximus port.

 BS> What are you waiting for? Join the maximus developing. I know you are 
 BS> a C programmer, 4 eyes is better than 2..

I am *not* an anything programmer, but have written C code.  Both for Unix
and DOS but very little of it had anything to do with BBSing.  I did once
write an online database utility for a DOS based Maximus but that was a
long, long time ago.  I am game though and have said so.  I don't think I
can be of much help with any portablilty of code to anything other then
Linux though, gcc in particular as that is all I use in the way of a
compiler.

 BS> If no-one is developing on the project, because I don't want it to be 
 BS> a one person project, so if SOMEBODY not commits anything I would not 
 BS> be developing on it 2 months more..

I hear you.  It won't be the first or the last time that sort of thing
happens.  The world will not come to an end but I agree that it would be
nice to see a future for BBSing.  I already said I will help in whatever
way I can but am content to leave portablility of code to those who are
better suited to that sort of thing.  I currently only have Linux running
and it looks like it is here to stay for the forseeable future.

 BS> IF we could get the dirt working, afterwoods we could make it 
 BS> better..

Sounds good to me.  Where do you suggest I start?  I am thinking that I
need to get menuing working properly and then take it from there.  Squish
seems to be behaving itself.  :-)

Life is good,
Maurice

--- Msged/LNX 6.1.1