Copyright: ® Guy Gallo


Help Contents
Contents

Overview

Introduction

Registration

Installation

Assumptions

How to use

Command Line Options

The Modules

New Mail

Adding CC to Existing Mail

Forum Upload

Message Request

Address Book/Groups

Address Book

Groups

Menu Commands

File

Options

Tools

Scripts

Advanced Topics

Files Used or Created by WCUTIL

The WCUTIL.INI file

The Default WCUTIL.TPL template

Turning Off Distribution Lists


Introduction

WCUTIL is an add-on for WinCIS that implements several features:

•	Adding multiple addresses to e-Mail (either new or existing) messages

•	Uploading files to forums

•	Special message requests

In addition to these major functions, WCUTIL also provides:

•	A hook to a "front end" script

•	A configurable billing script

•	Conversion of  MOX files into files readable using the built-in WinCIS message reader and

•	The creation of shadow forums to hold saved messages

•	Menu items to easily edit several of WinCIS's support files (button files, INI files etc.)

There is no printed or printable manual.  This help file is the manual.

WCUTIL uses a combination of script generation controlled by a stand-alone visual basic application and a modified script template (named, by default, WCUTIL.TPL) to perform various on-line processing.


Registration

WCUTIL is not free.  It is being released as ShareWare.  If you continue to use WCUTIL, please register and pay the $19.95 fee.

This is a one time registration fee.  That is, future updates to the program (barring a revision more major than any I foresee), will be free.

Since this program is specifically used for logging onto CIS (with WinCIS), there will be no support other than via CIS;  and there will be no disk based version of the program.  That is to say, since I can assume all users can log onto CIS, all support will be provided either via e-Mail or (preferably) in the WinCIS section of  the WUGNET forum;  and all updates will be posted to Library 13 of the WUGNET forum.

All registration will be handled on-line, via CIS's SWREG function.

To register, Select Script.Remain On-line to stay on-line after your automatic session is done, or log onto CIS using the Interactive button.  At the command prompt type

GO SWREG

and follow the on screen instructions.

The Registration ID for WinCIS Utilities is:  1143


Installation

WCUTIL.EXE must be in the same directory as WINCIS.EXE.

WCUTIL.INI must be present and in the same directory as WCUTIL.EXE.

WCUTIL.TPL is a script template containing the various script instructions necessary to utilize the on-line features of WCUTIL.EXE.  You must either make this TPL your active template or copy this file to WINCIS.TPL.  It makes no difference which you do.

To set WCUTIL.TPL as the active template select:

Settings.Processing Options.Template to Build Scripts from

and enter WCTUIL.TPL in the edit box.

When WinCIS prepares to go on-line, it builds a script file named WINCIS.SCR that contains the various forums to enter and options to execute.  This script is generated based on the structure of a TPL file.  The default TPL file is named WINCIS.TPL.  WCUTIL requires that you used WCUTIL.TPL -- either by changing your configuration's Processing Options.Template to Build Scripts from, or by copying WCUTIL.TPL to WINCIS.TPL.

WCUTIL.HLP should also be copied to your WinCIS directory.


Assumptions

WCUTIL makes the following assumptions.

•	That you are using the default installation regarding directory structure:  control files are in C:\WINCIS\CONTROL, and all messages are stored in C:\WINCIS\MESSAGES.

•	That the file paths contained in your CFG file and in WINCIS.INI are hard coded directories rather than variable directories.  That is to say, you are not using the variable method of pointing to a directory, such as &WinCISPath\CONTROL, but are specifying directories with their full path name, e.g. C:\WINCIS\CONTROL.

•	Version 1.0 of WCUTIL assumes that you are using WinCIS .94D.  WCUTIL will work with version .94C, but not properly.  Specifically, the Special Request Function is significantly hampered.


How to use

Simply run WCUTIL before logging onto CIS to modify mail (add CCs), add new mail, specify files to upload to a forum, or add special message handling requests to the next run.

There are two possible cases to consider when running WCUTIL:

1) WCUTIL is run and its options selected before loading WinCIS:

In this case, selecting either of the functions which require that a forum be "active" in order for the custom script to be executed, will be marked by WCUTIL in STATUS.INF for "read waiting messages".  The effect of this is that when you load WinCIS it will read STATUS.INF and the forum activities selected in WCUTIL will be executed when those forums are entered by logging onto CIS with the Actions button.  You will see Messages(Waiting) activated in the forum list.

2 WCUTIL is run and its options selected after loading WinCIS:

In this case, the marking of a form as active (as described above), will not be "registered" by WinCIS.  I hope to make the connection smarter, with Larry's help, in a future release.  For the time being, you have one of two choices:

Manually change any processing option for the forum you want to process with a WCUTIL script.

or

Logon to CIS using the Messages button rather than the Actions button.

For those of you interested in understanding why the above is necessary, and how WCUTIL interacts with WinCIS, please see


Command Line Options

By default, WCUTIL loads all three of the modules.

You can load WCUTIL with a specific module by specifying any one of the following keywords on the command line:

UPLOAD - Loads only the forum upload function

MAIL   - Loads only the mail function (also loads the address book)

REQUEST- Loads only the message request function (also loads the address book)

Even if you load WCUTIL with a command line option (and therefore initially display only one of the modules) you can always activate the other modules by selecting them from the Tools menu.


New Mail

This function allows you to create an e-Mail message.  The major difference between this function and the one built into WinCIS is that WCUTIL allows you to send an e-Mail message to multiple recipients.

The new message will be appended to any existing MAIL.SND file, or create a new one.

The editor is quite primitive, but it gets the job done.

The New Mail module

The To combo box can hold up to 50 addresses.

The Buttons

When the To combo box has the focus three buttons are activated:

Book  - This activates the WCUTIL address book

Groups - This activates the WCUTIL Group dialog box.

When an address within the existing list is selected, the Remove button becomes available.  This allows you to delete a single addressee from a multiple list.

When you type an address directly into the text edit box portion of the combo box, the Add button becomes available.  You must select Add to include a directly typed address into the list.

