FILE RUNNER ----------- ©1992 Karl-Erik Ruud Freeware This progam is Freeware, non-military use only. You are allowed to copy it to anyone for free. All files in this .lzh archive MUST be included if you repack it to another format. All files MUST be included if you copy it to your friends, bulletin boards or public domain disk libraries (like Fred Fish). You are hereby advised NOT to crunch the program or the external files it uses (or the program may not work). This doc file must remain unchanged. You are not allowed to get the program code, to hack the program or patch it in any way. If you have problems running File Runner on your Amiga, please let me know and I'll try to fix it for you. Use this program at your own risk. I may not be responsible for system crashes, lost data, disk errors or other errors using this program. If you suspect that someone has put a virus into File Runner, please let me know. Included in this .lzh archive is: File_Runner_1.x Wb 1.0, 1.1, 1.2 and 1.3 version File_Runner_2.x Wb 2.0 and 3.0 version extend.library version 1.41 by HiSoft reqtools.library version 1.0a by Nico Francis The libraries should be copied to your libs: directory. Also needed are the commands Run and NewCli (they are in the c: directory on Wb 1.x versions, and in rom in Wb versions 2.0 and above). The version of the program that you will use (either File_Runner_1.x or File_Runner_2.x) should be renamed to File_Runner. The only differences between is that File_Runner_1.x looks check if c:Run and c:NewCli are present. If you run this version on 2.0 or 3.0 Wb's, the program will report that c:NewCli is missing, and then quit. I tried to make a check in the program for the version of intuition.library (as I have done in Scriptconvert), but no matter how I did it, it wouldn't work (I only got guru 8000000B all the time). If I would have managed this then two versions of the program would not had been neccesary. Sorry about that! File Runner is a program that will let you run programs like the Execute Command function of Workbench 2.0. Therefore you might wish to not run it from Wb 2.0... :-) First the program will check that all external files it uses are present. If not, it will inform you about the missing one. Then it opens a small window on the Workbench screen. Click anywhere in the window to execute a command, or quit by clicking the close gadget on the left side (or press Ctrl-c). When you have clicked in the window, a string requestor will appear, asking you to enter the command you wished to be carried out. Type the command and press enter (or click the Ok button), or click on the Cancel button to abort (if you don't type anything the function will also be cancelled). Now File Runner will propably execute your command. If not, click again, and enter '-w ' in front of your command (that will be remembered). This will open a Cli and execute your command from the Cli window. Unfortunately you will have to close the Cli yourself (I tried to put in a function that ended the Cli, but it wouldn't work). I tried to get File Runner to open the Cli if the '-w ' wasn't present and a normal run would fail, but I ran into several problems. I discovered that to check if your task was running, File Runner had to know exactly how to spell the tasks name. F.ex. would not DISKMASTER or diskmaster work, it had to be DiskMaster (as spelled on the disk). And also if you had included some of the options of the program to be runned, how should I make the program know that it is not a part of the program name? So I decided to only use the '-w ' option. History Version 1.0 The program does not check the Workbench version because of something totally unknown to me (a bug in Workbench?). The Wb 2.0 version does not look for Run and NewCli in the c: directory. Unfortonuately extend.library has to be used, because the Execute() library function does not work as I supposed it should. ReqTools.library is used only for the good looking requestors. The program does not try to run a program specified without the '-w ' option from a Cli if it didn't start, because of problems finding the task of programs that was actually started. This resulted in that the command was executed two times. Programs that have to be runned from Cli/Shell has to have the '-w ' option in front of the command. Bugs If you run the 1.x version on Wb 2.0 or higher, it will fail because it look for NewCli and Run in the c: directory. Some programs will not start. Use the '-w ' option if you have problems. Because extend.library not can be used by different tasks at the same time, you may get a requestor telling you that "LIBRARY NOT FOUND..." or "FILE NOT FOUND...". Try to not use the '-w ' option. If it still doesn't work, you have to quit File Runner and start the program the normal way. Plans for the next version I will investigate more about how I can make the program look for the version of Wb, and hopefully put that into the program. All gadgets will be stored inside the program, so reqtools.library will not be needed. Execute() will hopefully be used instead of extend.library's Dos() command. There will be separate fields for program name, options, text file names, Ilbm picture, tracker module and AmigaDos scripts. File Runner will check directly on the disk for exact spelling of program names for task checking. The '-w ' option will then be used automaticly if the task refuses to run. External file viewers might be defined in a config file to view/edit text, pictures and modules. Guarantee No guarantee at all - sorry! Use the program at your own risk. I'll try to fix the program according to your wishes - just let me know! You can reach me at the following address: Karl-Erik Ruud Platous gate 27 N-0190 Oslo NORWAY Tel: +47-2-174422