home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
MISC
/
TGARTS.ZIP
/
PROBLEM.DOC
< prev
next >
Wrap
Text File
|
1999-12-13
|
8KB
|
155 lines
Telegard and Common Problems
by Scott Adams
In my 12 or so years running Telegard its actually hard to remeber
any real problems that was not hard to solve with Telegard. But I
will try to give a overview of some of the common problems and possible
but not the only way to solve it.
1) Problem: You have a fossil drive but Telegard won't answer.
Answer: If you are experiencing problems, such as the modem not
answering or the communication rate operating at ~300 bps, then please
check over the following items:
(1) Has the fossil driver been correctly setup to use the correct
comport? Fossil drivers use port numbers that are one less than
the comport reference number; i.e. COM1 = Port 0, COM2 = Port 1,
etc. Ensure that you have setup your fossil driver correctly.
(2) If you have a high speed modem, have you locked the fossil port
associated with your modem? If not, then this can cause the
modem to communicate with Telegard incorrectly (such as at 300
bps). Refer to your fossil documentation on how to correct
this; for X00 for example, you must specify the comport and rate
to lock with, such as:
device=x00.sys e b,0,115200
(3) Have you tried another fossil driver brand? Occasionally
certain fossil drivers just don't work with certain hardware
configurations.
(4) Are you using the latest *official* release, or a beta? Often
the betas have 'features' which really aren't features, and can
cause more problems than good. The converse is also true though;
sometimes the final releases have similar 'features'.
2) Problem: My Front-end mailer seems to only let callers connect at
300 or 2400 bps with Telegard.
Answer: There is no quick answer however there are three common
ways:
1) Fossil problems: The fossil driver is likely configured
incorrectly for the locked baud rate or locked port setup.
Consult 3.02 of \docs\faq.doc for further information.
2) Batch file/errorlevels: You might not be giving the right
errorlevel from your front end mailer to Telegard. Make sure
TG is detecting the correct baud rate if not then its likely
the batch file.
3) Modem Init string: Many modem initialization strings might be
giving the incorrect settings. For example modems might be
reporting the DTE connection rate instead of the proper rate.
In which case you should consult your modem documentation (in
many cases this can be fixed by adding W2 to the modem init
string if your modem supports this command).
3) Problem: My DSZ/GSZ protocols does not work.
Answer: DSZ/GSZ configuration -- If you are using non-standard port
setups for your communications, then you will need to update your
DSZ/GSZ protocol definitions. Change "PORT ~CP" to " PORTX ~CJ,~CI"
and that should alleviate the problems. Make sure that within
Telegard you have your modem BASE I/O ADDRESS and IRQ set properly
as well (single nodes -> Config. Modem, multiple nodes -> Manager.
Nodes.Modem).
4) Problem: My Zmodem says transfer.log not found?
Answer: Try allocating more Environmental space via the External
Utilities screen. A good size is 512-1024. Sometimes the log
is not found because of low memory at the time. Most times
increasing the Environment size (used by SET= statements) will
fix it.
Note: For 3 and 4 I use GSZ for other protocols consult faq.doc.
5) Problem: My new cd-rom won't work in Telegard.
Answer: If you just installed the CD-ROM and it won't work in
Telegard try this:
Go into System Configuration->Hardware. Press T and TG will
rescan and look for all installed HDs and/or CD-ROMS. When it
asks to update the drive table, press Y.
6) Problem: I get Run-time 100 error
Answer : This could be anything but most typically a file is
corrupt or opened before it should have been closed. Generally
you find this error while reading a message base and it
bombs out. There are ways to track the exact item down. If
you know its a file or message base try to interact with it
like purging the message base or adding files. Run the index
utility again. If you are able to track the particular file
down and you can't fix it through some outside means you will
likely have to delete that file and start over. But the majority
of the time it seems to be message bases get corrupt through
some external program but are easy to restart.
If you are just having a big time problem with soemthing here are
the steps you should follow in trying to fix the situation:
A. Consult \docs\errors.ref to see if the run-time error (if it
is one) is easy to fix and find out what the problem is.
B. Consult \docs\faq.doc for common problems and see if its
covered in there with a solution.
C. Consult \docs\telegard.doc to see if your doing something
wrong on your end by mistake.
D. Is the problem external or internal to Telegard? If external
see if the program or item is out of date for the current Telegard
version. Check to see if the problem internally is a bug that
has been reported. If not you might have discovered a bug.
D. Before giving up state your problem and ask for help. You can
do so in the FidoNet official telegard support echo (tg_support). You
will likely get a prompt answer in that echo. If you have to email
or netmail the author (though be adivsed he is very busy) or any of
the Telegard Development team (Alpha/Beta sites). Your best bet though
is to use the Fidonet echo.
E. If you think it indeed is a bug you just can't fix then
write all the information that is related to the problem down. Supply
the Operating System info (memory, special setups), supply the
version of Telegard and any other software you are currently using that
might conflict with Telegard. Write down the area of the problem
and any run time error numbers. Once all this information is gathered
post your problem as suggested in D to the above methods.
The majority of all Telegard problems is generally a old or badly
done external utility. Then comes typos and mis-setups from the sysop.
There is a small chance that Telegard is the cause but from my
experience it tends to be one of the first two items or a combination
of those items.
Note: I took some of these common problems from my \docs\faq.doc
which is a collaboration of various contributors from Tim Strike
to many others.
------------------------------------------------------------------
To contact me for feedback on the article or questions/comments:
BBS: 904-733-1721 Fringe BBS-EWOG II (guest account avaliable)
Email: longshot@darktech.org ICQ #: 24436933
Website: http://users.cybermax.net/~longshot
Netmail: FidoNet 1:112/91 Fido TG Echo: Tg_support
I welcome any comments or questions ohe articles. If enough
feedback is given I can do article follow-ups. I suggest you also
send feedback to the the other article authors of this newsletter
for without feedback the desire to continue is difficult.
------------------------------------------------------------------