Subject

Type in the subject for this message

Receipt

Check this box if you wish CIS to confirm that your message was received.

The Type Option Buttons

If you select either the Binary File or Text File option buttons, the message edit area will change to a single line and a button labeled Browse will appear.  This button will bring up the standard FileOpen dialog box to allow you to select a file for uploading as a message.

Save

Select the Save button when all fields have been filled in and you are ready to store the mail message.  If you have not filled in all fields, WCUTIL will display an error message.

Mail Distribution Lists

By default CIS includes a list of all addressees at the end of your mail message.  There is no way (currently) to turn this off on a message by message basis from WinCIS or WCUTIL.  If you do not want a distribution list included in your messages you must change this option on the CIS end of things.  Go to the CompuServe Mail prompt manually (in interactive mode) and type SET.  This will bring up the mail options menu.  Select option 6, set it to No, and answer Yes when asked if you want to make this change permanent.


Adding CC to Existing Mail

WCUTIL looks to see if there is already a MAIL.SND file in the MessagePath.  If so, it enables the Add CC to Existing Mail module, and lists all pending e-Mail messages.

The left hand box lists the title of all messages in the current MAIL.SND file.  The right hand box changes depending upon which message you have selected.  It displays the current address information for the selected message.

Beneath the right hand box are three buttons:

Book  - This activates the WCUTIL address book

Groups - This activates the WCUTIL Group dialog box.

When an address within the existing list is selected, the Remove button becomes available.  This allows you to delete a single addressee from a multiple list.


Forum Upload

File to Upload

The full path name to the file you wish to upload to a CIS Forum.

Browse

When the focus in on the File to Upload edit box, this button becomes available.  It displays the standard FileOpen dialog box from which you can select the file to upload.

CIS Name

The name to use on CIS for the file you have uploaded.  WCUTIL makes a best guess.  It assumes you wish to use the same file name.  However, CIS limits the name portion of a file name to six characters as opposed to DOS' allowing eight.  Therefore, WCUTIL will truncate a longer name portion to six characters.

Protocol

The protocol to use during the file transfer.  In most cases this should be left at the default "BIN" for Binary.

Forum

This drop-down list contains all of the available forums based upon your WinCIS configuration.

Select the forum to which you wish to send a file.

Library

This drop down list contains all of  the available library sections for the selected forum.  Select the specific library to receive the upload.

Title

The title for your upload.  This is a string of up to 48 characters.  It is used in the "short" display of your upload.

The edit box will not accept more than 48 characters.

Description

The more detailed description of your upload.  The description is limited to 549 characters.  It is advisable to enter the description as a single paragraph.

Keywords

Limited to ten words and 80 characters.  These keywords should be both specific and general, the words you think a user hearing of your upload might use to locate it in the library.

Save Options

These two option buttons and single check box control what precisely happens when you click the Save button.

Save <fname>.UP

If this box is checked then WCUTIL will save an "UP" file containing the upload information.  The name of the UP file will be taken from the name of the file being uploaded.  For instance, if you are uploading WCUTIL.EXE, the UP file will be named WCUTIL.UP.

This facility allows you to enter upload information (File to Upload, Title, Description, Keywords) once, and then create multiple UPL files to send your file to multiple forums.  Simply load the UP file and change the forum destination.

To <forum>.UPL

If this option button is checked, the script to upload your file is saved to a forum specific script.  For instance, uploading to WUGNET would create a WUGNET.UPL  file.

This script will only be executed if you enter the WUGNET forum for other processing options (such as messages or library scan).

Note: More than one file upload can be created for a single UPL script.

To WCUTIL.SCR

If you check this option button, the upload script is saved to a "front-end" script named WCUTIL.SCR.  This script is executed at the start of your next on-line session.

Save

Save the script and, optionally, the upload description.

Load

Load a previously saved UP file from the ControlPath.

Note:  WCUTIL is able to read UP files created by CISOP (a DOS-based CIS navigator).

Clear

Empty all fields in the dialog box.


Message Request

Request special message function.

The Custom Message Request module allows you to create a forum specific script to do special message and header scan captures.

CompuServe allows a complex array of commands for capturing message and message information.  The list included in the Custom Message Request module is probably not complete.  For that reason, and to allow Sysops to add additional commands to this module, the list of commands is contained in the WCUTIL.INI file, and can be edited and modified to suit your needs.

Forum

This drop down list contains all of the forums available in your ControlPath.  First select the forum to operate upon.

Then select the command to execute.

Depending upon the needs of the command, the left hand side of the dialog box will change, displaying edit boxes for message numbers, days, text, user id and the like.

You should also select the forum sections to operate upon.  If you select no section, the command will be executed upon all sections.

The edit box at the bottom of the dialog displays the current script file for Read (RM) or QuickScan (QM) functions.


Address Book

When WUTIL loads either of the message functions (Mail or Custom Message Request), it also loads the currently active WinCIS Address Book.

By default the address book for WinCIS is named ADDRESS.CFG and is stored in the same directory as the WinCIS executable.

However, with version .94D, it is possible to load address books of other names.  For this reason, WCUTIL first looks in you WINCIS.INI file, under the [PGM OPTIONS] section, for the keyword AddressBook=.  If such a keyword is found, it loads the specified address book.  If this keyword is not found, WCUTIL assumes the default (ADDRESS.CFG).

Note:  The path pointing to the address book must be hard-coded, not variable.

The Address Book does not allow for adding or deleting addresses.

You can select more than one address from the list, up to 50 addresses (the maximum number of addresses allowed by CIS for e-Mail).

The list of addresses is always sorted by name.

The total number of addresses and number of selected addresses are displayed at the right above the list.

Buttons

Search - This button will bring up a standard input box.  You can type either a portion of a name or comment.

Although this facility does not all for "regular" expressions (such as "find both Jones and Smith"), it does allow you to do multiple searches and display all results.

Do the first search, and prefix the second (or third) search word with a plus sign.  For instance, searching for "Jones" and then searching for "+Smith" would display all hits of Jones and Smith.

