PowerBatch Computing Systems Design, Inc. P.O. Box 566484 Atlanta, GA 30356-6009 There are 20 files on your installation disk. The two files SMLMODEL.MDL and POWERMAK.EXE will be placed in a directory on your DOS search path. The remainder of the files may be placed in any directory you desire. The POWERBAT.DOC file is the documentation and may be viewed with any text editor or printed to your printer with the DOS print command (ie print POWERBAT.DOC ). The files with an extension of .PWR are PowerBatch source files and the text is printed in the documentation. You should compile these example files and run the resulting programs to help familiarize yourself with PowerBatch. The file DEMO1.PWR uses all the commands with a couple of exceptions. To install PowerBatch run the install program located on the source disk. If the source in on a floppy drive enter A:PBINSTAL (or B:PBINSTAL). If the source is on a hard drive, change directory to the directory containing PBINSTAL and enter PBINSTALL [More on the next page] If you have purchased a registered copy of PowerBatch, the install program will recognize this by the presence of REGISTER.EXE on your diskette. When this program is present, the copy of PowerBatch you have just installed will be registered in your name. Your name and serial number will be imbedded in the software by the registration program. If you give anyone an evaluation copy of PowerBatch, DO NOT PROVIDE THE REGISTRATION PROGRAM WITH THE EVALUATION COPY. Simply copy all of the files but REGISTER.EXE. Better still, compile the two PowerBatch source files PBCLONE.PWR and MOVESUB.PWR and use these to create a clone of PowerBatch. PBCLONE uses MOVESUB as a subroutine and is an example of the use of subroutines in PowerBatch. Anyone who uses the registration program REGISTER.EXE will imbed your name and serial number within their software. Change Record V1.0-1.3 were alpha and beta test versions not available to the public. V1.4 Added BreakOn, BreakOff, and ?EnvStr commands. Fixed bug in keyboard input routine which was incorrectly handling a single keystroke. Changed execution of DOS commands to prevent loading of another copy of command processor. Changed beep command to default to 1 repetition. V1.4a Added SetPath, Prompt, and SetEnv commands to allow changing of environment variables in the master and current environment. V1.4b Rewrote the routine which gets another output file name if the default name is not acceptable. V1.4c Fixed bug in SetVar command which was damaging the path environment variable in the current environment area. Added error messages to commands which set environment variables in both current and master environment areas if the environment area was not found or the change or addition exceeded the amount of free space available in the environment area. Fixed bug which was truncating the POWERBAT.ERR file if fatal compile errors existed. Enabled stdout redirection from within PowerBatch. ie Pgmname > nul V1.4d Added special character indicator to READKEY command. Added ADD and SUBTRACT commands. Provides a means to loop N times. V1.4e Added ability to escape from routine which prompts user for valid input source file name if none is given or an error is detected. Characters which are not on the keyboard may be defined using the decimal value of the character ie "Variable Enter,2,#17#217" Added the ability to define color changes within a stream of text. The trigger character is Ctrl-A and this is followed by the THREE digit color attribute. Ctrl-A may usually be generated in your editor by pressing Alt-1 (the 1 on the keypad). These colors may be imbedded in variables or literals. (@=Ctrl-A for the example). Variable CmdLine,75,"@112F@007ile @112T@oo7ext..." WriteAt 5,3,"@112F@007ile @112T@007ext..." Fixed bug in stdout redirection. Previously only > nul was correct.