|
|
| TeleTest v2.00
| Upload Tester For Any Bbs Program,
| (C)1993 Netix Programing
| All Rights Reserved
| Freeware, No Registration Required
| Programmed By Digital Lightning
|
Carlo Technologies - NETiX Software Alpha Site, 416-472-4702
v.32bis v.42bis 14,400bps 200mb online, located in Markham
Ontario (Toronto Canada). Member of TeleNet, FIDONet and many
others. Contact Sysop for problems/contacting Digital Lightning.
Operation Requirements
TeleTest requires very little:
64k + Your ARCHIVE UTILITY REQUIREMENTS For Memory
A FOSSIL DRIVER INSTALLED (X00 or BNU Work best)
Telegard 2.7 Or Compatible version, or simalar system (NonTG)
Enough Free Space to unarc your LARGEST ARCHIVE at all times
Introduction
Upload testers which are simple enough to use for Telegard
are a rare sight. Now that has changed, this version of
TeleTest is only the first in a series of testers for
Telegard, and now Any Bbs system such as Renegade.
Formerly called TeleZip, but was devoted specificaly
to ZIP Files, I desided to re-do the program from scratch
and make it faster, better and more efficient. All of the
archive utilities I have ever encountered which are any use
has returned an errorlevel different when there is an error
decompressing files, so testing is a waste of time. It
depends on decompression errorlevels only.
Command Line Parameters
Telegard limits the parameters to three of them, @F for the
file, and @I for files to be added, or location of
decompression. Then if you do not have a Telegard compatible
system you need to specify so with Parameter four, "/D" for
disabling the loading of telegard data files.
Command Line Operation: Testing Operation
TELETEST.EXE <FILE> <PATH> [/D]
FILE: The path and name to the file (@F In telegard)
/D: Disable Telegard DataFile Loading, for use with Non
Telegard systems. The only real change between non-
telegard boards and telegard boards is the status line,
in telegard systems it displays the user online, on
non-tg systems it simply says NonTelegard Mode
PATH: Path to the Configuration file, A MUST FOR OPERATION!
If it does not fit inside of the system's input line then
simply make a batch file like this one:
@echo off
TELETEST.EXE %1 <PATH TO CONFIGURATION FILE>
A Simple batch file like that can save a lot of problems
and headaches.
Physical Operation
first it loads the data files, then it looks for the file you
specified, and figures out what archive format it is by
looking at the extention and comparing it to your Archive
Configuration. If configured, Batch File #1 is now run,
and then it then unarcs the file into the temp.
directory created by TeleTest. It then checks the
Errorlevel setting in your Archive configuration, if it
is not equal then it aborts with an errorlevel of 1. If
anything else goes wrong in the program, errorlevel of 2 is
is sent. Otherwise it continues by scanning the unarced
file for viruses, if the errorlevel does not equal the defined,
it aborts with an errorlevel of 1 because there is a possible
virus in the file, but before exiting if configured runs
Batch File #3. If it does equal the defined value, it then
runs Batch File #2. After which, it will (If placed
in the configuration of TeleTest) add a Zip Comment if the
file is a ZIP file, and then adds the file specified
(Advertisment file) to the archive if it is over the
specified filesize in the CFG File (Minimum file size is to
stop adding the advertisment to files too small and anoying
the users. Egsample: 1k Doc file, and a 4k advertisment
makes the file too large compared to the original size!).
Batch Files #1, 2, 3, and 4.
All of these batch files are for your convience, so you can
do things to the uploaded files. Such things are stripping
of the Auto Verification in the ZIP Files, or logging the
name into a file which is searched in to stop people from
uploading duplicates, even after the file has been deleted.
Many possiblities exist, here is a breef description on
when and possibly why the batch file is run. The name of
the file being tested is passes as Parameter #1 (%1 in the
batch files).
1) Batch file #1 is run before any testing occurs. This
one some use for the stripping of the Auto Verification on
ZIP Files (Using IfType.exe to make sure the file is ZIP
Type).
2) Batch file #2 is run after the scanning has taken place,
and the file has PASSED, no viruses exist.
3) Batch file #3 is run only when there is a VIRUS
DETECTED. This is good for copying the files to another
directory, or even deleting the file. In some cases you
can also hang up on the user using a program to do so.
Scanning the whole hard drive when this happens also is an
idea.
4) After the file still has PASSES Testing (No Viruses)
this command is run. It is good to delete advertisment
files from other BBSes which are anoying or any other thing
you wish to think up.
These Batch files can also be run as EXE Files, or COM
files. It does not matter as long as they are specified
in the configuration utility.
Installation
Running the program for all BBSes should be almost the
same.It loads in the Last Caller data file, and gets the
current callers name and number. It then looks to see if
there is a Carrier, if not then it assumes it is a Local
execution (Death?) and turns OFF ALL MODEM COMMUNICATIONS.
If this happens then you may not see the correct user name
on the status line since telegard does not log Local logins
and teletest has no way to get the username in that case.
Of course if you disable telegard data reading, then this
feature will not exist (Displaying the user name).
Telegard Instalation in Detail ---
To install TeleTest, go to the Sysop Menu of Telegard.
Then press P for the Main Configuration menu. Press F for
the file section configuration and then A for Archive
Confguration. Then modify (M1, M2...) all archives with
the + infront of it (Active Archives). Change the Test
Archive Command (Test Command) to "TELETEST.EXE @F <CFG
PATH>" or if the input line is too long, "TELETEST.BAT @F"
and create a Batch file with the folowing: <NEXT PAGE>
echo off
TELETEST.EXE %1 <PATH TO CFG FILE>
This will enable you to have the configuration file in odd
places and large paths.
*** MAKE SURE IF YOU HAVE YOUR ARCHIVE UTILITY PATH ***
*** DEFINED THAT TELETEST.EXE OR TELETEST.BAT IS ***
*** LOCATED IN THAT DIRECTORY OR IT WILL NOT WORK!! ***
Non-Telegard Instalation Non-Specific
You will need to change all archive definitions such that they
will run TeleTest instead of your archive utility to test
the archive integrity. If this is a Renegade System, folow
Telegard Instalation Procedure although some minor things
will be changed (IE: Menu command letters). Other systems
you have to be familar with your own system since there are
so many different systems out there I can not specify for all
of them.
Now you are done! When run localy it will not display the
right caller, it will dislpay the last caller but will
still be logged in thhe right mannor in the Sysop Logs
History
1.00 - First Release
1.01 - Minor bug fix
2.00 - Major changes... Too numerious to list. (Basicaly the
code was re-written). This version has been beta-tested
for over 5 months so it should work perfectly, longest
beta testing in NETiX Software History!
Thank You For Trying TELETEST v2.00, Hope You Enjoy it!