Search is not case sensitive.

The default search string is [all].  This can be used to restore the full address book after a search.

Clear Tags - This button simply resets the number of selected addresses to zero.


Groups

The Groups function of WCUTIL is extremely useful for those WinCISers who frequently send mail to multiple recipients.

The dialog box for Group management looks like this:

The left hand side is dedicated to Group names.  You can select, create, and remove entire groups.

When you add a new group, you are prompted for the group name and then immediately taken to the address book to add addresses.

The Names list box displays the addresses for the currently selected group.  When the focus is on the Names list, the Add and Remove buttons become available.  Add will bring up the address book.  Remove will remove the currently selected address from the group.

Group information is stored in the WCUTIL.INI file


File

Open

Exit


Open

Allows you to easily edit some of the text files used by WinCIS and WCUTIL.

For more information on the various files used and created by WinCIS and WCUTIL, please see Files Used or Created by WCUTIL.


Exit

Close WCUTIL.


Options

Editor/Viewer

You can change the default editor/viewer to use by selecting the Options menu.

The Viewer is called IF you select Read Only on the Command Dialog File Open dialog box.


Tools

Related Topics:

Loading Modules

Convert MOX Files

Create Message Archive


Loading Modules

The first four items on this menu are concerned with loading the major modules.  Note that each has a speedkey.

This facility is provided for those who may load WCUTIL for a specific module (using Command Line Options), and then wish to load any of the other modules.


Convert MOX Files

This is an utility that comes out of my particular way of organizing messages.  WinCIS saves all outgoing messages to a file named as <forum>.MOX.  But those files are not readable from within WinCIS, and they have a header that is incompatible with various other CIS readers (such as MSGVU).

This utility takes an MOX file and converts it to a standard "raw" CIS output file.

This file can then be loaded into a CIS reader.

If you convert the MOX file to the third of the option button options:  <forum>~.MSG, and create a bogus forum using the Create Message Archive function (described below), you will be able to load your outgoing message file into the WinCIS reader.

Note:  If you then EXPORT your messages from this forum to the <forum>~.MSG file, you will be able to load your saved messages.


Create Message Archive

This function will create a "bogus" forum for use to store saved messages (and outgoing messages if you use the Convert MOX files function).

What it does is:

•	Create a MSG file based on the first seven characters of the forum name to which is added the Tilde.  For example, the archive file for WUGNET would be WUGNET~.MSG

•	Create an SEC file with the archive name (for example, WUGNET~.SEC).  This is necessary in order for WinCIS to recognize this is a "forum."

•	If the View named Archived Messages does not exist, it will be created.

•	<forum>~.MSG will be added to the Archived Messages View.


Scripts

The scripts menu is one aspect of WCUTIL that I am certain will expand with each version.

The idea is to provide an interactive way to gather information from CIS.

•	The Build function will create interactively designed scripts for various functions.

•	The Add to WCUTIL.SCR function will append those custom scripts to the front-end of your next WinCIS session

The power of this "hook" should be obvious.  There is no reason not to be able to automate grabbing stock quotes, movie reviews, file searches, perhaps even Executive News Service.

Related Topics:

Build:

Add to WCUTIL.SCR


Build:

Get Billing Information generates a billing script.

The first check box enables the capture of previous activity (when this is not check the script will only get the current activity).

If you do not "Add to WCUTIL.SCR" then you must execute WCBILL.SCR manual.

The Save To options allow you to either

Capture to a distinct, one time file named BILLING.TXT (and optionally load it into Notepad).

or

Append the billing information to a "fake" forum named BILLING~

Get Stock:

Not available in this release of WCUTIL.


Add to WCUTIL.SCR

Allows you to add a script to the "front end" script.

When you are using WCUTIL.TPL as the controlling template, WinCIS looks to see if a file named WCUTIL.SCR exists in your ControlPath directory.

You can add any existing script to the front-end processor.

Important Note:  most of the scripts that ship with WinCIS are designed to be used by themselves.  As a result, they end with an LOGOFF instruction.

You must create modified versions of these scripts and remove the logoff instructions in order to be able to execute them from within WCUTIL.SCR and then proceed with other on-line processing options.


Files Used or Created by WCUTIL

What follows is a list of various files used by WinCIS and WCUTIL to process on-line actions

WCUTIL files:

<forum>.UPL

<fname>.UP

<forum>.RM

<forum>.QM

WCUTIL.INI

WinCIS files

MAIL.SND

STATUS.INF

<forum>.MOX

<fname>.TPL


<forum>.UPL

This file is created when you execute the Forum Upload function.  It is a WinCIS script that will be executed after entering the named forum.

For example, if you have specified a forum upload to WUGNET, WCUTIL will create a script named WUGNET.UPL and store it in your ControlPath.

When you next log on to CIS (using WCUTIL.TPL, of course), the WinCIS will find and execute this script when next it enters the WUGNET forum.

After the successful execution of the UPL script it will automatically be deleted.


<fname>.UP

When you create an UPL script to execute a forum upload, you have the option to save the upload description.

The name of this upload description file is based on the filename of file being upload.

For example, if you are uploading WCUTIL.EXE to WUGNET's library 13, WCUTIL will create a UPL file named WUGNET.UPL, and an UP file named WCUTIL.UP.

UP files are stored in your ControlPath.

UP files can be loaded into the Forum Upload module.  This allows you to create multiple upload scripts without having to re-enter the file information.


<forum>.RM

This class of file is created by the Message Request function.  It consists of any number of message read requests (prefaced by a comment describing the take the request was entered).

RM files are stored in the ControlPath.

Like UPL files, RM files are only looked for (and seen/executed if they exist), upon entering the named forum.  Therefore, after creating a RM script you must be sure to activate the forum (or log on with Messages instead of Actions).

After the successful execution of the RM script, it will be deleted.


<forum>.QM

The QM file, like the RM file, is generated by the Message Request function.  It consists of any number of message scan requests (prefaced by a comment describing the take the request was entered).

QM files are stored in the ControlPath.

