HOMERUN V1.02 GENERAL HELP Index 1.0 Introduction 2.0 Installation 3.0 Scheduling Program Starts & Kills 3.1 Start-ups 3.2 Kills 4.0 Appointment/Message Daily Diary 5.0 Calendar 6.0 Disclaimer 7.0 Bugs and Suggestions 1.0 Introduction Homerun allows programs to be run on any time schedule. Homerun can start & terminate OS2, Dos and WinOS2 (Windows) programs in a window, fullscreen or Presentation Manager as applicable. Dos & OS2 windows can also be closed using hexadecimal commands. Convenient red/green buttons confirm whether the start-ups and kills are active or inactive. If you have installed any OS2 FixPaks after Warp 3 it is recommended that you read the file rexxsom.txt included in the Homerun directory. The appointment/message scheduler allows simple multiple scheduling, and has a programmable warning alarm. 2.0 Installation Homerun can be installed from its own directory or from a floppy drive. The installation program will install an icon on the desktop. To install from its own directory unzip the files into a directory of choice (default is C:\HOMERUN), and at the C:\HOMERUN> prompt type INSTALL. To install from a floppy, at the A:> prompt type INSTALL. Homerun requires the runtime library file VROBJ.DLL and it is in the hrun100.zip file. If you already have VROBJ.DLL installed, you do not need this file. VROBJ.DLL can remain in the Homerun directory or can be moved to a directory listed in the LIBPATH list defined in the configuration file config.sys. To minimize CPU time, Homerun only status checks every 20 seconds. Between these checks there is no demand on the CPU. If you are watching, this delay can sometimes give the impression of being slow to respond to changes. Just remember, we are saving resources! In 'Settings' there is a preferences file which can remove some of the pop-up boxes for the experienced user. Note: A 'System Proportional Italic' font is used in Homerun to distinguish inputted data. In one test computer at 1024x768 there were slight imperfections in the appearance of the font. I have stuck with the italic font, but please let me know if there are other systems with this problem, and I will change the font back to a normal font. 3.0 Scheduling Program Starts & Kills 3.1 Start-ups Click on 'Events' in the 'Schedule' drop down menu. There are hints shown at the bottom of most windows to assist in entering data. There is virtually no limitation on how you can set up the start-ups. For OS2 programs, It is best to start with the 'Default' setting and to test your choice by clicking on 'Run now' and then 'Terminate now' if you are using this feature. It is unlikely that incorrect set-up of a program will crash the program, but in some cases the program may not run as scheduled. It is wise to test the start-up by clicking the 'Run now' button before saving it to the container list. DO NOT run Dos and Windows programs with the 'Default' setting. Although they may generally run, Homerun does not keep track of the session PID number and can not terminate it. The file extension must be included in order for the search check to work properly although the 'Terminate after X minutes' will still work properly. For 'Dos Window' and 'Dos Fullscreen' applications (including WinOS2 applications started in dos, the 'Terminate after X minutes' option, keeps track of the start-up PID number and uses that that to terminate the program. If several programs are started at the exact same time, Homerun could grab the wrong PID number, so it is best to stagger Dos start-ups by at least a minute. Windows programs may only run in full screen and are tricky. Success in making windows programs run depends on the video resolution and other factors. Also, you should enter the directory that is the working directory for the program you are running. For example enter: Entry Title: Windows Eudora Program path & file name: eudora.exe Parameters: Directory: c:\eudora to run Eudora. The 'Run in a WinOS2 Window session' only runs if the video resolution is 640x480. Terminating of windows programs is not supported, other than you can terminate a windows program YOU start through Dos. Although if you were able to send a hexadecimal 'ALT-F' and 'x' via the 'Use macro' you would think it should work. Hints: 1. If you intend to start-up a 'Run in a WinOS2 Fullscreen session' while you have a 'Dos Fullscreen' session active, the Dos session should be started in the background or questionable results may occur. 2. OS2 Windows do not start in the 'Background'. Use the 'Min' box and start minimized. 3. Fullscreen programs do not start minimized. Use the 'Background' box and start in the background. 4. Thanks to Andy Glass who offered that: cmd.exe /c detatch [path]/homerun.exe will run Homerun in 4OS2. 3.2 Kills The 'kills' use a program called 'go' written by Carston Wimmer, and further information about this program can be found in the file go.doc. You can send keystroke commands and hexadecimal keystrokes to a Dos or OS2 window by activating the 'Use macro' button and completing the entry fields. For example enter: Window Title: DOS Window Macro: exit to close a dos window. Note: This feature uses the clipboard and it must be active. The 'Program started in an OS2 Window' check box is to be used for programs started in an OS2 Window or started with a .cmd batch file. For example, Maximus could be started with a batch file 'max.cmd'. In this case the executable to be entered would be the Maximus 'maxp.exe' file and the 'Program started in an OS2 Window' box should be checked in order that the OS2 window is closed at the termination of (maxp.exe) Maximus. You can enter a sequence of kills through the start-ups if desired, using 'go' or any other kill program. For example enter: Entry Title: Elephant Program path & file name: go k Parameters: elephant.exe Directory: c:\homerun ( Hint: In this example use 'Run without using start' as the shell.) to kill a program whose executable is 'elephant.exe'. The Directory is the path to your 'kill' program. The 'Fullscreen (Window) Cmd.exe Shell and kill on exit' do not use the /C of START which is not too reliable. Rather the program 'kills' the shell after the program is found and killed. 4.0 Appointment/Message Daily Diary The appointment/message scheduler is quite straight forward and contains hints in the windows to assist the new user. There is a programmable appointment warning alarm to alert the user about impending appointments. The appointments can be scheduled in a variety of ways from every few minutes to yearly and beyond. 5.0 Calendar There is a built in 50+ year calendar and access to this feature has been conveniently located in the Calendar menu. 6.0 Disclaimer The author makes no representations about the accuracy or suitability of this material for any purpose. It is provided "as is", without any express or implied warranties. The author will assume no liability for damages either from the direct use of this product or as a consequence of the use of this product. 7.0 Bugs and Suggestions Should an unexpected dump occur, check the Homerun.err file for an explanation. Please report any bugs (or suggestions) and I will take action on them if possible and practical.