| |
VK3FBD > FBB 24.04.06 03:04l 41 Lines 1627 Bytes #999 (0) @ WW
BID : 170190VK3FBD
Read: GUEST
Subj: Re: Attention all SysOps!
Path: DB0FHN<DB0NOE<DB0GAP<DB0AAB<DB0PV<OE6XHG<OE1XAB<HG8LXL<7M3TJZ<ON0AR<
ZL2BAU<VK4TRS<VK3FBD
Sent: 060424/0152Z @:VK3FBD.#MEL.VIC.AUS.OC #:4941 [Lilydale] FBB7.00g
From: VK3FBD@VK3FBD.#MEL.VIC.AUS.OC
To : FBB@WW
Hi all Sysops
After reading Chucks bull on writing a new BBS perhaps all sysops
should
think about what would be nice to have in it and keep Chuck posted so that
he has a feel for what the "customer" really wants.
I agree with him that it would be nice to do all the things that FBB
does without the horrors of working through Port.sys and getting BPQ,
tfpcx etc running but what I would really like is a just single port
out of the bbs through a 100baseT or similar outlet and do the
conversions to other modes in external PIC or similar micro's which
would just hang off the network with their own tcpip addresses on
one side and the radio's on the other. Micro's are so cheap these
days that these sort of solutions can be implemented on a fairly
low budget.
I see this as making it easier to get the BBS written and later
configured. It also means that most of the processing load would
be shared externally and leave the rest of the PC to its own
devices. More to the point it could lead to a lot od fun for amateurs
in implementing the various interfaces for the different speeds,
radios and so on that FBB currently tries to handle internally.
Good luck Chuck with your project
73's de Tony VK3FBD
It would also make things a lot cleaner in avoiding addressing, IRQ
memory conflicts and so on when trying to interface with Windows.
73 - Tony, VK3FBD @ VK3FBD.#MEL.VIC.AUS.OC
Message timed: 11:49 on 2006-Apr-17
This message originated in Lilydale Melbourne Victoria Australia
Read previous mail | Read next mail
| |