Like UPL files, QM files are only looked for (and seen/executed if they exist), upon entering the named forum.  Therefore, after creating a RM script you must be sure to activate the forum (or log on with Messages instead of Actions).

After the successful execution of the QM script, it will be deleted.

WCUTIL.SCR

This is a script file

WCBILL.SCR

Stored in the Scripts directory.


WCUTIL.INI

This file contains several important options for WCUTIL:

•	Editor/Viewer configuration.  This allows you to use your preferred editor and Viewer .

•	Group Information.  All groups of addresses are stored in the WCUTIL.INI file.

•	Custom Message Request commands.

Please The WCUTIL.INI file for further information about the structure of this file.


MAIL.SND

Contains any mail to send.  If this file already exists, WCUTIL will load with the Add CC to Existing Mail module as well as the Create New Mail module.

You can use the Create New Mail module to add to or create a MAIL.SND file.

Since this is the file used by WinCIS to send mail, WCUTIL needs no additional steps to be taken.


STATUS.INF

This file, new to version .94D of WinCIS, contains flags for pending on-line and off-line actions.

When you create an upload script or a special message request, this file is modified by WCUTIL.  The forum to act upon with the WCUTIL script is marked for "read waiting messages."


<forum>.MOX

These file are created to save outgoing e-Mail and forum messages.  Their creation is controlled by settings in the Processing Options dialog box.


<fname>.TPL

This is a script template.  By default this is WINCIS.TPL.  To enable the functionality of WCUTIL you must use the template distributed with this package as WCUTIL.TPL.


The WCUTIL.INI file

This file contains several important options for WCUTIL:

•	Editor/Viewer configuration.  This allows you to use your preferred editor and Viewer .

•	Group Information.  All groups of addresses are stored in the WCUTIL.INI file.

•	Custom Message Request commands.

Here is an example WCUTIL.INI file (similar to the one that ships with WCUTIL):

[Options]

Editor=DESKEDIT.EXE

Viewer=BROWSER.EXE

[Address Groups]

WCUtil=David R Smith 70412,576;Jonathan Zuck 76702,1605;Larry Lee (WinCIS) 76670,1471

[Custom Message Request]

;*********************************************************************

;the following section contains the custom message request strings

;Syntax:

;

;CIS COMMAND=Description;prompt1;prompt2

;

;note:  it is important that each line have all three parts.

;

;The COMMAND portion of the string can contain any of the following three

;"reserved" words:

;

;nnn=Number

;ddd=days

;user=User name or id

;

;What form of user input is allowed is determined by these keywords.

;

;note: any command that requires a "user" field must have that

;field in the second prompt

;*********************************************************************

SCA QUI NEW=Scan all new message headers;none;none

SCA QUI DAYS:ddd=Scan messages posted within ddd days;Days;none

SCA QUI ALL=Scan all forum messages;none;none

SCA QUI STA:nnn=Scan all messages from number nnn;Starting number;none

REA NUM:nnn=Read message number nnn;Msg number;none

REA WAI=Read Waiting messages;none;none

REA THR WAI=Read Waiting message threads;none;none

REA THR NEW=Read all new message threads;none;none

REA THR NUM:nnn=Read message number nnn and all replies;Msg number;none

REA THR DAYS:ddd=Read message threads posted within ddd days;Days;none

REA THR ALL=Read all forum message threads;none;none

REA THR STA:nnn=Read all message threads starting with nnn;Starting number;none

REA NEW TO:ALL=Read all new messages addressed to ALL;none;none

REA NEW=Read new messages;none;none

REA NEW FROM:user=Read new messages from user name or ID xyz;none;From user

REA NEW TO:user=Read new messages to user name or ID;none;To user

REA NEW SUB:text=Read new messages with subject string;Subject;none

REA DAYS:ddd=Read messages posted within ddd days;Days;none

REA DAYS:ddd FROM:user=...from user name or ID;Days;From user

REA DAYS:ddd TO:user=...to user name or ID;Days;To user

REA DAYS:ddd SUB:text=...with subject string;Days;Subject

REA ALL=Read all forum messages;none;none

REA ALL FROM:user=Read all messages from user name or ID;none;From user

REA ALL TO:user=Read all messages to user name or ID;none;To user

REA ALL SUB:text=Read all messages WITH subject string;Subject text;none

REA STA:nnn=Read all messages starting with nnn;Starting number;none

REA STA:nnn FROM:user=...from user name or ID;Starting number;From User

REA STA:nnn TO:user=...to user name or ID ###;Starting number;To User

REA STA:nnn SUB:text=...that contain subject string;Starting number;Subject text

DEL PRI DAYS:ddd=Delete Private msges to user, last ddd days;Withing days;none

DEL NUM:nnn=Delete Forum Message number nnn;Msg number;none

HI NUM:nnn=Reset Forum's High message number to nnn;Set Hi Msg number to;none

OTHER=Manually enter any valid message command;Command;none

There are three sections to this INI file.

Related Topics:

[Options]

[Groups]

[Custom Message Request]


[Options]

This is the simplest of the sections.  It simply points to the applications to use as the Editor and Viewer in the FileOpen functions.

Editor=DESKEDIT.EXE

Viewer=BROWSER.EXE

By default both are set to NOTEPAD.EXE.


[Groups]

The syntax for this sections is:

GroupName=Address1;Address2...AddressN

The GroupName should be unique.

Each group can hold up to 50 addresses.


[Custom Message Request]

This is the most complex of the options stored in WCUTIL.INI.

The default settings to this section should not be changed unless you know what you're doing.

The syntax for each item is:

CIS COMMAND=Description;prompt1;prompt2

For example, to take a frequently used custom request:

REA THR NUM:nnn=Read message number nnn and all replies;Msg number;none

The command that will be executed by the RM script will be

REA THR NUM:nnn

where nnn will be the number entered by the user.

The description of this command, as it appears in the list of special request commands, will be

REA THR NUM:nnn                   |Read message number nnn and all replies

The last two options in the line, prompt1;prompt2 determine what will appear as the text description on the dialog box.

