| |
SQ6BOT > PSBBS 01.07.96 14:36l 68 Lines 2601 Bytes #-10328 (0) @ WW
BID : U66SR6BOX001
Read: UA6HJQ GUEST
Subj: Re: PSBBS
Path: DB0AAB<DB0FSG<DB0IGL<DB0KCP<DB0ZKA<DB0LX<DB0RBS<DB0SEL<DB0ZDF<DB0AIS<
DB0SIF<DB0SON<DB0MAK<DB0PV<DB0WGS<OE3XSR<OK0PBX<SP6KBL<SR6BOX
Sent: 960630/1300z @:SR6BOX.#WRO.POL.EU [BayCom-Mailbox [Wroclaw]] BCM1.37b
From: SQ6BOT @ SR6BOX.#WRO.POL.EU (Zipu)
To : PSBBS @ WW
DG9EP wrote:
> PMFJI, but before you start go ahead, please consider:
^^^^^
What does this abbreviation mean?
> * you want to write a BBS? so why do you start with the ax25-connectivity?
> wouldnt it be better to start with the bbs system itself? Or, why at all
> you want to manage the hardware by your own? There ars so much hardware in
> use (DRSI, SCC*, BayCom-SCC, KISS, SMACK, TNC2, Vanessa, FALCon, TNC3 ...)
> you cant support them all by your own!
> Same to protocoll extension? Do you want to write additional code for DAMA,
> Optima, MOD 128 (all are ax25-extension) or as you mentioned for TCPIP?
> That cant be done. So why do not use a layered-concept like PC/Flexnet (i
> write LIKE! not use :-) ) because it much more easier to maintain. The
> BayCom-Box uses it now. And the interface is very easy:
>
> APPLICATION (e.g. BBS, Infobox, Convers....)
> -----------
> FlexKernel
> -----------
> DeviceDrivers
I'm looking mainly at JNOS. But in sources which I wrote uptill now
there is a kernel and it communicates with functions that support
several devices (incl. loopback) - they run as separate processes.
You'll see it next time I'll send sources - when loopback will be complete.
I think it would be easy to add command like 'attach devicedriver'
but I need some descriptions of these...
And the application level - now it's only one process called ex.
"BBS user: SQ6BOT", but this one can fire up many others...
> There are many DeviceDrivers availble now, including some for Soundblaster
> for 9k6 FSK !!!
Do you have any specifications of such drivers? How to communicate with them?
I know absolutely nothing about them... >8-(
> * Be plattform independent. A BBS do not need a User Interface (the sysop can
> log in like a user via localloopback), so a programm written in C can be
> ported to any system (yes, some #ifdef's but not many). And times are
My DisplayScreen() function should be changed - it's really unasthetic
and device dependent ;((((((
Anyway there is AX.25-loopback interface, that will use the same protocol
procedures as ex. KISS interface and there will be no difference if it's
sysop connecting via loopback or user connecting via radio link.
> changing: DOS will not stay forever; someday there will be maybe a System
> like Linux at no cost with superior easy install...
I hope so... ;)
> or maybe you'll receive
> requests to run psbbs under windows :-)
Oh, noooooooo........ ;-)
73, Peter
Read previous mail | Read next mail
| |
