Subj : Re: U64 + BBS SUCCESS
To   : j0hnny a1pha
From : Bucko
Date : Thu Sep 26 2024 18:25:58

On 26 Sep 2024, j0hnny a1pha said the following...
 
 ja> 
 ja> That said, IMAGE and C-NET (maybe even C*BASE) seem to have some sort of
 ja> add-on propietary echo networking functions. I wonder if that could be
 ja> used to import/export to the FTN standard...? That would be DOPE

The Image network is not FTN compatible. If anyone remembers Frank from SCINet 
he was going to write a go between to do just that take the FTN packages and 
convert them to something Image could read, and vice versa.. Only issue with 
FTN networks and the C64 unless you are running at U64 at 48mhz you will find 
the message packages are just to large to process. Running on a Lt Kernal 
system the Machine is running at 1mhz. The HD is fast but the machine is not. 
When I was running the NISSA network back in the early 90's as Administrator, 
we had a break down of one of the legs of the network (Back then the network 
ran from BBS to BBS not a HUB style network like we have now) and I got a 600+ 
block file of message base posts. That is equal to just about a full 1541 disk 
which is 330k it took 32 hours to process the file thus rendering the BBS 
useless as the BBS processes live and not in the background. I have had times 
when I would get 5 meg message packages in Fido and on my PC it takes seconds 
to process it with Mystic. Even at 48mhz that would take probably a couple of 
hours to process.

So can it be done? Sure! Should it be done? Unless you are going to keep the 
messages down to a minimum no..


         |11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

.... The caterpillar does all the work but the butterfly gets all the publicity

--- Mystic BBS v1.12 A48 (Linux/64)
 * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (1337:3/102)

.