The nature of the input field will be determined according to the reserved words contained in the CIS COMMAND section of the entry (in fact, this is the "keyword").

For instance, if the keyword contains the word "user", WCUTIL knows that this command accepts a user ID as input, and will display both an edit box and the Address Book button.

If the keyword contains "ddd", WCUTIL will display an edit box for number of days and limit the input to numbers.


The Default WCUTIL.TPL template

Here is the default WCUTIL.TPL file.  Significant command additions or comments are colored RED:

;***********************************************************************

;WCUTIL TPL file

;This TPL file has been customized for use with WCUTIL.EXE an add-on

;utility for WinCIS.

;

;Lines commented out by the author will be marked with three semi-colons

;

;blocks of added commands will be delineated by:

;------------------------------------------------------------------------

;as will explanatory comments

;***********************************************************************

[PROLOG]

;

; This script file was created on &&DATE at &&TIME by &&USERNAME.

;

;***********************************************************************

;       WinCIS &&VERSION

;       Copyright(C) 1992

;       Larry Lee (76670,1471)

;       16038 Augusta Drive

;       Chino Hills, Ca 91709

;       (Script language notes have been moved to the bottom of file)

;       (left out of the help file version of this file...)

;***********************************************************************

;

;

;;;SEND SET BRIEF YES^M

;;;WAIT !

;;;SEND SET PAGED NO^M

;;;WAIT !

;;;SEND SET BLANK YES^M

;;;WAIT !

SEND SET WIDTH 80^M

WAIT !

;

;------------------------------------------------------------------------

; Execute WCUTIL.SCR if it exists in the ControlPath

;------------------------------------------------------------------------

  IF FILEEXISTS &&CONTROLPATHWCUTIL.SCR

    @ECHO No WCUTIL.SCR to execute.

    %ECHO Executing WCUTIL.SCR...

    %DO &&CONTROLPATHWCUTIL.SCR

    %KILLFILE &&CONTROLPATHWCUTIL.SCR

;

[EPILOG]

;

;***********************************************************************

; All Done, Just Log off CompuServe

;***********************************************************************

;

LOGOFF

[READ MAIL]

;

; Read Any Waiting CompuServe Mail

;

 IF MAILWAITING

  @REMOVEACTION MAIL Read.Waiting

  %ECHO Reading CompuServe Mail

  %READMAIL &&SYSMESSAGEPATHMAIL.MSG

    %%ECHO CompuServe Mail Read Complete!

    %%REMOVEACTION MAIL Read.Waiting

    %@ECHO Unable to Read your CompuServe Mail!

[SEND MAIL]

;

; Send Any Waiting CompuServe Mail

;

  IF FILEEXISTS &&SYSMESSAGEPATHMAIL.SND

  @REMOVEACTION MAIL Send.Replies

  %ECHO Sending CompuServe Mail

  %SENDMAIL  &&SYSMESSAGEPATHMAIL.SND

    %@ECHO Unable to Send your CompuServe Mail!

    %%ECHO CompuServe Mail Send Complete!

    %%REMOVEACTION MAIL Send.Replies

[PROMPT MAIL OUTBOX]

;

; Ask what about Overwriting to the Mail OutBox

;

     %%ASK OVERWRITE? &&SYSMESSAGEPATHMAIL.MOX  Do you want to save your outgoing Mail in &&SYSMESSAGEPATHMAIL.MOX

     %%%ECHO Saving Your Out Going Mail to &&SYSMESSAGEPATHMAIL.MOX

     %%%FILEMARK &&SYSMESSAGEPATHMAIL.MOX MAIL_SENT CIS:MAIL

     %%%COPYFILE &&SYSMESSAGEPATHMAIL.SND &&SYSMESSAGEPATHMAIL.MOX

; At This point the Mail File Is No Longer Needed

     %%KILLFILE &&SYSMESSAGEPATHMAIL.SND

[APPEND MAIL OUTBOX]

;

; Append Queued Mail to the Mail OutBox

;

   %%ECHO Appending your outgoing Mail to &&SYSMESSAGEPATHMAIL.MOX

   %%FILEMARK &&SYSMESSAGEPATHMAIL.MOX MAIL_SENT &&FORUMNAME

   %%COPYFILE &&SYSMESSAGEPATHMAIL.SND &&SYSMESSAGEPATHMAIL.MOX

; At This point the Mail File Is No Longer Needed

   %%%KILLFILE &&SYSMESSAGEPATHMAIL.SND

[OVERWRITE MAIL OUTBOX]

;

; Overwrite Queued Mail to the &&FORUMNAME OutBox

;

   %%ECHO Saving your outgoing Mail in &&SYSPATH&&FORUMNAME.MOX

   %%KILLFILE &&SYSMESSAGEPATHMAIL.MOX

   %%FILEMARK &&SYSMESSAGEPATHMAIL.MOX MAIL_SENT &&FORUMNAME

   %%COPYFILE &&SYSMESSAGEPATHMAIL.SND &&SYSMESSAGEPATHMAIL.MOX

; At This point the Message File Is No Longer Needed

   %%%KILLFILE &&SYSMESSAGEPATHMAIL.SND

[DELETE MAIL OUTBOX]

;

; Never Save Queued Mail to the Mail OutBox

;

   %%ECHO Deleting outgoing Mail: &&SYSMESSAGEPATHMAIL.SND

; At This point the Mail File Is No Longer Needed

   %%KILLFILE &&SYSMESSAGEPATHMAIL.SND

[GO FORUM]

;

;***********************************************************************

; Lets enter the &&FORUMNAME forum, &&FORUMTITLE

;***********************************************************************

ECHO Going to &&FORUMNAME, &&FORUMTITLE

;----------------------------------------------------------------------

;If you wish to grab forum announcements each time you enter a forum

;uncomment the following four lines:

;----------------------------------------------------------------------

;;;FILEMARK &&MESSAGEPATH&&FORUMNAME.MSG Read_Annoucements &&FORUMNAME

