Page 1
T R A N S C A N V 4 . 0 0
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
BBSINFO.DOC
~~~~~~~~~~~
Last updated: 1/30/93
This file contains important information on setting TranScan up to use
with different kinds of BBS Software. In the near future we plan on
adding direct support for many more BBSs. Until then any BBS can still
benefit from TranScan.
TABLE OF CONTENTS
~~~~~~~~~~~~~~~~~
Wildcat v3+ & Wildcat-IM..........................................2
Wildcat Test-Drive (v2+)..........................................3
PCBoard v14.5.....................................................3
VBBS..............................................................3
GTPower...........................................................3
WWIV..............................................................4
SpitFire..........................................................4
Oblivion/2........................................................4
GAP...............................................................5
Searchlight.......................................................5
Other BBS Software................................................5
Page 2
Wildcat v3+ & Wildcat-IM
~~~~~~~~~~~~~~~~~~~~~~~~
TranScan provides direct support for Wildcat v3+ & Wildcat-IM including
updating the file database, writing messages to users, reading com
information from MAKEWILD.DAT and environment variables, and writing to
the activity log. To setup TranScan follow these simple steps:
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) If MAKEWILD.DAT is in a directory that is not in your path you
should add this directory to your path statement.
3) Delete all current SCANFILE.BAT and SCANFILE.RUN files.
4) Create a SCANFILE.BAT file in the Wildcat home directory (where
MAKEWILD.DAT lives) as follows:
TS %1
If you use the AUTONODE feature of Wildcat you will need to create
a SCANFILE.RUN file in each node directory (NODE1, NODE2, etc.) as
follows:
cd\wc30\wcwork\node1 rem or node2 or node3 etc.
TS %1
5) Extract the *.IMP files from the WILDCAT.ZIP file and place them in
the same directory as your MSG0000.DAT file. These files are needed
to export the messages to your users. Be sure and edit these files
to suit your tast.
6) Configure TranScan to meet your needs. Be sure to select "Wildcat"
in the "BBS Set-Up" and select all other options.
7) If you selected "Y" to either "Compress OffLine?" or "Do GIF/JPGs
OffLine?" you will need to add the following to either your
POSTCALL.BAT or daily event batch file:
TS -L
8) You should always run "TS -L" before moving files on your BBS. You
may want to include this command line in your SYSOP1.BAT so that you
can do this from your SYSOP menu. You could also include this in a
batch file for WCPRO as follows:
CD\WC30
TS -L
WCPRO
9) TranScan can add Orphan Files to your Wildcat database "on the fly",
too. Here at TRANSCAN BBS I have my QMPRO configured to put all
downloads in my wildcat UPLOADS directory. I have created a
QMPRO.BAT file as follows:
CD\QMPRO
QMPRO
TS C:\FILES\UPLOADS\*.* -D
TranScan checks all the files in the UPLOADS directory against the
list of files (TS.DID) that it has already processed. If it finds
such a file it will TranScan it for viruses, recompress it, then add
the new file and description (if there was one) to your Wildcat
database. This eliminates any need from using the LOCAL UPLOAD
feature in Wildcat. In fact, you could have QMPRO.BAT run WCPRO
right after TranScan so that you wouldn't forget to move these new
uploads to their proper directories.
10)I recommend you change the prompts in your WCTEXT.DAT file if you
are using TranScan.
Prompt #578: Scanning/testing @SUB@, please wait...
Change to : Scanning/testing @SUB@ with TranScan. Please wait...
Prompt #579: @0E@@SUB@ - FAILED!
Change to : @0E@@SUB@ - FAILED TranScan integrity/date/virus check!
Prompt #580: @0E@@SUB@ - PASSED!
Change to : @0E@@SUB@ - PASSED TranScan integrity/date/virus check!
11)TranScan creates a LASTCALL file in your node work directory (NODE1,
NODE2, etc) to keep track of the name of the last caller to upload
files to that node. This makes it possible for TranScan to only
write one "Thank You" message per call for uploads. It is possible
that the same uploader could call back and upload more files. If
no one else had uploaded files to that node the name in the LASTCALL
file would be the same. For this reason you might want to delete
this file in the POSTCALL.BAT file.
Page 3
Wildcat Test Drive (v2+)
~~~~~~~~~~~~~~~~~~~~~~~~
TranScan provides limited support for Wildcat Test Drive BBS. It will
display COM output when used with External Uploads. It will not update
databases, import FILE_ID.DIZ, DESC.SDI, or GIF descriptions. There are
no plans to support these features in the future for Wildcat Test
Drive.
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) The following is a sample external upload batch file:
cd\wildcat\ep
dsz port %2 speed %1 RZ %3
copy %3 %4
Del %3
TS %5 /P%2
3) For files that are uploaded from internal protocols you will need
to run TranScan on those directories. It is suggested that you set
the "List files already DID?" to "Y" in the Configure-TranScan
Options. This will keep TranScan from processing files more than
once. The following is a sample batch file:
ts c:\files\uploads\*.* c:\files\private\*.*
Note that you can include up to 10 filemasks on the TranScan command
line.
PCBoard v14.5
~~~~~~~~~~~~~
TranScan provides limited support for PCBoard BBSs. It will display COM
output reading the PCBOARD.DAT and PCBOARD.SYS files for port
information. It will also update the UPDESC. file importing
FILE_ID.DIZ, DESC.SDI, or GIF descriptions. Many other features are
not available but will be added in the near future. To setup TranScan
follow these simple steps:
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) Delete all current PCBTEST.BAT files.
3) Create a PCBTEST.BAT file in the PcBoard home directory (where
PCBOARD.DAT lives) as follows:
TS %1 /%2,%3
4) You must add the /SWAP variable to the PCB environment. For example:
SET PCB=/SWAP
VBBS
~~~~
TranScan only provides COM output for VBBS BBSs at this time. Many
other features are not available but will be added in the near future.
To setup TranScan follow these simple steps:
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) Delete your current NEWUPLD.BAT file.
3) Create a new NEWUPLD.BAT file as follows:
TS %1 /P1
The /P switch is for indicating which port to use. /P2 would be used
for port 2, /P3 for 3, etc. If you are using non-standard uarts
please consult the TS.DOC manual for more information on these
command lines.
GTPower
~~~~~~~
TranScan only provides COM output for GTPower BBSs at this time. Many
other features are not available but will be added in the near future.
To setup TranScan follow these simple steps:
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) Delete your current GT_VSCAN.BAT file.
3) Create a new GT_VSCAN.BAT file as follows:
TS -LC:\GTLOG\GT_RECV.LOG /P%2
REM >C:\GTLOG\GT_RECV.LOG
4) Processing could also be done off-line by using GTLOGOFF.BAT. For
example:
TS C:\FILES\UPLOADS\*.* -D
Page 4
WWIV
~~~~
At this time WWIV does not leave enough memory available to run
TranScan while a caller is on-line. You should run TranScan from a
daily event as follows:
TS C:\FILES\UPLOADS\*.* -D
Many other features are not available but will be added in the near
future.
SpitFire
~~~~~~~~
Spitfire does not have a Post-Upload hook that allows testing files
immediately after upload. However this processing can be done from the
External Upload Batch files (SFEXTUPA.BAT, SFEXTUPB.BAT, etc) and after
a caller hangs up (SFINIT.BAT). You could also process the files in a
daily event.
The following is an example batch file for using TranScan during an
External Upload:
BRK OFF
ECHO OFF
CD\SF\EXTERNAL
DSZ.COM %2 RESTRICT RZ
TS /P%2 %3 %5 %6 %7 %8 %9
CD\SF
BRK ON
Many other features are not available but will be added in the near
future.
Oblivion/2
~~~~~~~~~~
TranScan only provides COM output for Oblivion/2 BBSs at this time.
Many other features are not available but will be added in the near
future. To setup TranScan follow these simple steps:
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) Delete your current MAINTAIN.BAT file.
3) Create a new MAINTAIN.BAT file as follows:
TS %1 /P1
Where /P1 represents the port 1, /P2 = 2, etc.
If file is failed it should be moved or deleted. Oblivion will
notice the file is missing and fail the upload.
Page 5
GAP
~~~
TranScan only provides COM output for GAP BBSs at this time. Many
other features are not available but will be added in the near future.
To setup TranScan follow these simple steps:
1) Put TS.EXE, TS.OVR, and TS.EXE in a directory in your path.
2) Delete your current UPCHECK.BAT file.
3) Create a new UPCHECK.BAT file as follows:
IF %6==0 TS %1 /P1
IF NOT %6==0 TS %1
If file is failed it should be moved or deleted. GAP will notice the
file is missing and fail the upload and display "...failed the
integrity check". TranScan can convert the file online and GAP will
recognize the changed file extension.
At this time TranScan does not write the DESC.SDI file to the Upload
Directory Path. This feature and others will be added in the near
future.
Searchlight
~~~~~~~~~~~
At this time TranScan should only be used during an event with
Searchlight BBS. In the near future TranScan will be able to read the
UPLIST.BBS file and process files while the user is online. The daily
event would be as follows:
TS C:\FILES\UPLOADS\*.* -D
RBBS
~~~~
At this time RBBS does not leave enough memory available to run
TranScan while a caller is on-line. You should run TranScan from a
daily event as follows:
TS C:\FILES\UPLOADS\*.* -D
Many other features are not available but will be added in the near
future.
OTHER BBS SOFTWARE
~~~~~~~~~~~~~~~~~~
If your BBS software was not listed it is only because I have not
tested it with TranScan. Feel free to upload the SHAREWARE version of
this software to TRANSCAN BBS at (913) 266-0781. Be sure to leave a
message if you have installed TranScan with this software outlining how
you did it.
Thanks!
Craig Dunstan