home *** CD-ROM | disk | FTP | other *** search
- Task Macro - A {COMMO} timed execution facility
- Copyright (c) 1992 Joe Hayashi
-
-
- -----------------------------------------
- INTRODUCTION
- -----------------------------------------
-
- TASK.MAC is a set of {COMMO} macros that allow you to automatically
- execute DOS programs at any time of the day on any day of the week.
- With some clever macros, you'll have {COMMO} acting as your electronic
- valet, dialing BBSs in the middle of the night to get mail mail, files,
- and news. Any DOS program you can run unattended is ideal for use
- with TASK.MAC.
-
- TASK.MAC is not a TSR, it is designed to take over your computer and
- work while you are asleep or away. You must have {COMMO}, a terrific
- terminal program written by Fred Brucker, for TASK.MAC to work.
-
- To make TASK.MAC work, you need to put the file TASK.MAC and TASK.TXT
- in your commo directory. TASK.TXT is the schedule file that TASK.MAC
- reads and acts upon. The structure of TASK.TXT is outlined below.
-
- I've have included some other files in this package as well. The
- CIS.MAC macros are some macros I use to automate some of my time on
- compuserve. They are provided so that you can give TASK.MAC something
- to do right away. The SED.ZIP package includes some SED scripts that
- make the text files created by CIS.MAC easy to read.
-
- -----------------------------------------
- TASK.MAC
- -----------------------------------------
-
- Getting started:
-
- Move both TASK.MAC and TASK.TXT into your commo directory. If you
- want an easy way to launch TASK.MAC, you can use the included BYE.BAT
- file. BYE.BAT just launches commo with TASK.MAC loaded and runs the
- :start macro. To use BYE.BAT, put it on your DOS path.
-
- Here is BYE.BAT:
-
- @echo off
- cd \commo
- commo /mtask.mac /:start
-
- You may need to change a couple things in TASK.MAC to make sure that
- it will work for you. There are two lines in TASK.MAC that begin
- with an exclamation point. Double check these lines to make sure they
- jive with your setup. You may need to edit BYE.BAT if commo does not
- reside in a directory off of your root diretory.
-
- The last thing you need to do is to edit the TASK.TXT file to include
- the commands you want to run. You'll notice that there are already a
- fair number of commands I've included for you. All of the CIS.MAC
- macros are used as well as some dummy commands.
-
- The structure of the TASK.TXT file is pretty simple. Here are two
- sample lines.
-
- #time mtwtfss command line <-- comment line
- 06:00 y y y commo /:apo <-- task line
-
- The first line is a comment line. All lines that begin a "#" (sharp)
- character are ignored.
-
- The second line is a task line. It includes the time of day to
- execute the task, the days of the week on which to execute the task,
- and the task itself.
-
- I've included the comment line to make the structure of task lines
- clearer. It is unnecessary to include this comment line in your
- TASK.TXT file.
-
- The first item is the 24 hour time of day to execute this task. In
- this example the execution time is 6am.
-
- Next is a series of seven characters, either a "y" or a " " (space)
- character. These seven character tell TASK.MAC on which days to
- execute your task. The character directly below the first "m" on
- the comment line tells TASK.MAC whether on not to execute this task
- on Monday. If there is a "y" in this space, it will execute. If
- there is a space " " here, it will not. This task will be execute
- at 6am on Monday, Wednesday, and Friday.
-
- The third item, starting in the 15th position on line two is the
- full DOS command line to be executed. In this case the command
- "commo /:apo" (start commo and run the :apo macro) will be executed.
-
- The last thing you need to remember about the TASK.TXT file is that
- the commands need to be sorted in order of execution times. If your
- text editor doesn't sort things, have the DOS sort command do it.
- From DOS, type "type task.txt | sort > task.new". Delete task.txt
- and rename task.new to task.txt.
-
- -----------------------------------------
- CIS.MAC files
- -----------------------------------------
-
- What do these files do?
-
- I've included the CIS.MAC files so that you can actually have
- TASK.MAC do something for you in case you haven't any macros of
- your own. The CIS.MAC macros are for users of Compuserve. If
- you aren't a member, these macros won't do diddly.
-
- I have included macros to get AP Headlines News, Online Today,
- PCWeek and MacWeek newsbriefs, and What's New for both Compuserve
- and Ziffnet.
-
- The easiest way to use the CIS.MAC files is to append them to your
- COMMO.MAC file. Type "copy commo.mac + cis.mac" in your commo
- directory to accomplish this.
-
- To use CIS.MAC you _must_ add an entry to your commo.fon file. The
- name of the entry must be "Auto_cis" and it must include your
- Compuserve password and the number you dial to access compuserve.
- I've included a simple file ADD.FON with instructions if you'd rather
- not add the number yourself. You can append this file to your
- COMMO.FON file by typing "copy commo.fon + add.fon". You'll still
- must edit the file to include your password and access phone number.
-
-
- -----------------------------------------
- SED.ZIP
- -----------------------------------------
-
- The files packed in SED.ZIP are SED scripts used (optionally) by
- the CIS.MAC macros files to make the files created by the CIS.MAC
- macros more readable.
-
- You need to put the *.sed files in your commo home directory. You
- also need to get your hands on a DOS version of SED. There are two
- in the Unix forum on Compuserve in library 13 (go unix, library 13
- "DOS under UNIX"). One is called SED.ZIP, the other is called
- TC-SED.ZIP. The TC-SED.ZIP executable has at least one known bug
- (the "not" command (!) is broken). I recommend SED.ZIP it's bigger
- and slower but it seems to work more like a Unix version. The code
- comes from the FSF. As far as I know, both are in the public domain.
-
- SED stands for stream editor. It's a standard Unix tool that carries
- out series of editing commands on a text file. Yes, it can be
- difficult to use. I make no claim of being a SED master; I'm sure
- these files could be improved. But heck, if they work for me, they
- might work for you.
-
- If you find that you love SED and want to write your own scrips, I
- would check out a book on Unix. SED works well with commo because
- all of the commo support files are plain text. It's fairly trivial
- to write a script that appends BBS listins to your commo.fon file,
- eliminating the need for you to add all those curly braces by hand.
- There are undoubtedly dozens of other good uses for SED and I am sure
- that clever and prudent use of SED might someday save the world.
-
-
- -----------------------------------------
- ADMINISTRIVIA
- -----------------------------------------
-
- 1) This distribution is Good Deed Ware. If I've done you a good
- deed by writing these macros, then do a good deed for someone else
- today.
-
- 2) TASK.MAC and the CIS.MAC macros are Copyrighted to Joe Hayashi
- (c) 1992. You may distribute these files only in an unmodified form.
- You may not distribute any of these files as part of a larger software
- distribution without my prior written consent.
-
- 3) I don't guarantee anything about any of these files. Your use
- of these files constitutes an agreement to not to hold me responsible
- for any damage your do to your computer system as a result of your
- use of these files.
-
- 4) All trademarks used within are registered trademarks of their
- respective companies.
-
- 5) Please send bug reports, comments & questions to:
-
- Joe Hayashi 70754.1164@compuserve.com
-
- Thanks for trying TASK.MAC. Take care.
-
- -Joe
-