;;;PUTFILE &&MESSAGEPATH&&FORUMNAME.MSG ^M^J#: 0 S-1/ Forum Annoucement^M^J    01-Jan-93  &TIME

;;;PUTFILE &&MESSAGEPATH&&FORUMNAME.MSG ^M^JSb: News Flash^M^JFm: System^M^JTo:^M^J^M^J

;;;CAPTURE &&MESSAGEPATH&&FORUMNAME.MSG

GO &&GATEWAY:&&FORUMNAME

;

; Join Forum If Required!

;

  %IF NOT JOINED

    %@REMOVEACTION &&FORUMNAME Join.Forum

    %%ECHO Attempting to Join &&FORUMNAME, &&FORUMTITLE

    %%JOIN

        %%%ECHO Successfully Joined &&FORUMNAME, &&FORUMTITLE

  	%%%REMOVEACTION &&FORUMNAME Join.Forum

        %%WAIT !

        %%@ECHO Sorry, unable to Join &&FORUMNAME, &&FORUMTITLE

        %%@SETERRORLEVEL 0 FALSE

;

; Set Session Defaults to Command Mode for Forum Processing

;

;--------------I HAVE REMOVED THE FOLLOWING TO SAVE TIME UPON EACH

;--------------ENTRY TO A FORUM

;--------------THIS MODIFICATION ASSUMES YOU HAVE SET THE PROMPT TO ^G

;--------------PERMANENTLY.  See [Set Forum Defaults] for more.

;;;  %ECHO Setting Temporary Session Defaults in &&FORUMNAME, &&FORUMTITLE

;;;  %SEND OPT;INI;1;MOD;3;EDI EDIT;PAU N;REP LIST;TYPE N;SKIP N;CHAR;S^M

;;;  %WAIT New prompt:

;;;  %%SEND ^^G^M

;;;  %WAIT FORUM !

;;;    %@SETERRORLEVEL 0 FALSE

;

  @ECHO Sorry, unable to enter the &&FORUMNAME Forum!

  %ECHO Now in &&FORUMNAME, &&FORUMTITLE

;

; Check for Waiting Messages in the &&FORUMNAME Forum

;

  %IF MESSAGESWAITING

    %@ECHO No Messages Waiting to be Read On &&FORUMNAME, &&FORUMTITLE

    %@REMOVEACTION &&FORUMNAME Read.Waiting.Messages

    %%ECHO Reading Waiting Messages of &&FORUMNAME, &&FORUMTITLE

    %%SCAN &&MESSAGEPATH&&FORUMNAME.MSG READ WAIT

    %%REMOVEACTION &&FORUMNAME Read.Waiting.Messages

;

;------------------------------------------------------------------------

;Check to see if there's an upload file

;------------------------------------------------------------------------

%IF FILEEXISTS &&CONTROLPATH&&FORUMNAME.UPL

  %@ECHO NO &&CONTROLPATH&&FORUMNAME.UPL TO EXECUTE

  %%ECHO Executing upload script: &&CONTROLPATH&&FORUMNAME.UPL

  %%DO &&CONTROLPATH&&FORUMNAME.UPL

  %%%KILLFILE &&CONTROLPATH&&FORUMNAME.UPL

  SETERRORLEVEL 2 TRUE

[GO LIB]

;

; Lets enter Library #&&LIBRARY of &&FORUMNAME

  %LIB &&LIBRARY

;

; If something goes wrong... Inform the user and bypass this Library!

;   Otherwise all is well... Continue processing (downloads, catalogs, etc)

;

    %@ECHO Sorry, unable to enter Library #&&LIBRARY of &&FORUMNAME, &&FORUMTITLE

    %%ECHO Now In &&FORUMNAME, &&FORUMTITLE Libraries

;

[JOIN FORUM]

;

; Commented Out Since It's Done at GO FORUM Automatically

; Join The Forum

;

;  %IF NOT JOINED

;    %@REMOVEACTION &&FORUMNAME Join.Forum

;    %%ECHO Attempting to Join &&FORUMNAME, &&FORUMTITLE

;    %%JOIN

;       %%%ECHO Successfully Joined &&FORUMNAME, &&FORUMTITLE

;       %%%REMOVEACTION &&FORUMNAME Join.Forum

;       %%@ECHO Sorry, unable to Join &&FORUMNAME Forum!

[SET FORUM DEFAULTS]

;

; Set Permanent Session Defaults to Command Mode for Forum Processing

;

  %ECHO Setting Permanent Session Defaults in &&FORUMNAME, &&FORUMTITLE

;;;  %SEND OPT;INI;1;MOD;3;EDI EDIT;PAU N;REP LIST;TYPE N;SKIP N;P^M

;--------------------------------------------------------------------

;This modification to the Set Forum Defaults section also sets the

;character prompt to ^G.  This means you do not have to set temporary

;defaults each time:

  %SEND OPT;INI;1;MOD;3;EDI EDIT;PAU N;REP LIST;TYPE N;SKIP N;CHAR;P^M

  %WAIT New prompt:

  %%SEND ^^G^M

;--------------------------------------------------------------------

  %WAIT FORUM !

  %REMOVEACTION &&FORUMNAME Set.Defaults

[UPDATE FORUM SECTIONS]

;

; Read the Section Descriptions

;

  %ECHO Updating &&FORUMNAME, &&FORUMTITLE Message And Library Descriptions

  %KILLFILE &&CONTROLPATH&&FORUMNAME.SEC

  %READ &&CONTROLPATH&&FORUMNAME.SEC NAM;1;2;M

  %REMOVEACTION &&FORUMNAME Update.Sections

[READ FORUM ANNOUNCEMENTS]

;

; Read the &&FORUMNAME Forum Announcements

;

  %ECHO Reading &&FORUMNAME, &&FORUMTITLE Announcements

  %READANN &&MESSAGEPATH&&FORUMNAME.MSG

  %REMOVEACTION &&FORUMNAME Read.Announcements

[GO MESSAGES]

;

; Enter Message Area of the &&FORUMNAME Forum

;

  %MESSAGES

