Telegard - Frequently Asked Questions

Telegard
Information
Resources
Download
File Archive

Other Software
fks Software

1.1 - What is the latest public version?

The latest release is always available from:

1. ftp://telegard.net/pub/tg

1.2 - What is the difference between gamma, beta and final releases?

Gamma releases are testing releases for the general public. They are used to test new features on a broader scale, and for soliciting comments on features to be included in future releases. These versions will be marked V.VV.g## where .g## is the gamma release number. NOTE: Gamma releases are _not_ supported software.

Final releases are for public consumption. The releases have been tested through several stages and are as bug-free as possible at the time of release. Final releases are supported (to the extent that us _volunteers_ can manage).

1.3 - When, or what is the next scheduled release?

Telegard 3.10 marks many changes not only in the direction of the software, but also the 'under the hood' code (the stuff that you can't see, but can feel)--it will be more powerful, more user friendly, and hopefully faster than previous versions.

We are finally gearing up towards the 3.09.g1 gamma release. Please keep your eyes on our site as it will be updated periodically with news regarding 3.09.g1!

The only information (for public eyes) with regards to new features is:

1. There will be a new scripting language (3.09.g2)
2. There will be better user interface options (3.09.g1 & g2)
3. There is a new file system engine--faster, and more extensive (3.09.g1)
4. Versions for OS/2, Win32 (95/NT) and Linux are being _explored_ (3.09.g2)

1.4 - Telegard 2.7+ source code?

The Telegard 2.5g source code is floating around on various BBS and internet sites around the world. I am not responsible for this source code. Infact, I had nothing to do with Telegard when this source code was first developed (I wasn't even a SysOp at the time!). The legality of this source code is also in question--only one of the two authors released the code, without permission--and while no legal issues have been raised in the past, I still don't suggest its' use.

The old Telegard 2.5g source code is not only outdated (7+ years now), it is poor in implementation, and would require a heavy re-write of the core routines to make the system capable of handling any of 'todays' BBS concepts. I urge many of you to just *stay* away--it's not worth the trouble, and potentially worth many problems.

1.5 - Telegard & the Internet?

Internet Email & Newsgroups are easily integrated into your current system. To do this, you will need:

1. A source for your internet email & newsgroups--this could be from a feed such as Fidonet (several local networks provide internet feeds), from a service provider, or from wherever else you can get a source. If the service is FTN based, you can use a FrontEnd mailer to get you mail--otherwise you may need special dial-in tools (UUCP), or special scripting (to download from your source).
2. Software to convert the mail from the source format, to a format which can be handled by Telegard message areas. Telegard uses Squish and JAM as standard message formats. More often than not, your Internet mail & newsgroups will not be a format directly compatible with Telegard--conversion utilities can take the source format, and either toss it DIRECTLY to the JAM or Squish areas, or can toss the mail to an intermediate step (*.MSG, *.PKT) which can then be tossed into the JAM or Squish areas by a standard mail tosser. While I haven't explored the conversion process, both GIGO and WaterGate are products which may do the trick. If you get your mail from a FTN source, the files are likely already in .PKT format as standard netmail/echomail would be--you then only need a mail tosser (FastEcho, Gecho, Fmail, etc.).

Inbound Telnet has more requirements because of the nature that a telnet session is a dedicated communications session. You will need:

1. A dedicated connection to an internet service provider (ISP). (this can be a dedicated dial-up connection -- not neccessarily having to be ISDN / T1 type connections). What I mean by dedicated is that you will connect your system to the account, and it'll run indefinately (it don't kick you off after an hour--an unlimited usage internet connection by definition). With the new cable technologies coming out, it could also be a cable connection.
2. A static IP address for your system from the ISP--if your ISP uses dynamic addressing, you will need a fancy way of passing users to the connection (this will mean a script to set up a HTML/script to send the user to your dynamic address for this connection).
3. Software to connect your Telegard (fossil based) system to the internet connection you are running. This requires a 32-bit operating system which is cabable of creating a virtual port, and then Telegard will use that virtual port. In addition, you need a telnet server daemon to handle the inbound connection(s). Under OS/2, the SIO & Vmodem combination apparently works quite well. Under Windows 95, a fossil driver with base I/O port mapping, and VCom works. Windows NT may be similar.

Outbound Telnet is the most difficult of all because it requires a special door to handle the telnet connection. Under OS/2, this can be apparently accomplished with SIO and Vmodem.

While I agree this was a very quick overview to what can be a complex issue, there are a few sources which may help you--firstly, there is a text file describing some of the setup for Inbound Telnet & Telegard--I beleive it is available in the TGFAQnnn.ZIP files on our primary FTP site. Also, searching for things like "Gigo", "Vcom", "SIO" +"Vmodem" will result in several hits on the WWW which have further information.