June 22, 1993 This version of Autorobo is completely changed from the previous versions and a number of bugs have been corrected. ========================================================================= Changes: Agenda actuation separate from Robocomm. Actuation of agendas based on date and time rather than sequentially as with the previous versions. Daily, every other day, weekly and monthly scheduling. Neater screens with more bells and whistles. Elimination of agenda descriptions different from displayed description for ease of setup and to preserve environment space. ========================================================================= To clarify things Autorobo uses "EVENTS" to run Robocomm "AGENDAS." Autorobo is a 4dos/Ndos program I wrote for my own use. It will schedule up to 9 events for up to 9 Robocomm agendas to be run on either a daily, every second day, weekly, monthly (every 30 days) or one time basis. Keep In mind that Robocomm agendas can be set to call numerous BBSs on specific days of the week so the combinations are limitless. Autorobo will import Robomail .qwk files, and pack Robomail and Robocomm on a daily basis, every second day basis, a weekly basis, a monthly (every 30 days) basis or at scheduled dates and times. I have Autorobo run scheduled events then import the .qwk files to Robomail, delete duplicate files to a selected BBS with DUP40 and pack Robomail and Robocomm during the night. In the morning Robocomm and Robomail are ready to go. *DUP40 is available from Groupone or most BBSs. Look for DUP40.ZIP =========================================================================== **** Caution **** If you run this program it will create a file C:\arlst.lst in which to store all Autorobo environment variables when you save the configuration . It will not affect your normal environment variables. Autorobo also uses this file to store the changes after an agenda has been run and the Active flag has been turned off. In the case of Daily, every second day, weekly or monthly events the date of the next event is stored and the flag in not reset. If you have a file named C:\arlst.lst it will be deleted so I suggest you rename either your file or, using a text editor, the path or the name arlst.lst wherever it occurs. In effect, Autorobo will always remember where it left off and when to run the next daily, every second day, weekly and\or monthly event. ========================================================================== Getting Started Autorobo is a snap to use. Unzip the files into any directory in your path. Robocomm.exe, Dup.exe and Robomail.exe must also be in your path as Autorobo will look for them. They should be in your path anyway. Edit the file "AREVENT.MNU with a text editor and change the names of the events I have left in AREVENT.MNU as examples to the exact names of agendas you have in Robocomm. Make sure to leave the first column blank. There is no limit that I know of as to how many events you can put in AREVENT.MNU. When running Autorobo for the first time it is advisable to enter each agenda menu and clear the agenda by selecting "Clear Event" from the menu. When all events have been cleared save everything by pressing "S" at the main menu. If you do not do this the word "(NULL)" will appear in certain places. "(NULL)" won't do any harm and will disappear as soon as you use the specific event. Besides, it can't hurt to start clean. =========================================================================== I think the menus for setting up the events are pretty straight forward. Try them and watch the settings above the menu box to see what they do. In the event set up menus (1-9) a "." or maybe 2 "." will appear. Ignore them they do nothing but clear the tail ends of long event names when short named events are selected. The active scheduled Events run in order of date and time. If an event is still operating at the time for which another event is scheduled the event will run immediately after the currently running event finishes. If all events are scheduled for the same time or fall into a period when an event is running they will be executed in numeric order. The exception is if you schedule a time but no date. If there is no date scheduled Autorobo will run the event at the next occurrence of that time. If another event is running it will miss the time. It is always safest to schedule a date. If you have no time and date and the event is active Autorobo will not run the event. To the right of the individual events on the main screen the letters A, R, D, W, M or 2 will appear. these signify the event has been set as follows: A = Active R = Reset is on D = Daily W = Weekly M = Monthly 2 = Every second day The easiest way to use Autorobo is to assign an event name to events 1-9 and select "Set all for now" under the event menu. You can then alter the time, date and\or active status from that point. The Daily, weekly, every second day and monthly events will be run at the specified time and then the date reset accordingly. They will always be active when Autorobo is running. If an event is selected as "A"ctive the active status will be cleared after the event has been run. To run an event immediately simply select the event (1-9) from the main menu and select "Set all for NOW." This inputs the current time and date and makes the event active. ESC to the main menu and select "R"un and all the active events will run immediately. If you do this at 23:59:59 and select "R"un at 00:00:01, tough, it's the next day. Besides, I've included a 20 second delay at midnight so any event scheduled between 00:00:00 and 00:00:20 won't run until 00:00:21. If Autorobo is started by the command line or autoexec.bat the command "AR.BTM RUN" it will begin to run the active scheduled events. In the event of a power failure the program will reset when the computer reboots and pick up where it left off as long as you have "ar.btm run" in your autoexec.bat file. In order for this to work the completed schedule must be saved before it is run. When Autorobo is exited all events not saved will be lost and the last saved configuration will be reloaded. If Autorobo is not exited the current events will be retained in memory even if they are not saved. This allows you to change and run a usually daily event for instance without affecting the original setting. If a daily, every second day, weelky or monthly event is run in the interim Autorobo saves the new run dates and you will have to manually reset the original status. It is Robocomm that keeps track of whether a Robocomm agenda has been run and completed so robocomm will give the program back to Autorobo if it sees that there is "Nothing to Run." If Autorobo attempts to run an event and Robocomm immediately returns to Autorobo without doing anything Robocomm sees its agenda as completed. Use the reset command to run the event under any circumstances. The reset option can be selected and will cause Robocomm to reset an agenda and run it whether it has been previously completed or not. Use reset with care. The use of the reset option should be reviewed in the Robocomm docs. When selecting an event to run daily, every second day, weekly or monthly it is best to always turn the reset command on. If a scheduled event is not Active it will not be run. A few notes: I use a fair amount of environment variables so if you get an "out of environment" message increase the size of your environment both in the config.sys file and the 4dos.ini or Ndos.ini files. Config.sys shell=I:\4dos.com @c:\4dos.ini /P /e:2048 4dos.ini ENVIRONMENT = 2048 There is a "Load" option on the main menu. This function will reload the last saved configuration. I pretty much use this program in specific ways and there might be bugs of which I am unaware. If you have any problem and\or find a bug I'd like to know about it. I intend to improve on Autorobo so any suggestions would be appreciated. I can be reached at: Ted Thompson 4855 Hyde Road Manlius, NY 13104 315-682-7703 Or on the Ilink Robocomm conference. If you like and use Autorobo a $10.00 contribution towards the time I've put into the program would be greatly appreciated.