;

; If something goes wrong... Inform the user and bypass the Message Area!

;   Otherwise all is well... Continue processing (READS, SCANS, ...)

;

   %@ECHO Sorry, unable to enter Message Area of &&FORUMNAME, &&FORUMTITLE

   %%ECHO Now In &&FORUMNAME, &&FORUMTITLE Message Area

;

;------------------------------------------------------------------------

;WCUTIL LOGIC TO SEE IF THERE IS A SPECIAL REQUEST RM FILE

;------------------------------------------------------------------------

;Check ErrorLevel 9 before deleting RM file

   %%IF FILEEXISTS &&CONTROLPATH&&FORUMNAME.RM

     %%@ECHO NO &&CONTROLPATH&&FORUMNAME.RM TO EXECUTE

     %%%ECHO Executing message requestscript: &&CONTROLPATH&&FORUMNAME.RM

     %%%DO &&CONTROLPATH&&FORUMNAME.RM

     %%%Wait !

     %%%?????%Echo Deleting &&CONTROLPATH&&FORUMNAME.RM

     %%%?????%KILLFILE &&CONTROLPATH&&FORUMNAME.RM

;------------------------------------------------------------------------

;WCUTIL LOGIC TO SEE IF THERE IS A SPECIAL REQUEST QM FILE

;------------------------------------------------------------------------

;Check ErrorLevel 9 before deleting QM file

;Set ErrorLevel 10 to be used by WinCIS SCAN HEADER

   %%IF FILEEXISTS &&CONTROLPATH&&FORUMNAME.QM

     %%@ECHO NO &&CONTROLPATH&&FORUMNAME.QM TO EXECUTE

     %%@SETERRORLEVEL 10 FALSE

     %%%ECHO Executing message request script: &&CONTROLPATH&&FORUMNAME.QM

     %%%DO &&CONTROLPATH&&FORUMNAME.QM

     %%%Wait !

;     %%%%KILLFILE &&CONTROLPATH&&FORUMNAME.QM

     %%%?????%Echo Deleting &&CONTROLPATH&&FORUMNAME.QM

     %%%?????%KILLFILE &&CONTROLPATH&&FORUMNAME.QM

     %%%?????%SETERRORLEVEL 10 TRUE

[READ FORUM MESSAGES]

    %%READ &&MESSAGEPATH&&FORUMNAME.MSG READ THR NUM:&&READMSGNUMBER

[RESET READ FORUM MESSAGES]

;

;  At this point no messages need to be read so Kill Then Read Msg Index

    %%REMOVEACTION &&FORUMNAME Read.Messages

    %%KILLFILE &&CONTROLPATH&&FORUMNAME.MXS

[READ WAITING FORUM MESSAGES]

;

; Commented Out Since It's Done at GO FORUM Automatically

; Check for Waiting Messages in the &&FORUMNAME Forum

;

;  %%IF MESSAGESWAITING

;    %%@REMOVEACTION &&FORUMNAME Read.Waiting.Messages

;    %%@ECHO No Messages Waiting to be Read On &&FORUMNAME, &&FORUMTITLE

;    %%%ECHO Reading Waiting Messages of &&FORUMNAME, &&FORUMTITLE

;    %%%SCAN &&MESSAGEPATH&&FORUMNAME.MSG READ WAIT

;    %%%REMOVEACTION &&FORUMNAME Read.Waiting.Messages

[READ NEW FORUM MESSAGES]

;

; Read New Messages in the &&FORUMNAME Forum

;

    %%ECHO Reading New Messages of &&FORUMNAME, &&FORUMTITLE in Sections &&MSGSECTIONS

    %%SCAN &&MESSAGEPATH&&FORUMNAME.MSG READ NEW &&MSGSECTIONS

    %%REMOVEACTION &&FORUMNAME Read.New.Messages

[QUICKSCAN FORUM MESSAGE HEADERS]

;

; Scan For New Messages Threads in the &&FORUMNAME Forum and Overwrite existing File

;

;;;    %%ECHO Scanning For New Threads of &&FORUMNAME, &&FORUMTITLE in Sections &&MSGSECTIONS

;;;    %%KILLFILE &&CONTROLPATH&&FORUMNAME.MQS

;;;    %%SCAN &&CONTROLPATH&&FORUMNAME.MQS SCAN QUICK NEW &&MSGSECTIONS;T

;------------------------------------------------------------------------

;Added for WCUTIL compatibility:  the check for Error Level 10 before deleting MQS

;------------------------------------------------------------------------

    %%ECHO Scanning For New Threads of &&FORUMNAME, &&FORUMTITLE in Sections &&MSGSECTIONS

      %%???????@ECHO No custom message scan; deleting old header file

      %%???????@KILLFILE &&CONTROLPATH&&FORUMNAME.MQS

      %%???????%ECHO Merging standard message scan with custom scann

    %%SCAN &&CONTROLPATH&&FORUMNAME.MQS SCAN QUICK NEW &&MSGSECTIONS;T

    %%REMOVEACTION &&FORUMNAME Scan.New.Messages

[SEND FORUM MESSAGE]

;

; Sending Queued Messages and Replies to the &&FORUMNAME Forum

;

    %%ECHO Sending Queued Messages and Replies to &&FORUMNAME, &&FORUMTITLE

    %%SENDMSGS &&MESSAGEPATH&&FORUMNAME.SND

[PROMPT MESSAGE OUTBOX]

;

; Ask what to do about copying the OutGoing Messages

;

   %%%ASK OVERWRITE? &&CONTROLPATH&&FORUMNAME.MOX  Do you want to save your outgoing &&FORUMNAME Messages in &&MESSAGEPATH&&FORUMNAME.MOX?

   %%%%ECHO Saving your outgoing Messages to &&MESSAGEPATH&&FORUMNAME.MOX

   %%%%FILEMARK  &&MESSAGEPATH&&FORUMNAME.MOX MESSAGES_SENT &&FORUMNAME

   %%%%COPYFILE  &&MESSAGEPATH&&FORUMNAME.SND &&MESSAGEPATH&&FORUMNAME.MOX

; At This point the Message File Is No Longer Needed

   %%%REMOVEACTION &&FORUMNAME Send.Replies

   %%%KILLFILE &&MESSAGEPATH&&FORUMNAME.SND

[APPEND MESSAGE OUTBOX]

;

; Append Queued Messages and Replies to the &&FORUMNAME Forum OutBox

;

   %%%ECHO Appending your outgoing &&FORUMNAME Messages to &&MESSAGEPATH&&FORUMNAME.MOX

   %%%FILEMARK &&MESSAGEPATH&&FORUMNAME.MOX MESSAGES_SENT &&FORUMNAME

   %%%COPYFILE &&MESSAGEPATH&&FORUMNAME.SND &&MESSAGEPATH&&FORUMNAME.MOX

; At This point the Message File Is No Longer Needed

   %%%%REMOVEACTION &&FORUMNAME Send.Replies

   %%%%KILLFILE &&MESSAGEPATH&&FORUMNAME.SND

;

[OVERWRITE MESSAGE OUTBOX]

;

; Overwrite Queued Messages and Replies to the &&FORUMNAME Forum OutBox

;

   %%%ECHO Saving your outgoing &&FORUMNAME Messages in &&MESSAGEPATH&&FORUMNAME.MOX

   %%%%KILLFILE &&MESSAGEPATH&&FORUMNAME.MOX

   %%%FILEMARK  &&MESSAGEPATH&&FORUMNAME.MOX MESSAGES_SENT &&FORUMNAME

   %%%COPYFILE  &&MESSAGEPATH&&FORUMNAME.SND &&MESSAGEPATH&&FORUMNAME.MOX

; At This point the Message File Is No Longer Needed

   %%%%REMOVEACTION &&FORUMNAME Send.Replies

   %%%%KILLFILE &&MESSAGEPATH&&FORUMNAME.SND

[DELETE MESSAGE OUTBOX]

;

; Never Save Queued Messages to the &&FORUMNAME Forum OutBox

;

   %%%ECHO Deleting outgoing Messages: &&MESSAGEPATH&&FORUMNAME.SND

; At This point the Mail File Is No Longer Needed

   %%%REMOVEACTION &&FORUMNAME Send.Replies

   %%%KILLFILE &&MESSAGEPATH&&FORUMNAME.SND

[SET HIGH MESSAGE COUNTER]

;

; Set The High Message Counter to High Values

;

    %%SEND HIGH;L^M

    %%WAIT !

[OVERWRITE MESSAGES]

;

; Create New or Erase Existing &&FORUMNAME.MSG File if found to exist.

;

    %%KILLFILE &&MESSAGEPATH&&FORUMNAME.MSG

[PROMPT CATALOG]

;

; Ask what to do if a Library Catalog exists for this Forum on Disk

;

   %%IF FILEEXISTS &&CONTROLPATH&&FORUMNAME.LBR

   %%%ASK OVERWRITE? &&CONTROLPATH&&FORUMNAME.LBR  Do you want to Overwrite or Append to the &&FORUMNAME Catalog File?^M^J&&CONTROLPATH&&FORUMNAME.LBR

   %%%@SETERRORLEVEL 3 FALSE

   %%@SETERRORLEVEL 3 TRUE

[APPEND CATALOG]

;

; Append to Existing Library Catalog

;

   %%SETERRORLEVEL 3 TRUE

[OVERWRITE CATALOG]

;

; Overwrite the existing Catalog

;

   %%KILLFILE &&CONTROLPATH&&FORUMNAME.LBR

   %%SETERRORLEVEL 3 TRUE

[SHORT CATALOG SCAN]

;

; Requesting Download Information on &&SCANDESC

;

    %%%ECHO Scanning Libraries of &&FORUMNAME, &&FORUMTITLE

    %%%SCAN &&CONTROLPATH&&FORUMNAME.LBR LIST &&SCANFILE &&SCANLIBS &&SCANAGE &&SCANKEYWORDS

    %%%REMOVEACTION &&FORUMNAME Scan.Libraries

;

[FULL CATALOG SCAN]

;

; Requesting Download Information on &&SCANDESC

;

    %%%ECHO Scanning Libraries of &&FORUMNAME, &&FORUMTITLE

    %%%SCAN &&CONTROLPATH&&FORUMNAME.LBR SCAN &&SCANFILE DES &&SCANLIBS &&SCANAGE &&SCANKEYWORDS

    %%%REMOVEACTION &&FORUMNAME Scan.Libraries

;

[RESET SCAN CATALOG]

;

;  At this Point Library Scans are Complete so Kill Then Search Pattern Index

;

    %%%KILLFILE &&CONTROLPATH&&FORUMNAME.LXC

[DOWNLOAD FILES]

    %%DOWNLOAD &&DOWNLOADFILE &&DOWNLOADPATH &&DOWNLOADUPLD

;          Title: &&DOWNLOADTITLE

;          Library# &&LIBRARY, &&DOWNLOADSIZE Bytes, As of &&DOWNLOADDATE

;

[RESET DOWNLOAD FILES]

;

;  At this Point Downloads are Complete so Kill Then Download Tag List

;

    %%REMOVEACTION &&FORUMNAME Download.Files

    %%KILLFILE &&CONTROLPATH&&FORUMNAME.LXR

[UPLOAD FILES]

;

; Sending Files

;                           <To be defined>

    %REMOVEACTION &&FORUMNAME Upload.Files

;

;***************************************************************

;* WinCis Commands Commands  Left out of this help file*

;***************************************************************


Turning Off Distribution Lists

By default CIS includes a list of all addressees at the end of your mail message.  There is no way (currently) to turn this off on a message by message basis from WinCIS or WCUTIL.  If you do not want a distribution list included in your messages you must change this option on the CIS end of things.  Go to the CompuServe Mail prompt manually (in interactive mode) and type SET.  This will bring up the mail options menu.  Select option 6, set it to No, and answer Yes when asked if you want to make this change permanent.