Lion Share

home *** CD-ROM | disk | FTP | other *** search

/ Lion Share / lionsharecd.iso / utils_mz / palrun.zip / PALRUN.DOC < prev next >

Wrap

Text File | 1989-10-04 | 78KB | 1,933 lines

PALRUN version 1.0 Registration Form ----------------------------------------------------------------- Make checks payable to: PAL Software NY, Inc. 51 Cedar Lane Ossining, NY 10562 ----------------------------------------------------------------- Qty ________ PALRUN 1.0 @$20 $____________ NY residents add appropriate sales tax: $____________ Total: $____________ Upon registration you will be provided with your exclusive password for PALRUN. Please see the chapter in the documentation entitled "License" for information regarding your right to try out PALRUN. PALRUN Documentation, Version 1.0 Copyright (c) 1989 All Rights Reserved PAL Software NY, Inc. 51 Cedar Lane Ossining, NY 10562 BBS: (914) 762-8055 _______ ____|__ | (tm) --| | |------------------- | ____|__ | Association of | | |_| Shareware |__| o | Professionals -----| | |--------------------- |___|___| MEMBER PALRUN is a trademark of PAL Software NY, Inc. Table of Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . 5 How to Run PALRUN . . . . . . . . . . . . . . . . . . . . . . 6 USAGE . . . . . . . . . . . . . . . . . . . . . . . . . 6 ALTERNATIVE 1 - EXECUTE AND RETURN TO DOS . . . . . . . 7 ALTERNATIVE 2 - THE PALRUN PROMPT . . . . . . . . . . . 7 NESTED BATCH FILES WITH PALRUN . . . . . . . . . . . . . 7 INPUT/OUTPUT REDIRECTION ON A COMMANDLINE . . . . . . . 7 MULTIPLE COMMANDS ON A COMMANDLINE . . . . . . . . . . . 9 WHAT PALRUN DOES . . . . . . . . . . . . . . . . . . . . 10 Running PALRUN From Its Own Prompt . . . . . . . . . . . . . 11 Changing PALRUN's Assumptions With the Setup Procedure . . . 13 PALHOUSE DEFAULTS . . . . . . . . . . . . . . . . . . . 14 PKUNZIP(tm) DEFAULTS . . . . . . . . . . . . . . . . . . 15 MISCELLANEOUS . . . . . . . . . . . . . . . . . . . . . 15 BATCH FILES TO SUBSTITUE FOR PKUNZIP . . . . . . . . . . 16 SAVING YOUR CHANGES . . . . . . . . . . . . . . . . . . 17 Programs to Keep Out of PALHOUSE.ZIP . . . . . . . . . . . . 18 PALRUN Tips, Tricks and Traps . . . . . . . . . . . . . . . . 20 Registration Benefits . . . . . . . . . . . . . . . . . . . . 28 Association of Shareware Professionals Ombudsman Procedure . 29 License . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 APPENDIX A . . . . . . . . . . . . . . . . . . . . . . . . . 32 2 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ************ Introduction ************ Early in the history of personal computing, it became apparent that convenience dictated the need for some form of storing related files together. In the CP/M days, "libraries" became common, files with the extension ".LBR" which contained other files within them which could be easily extracted at will. At about the same time, tools became available to "squeeze" a file to take up less space. Ultimately, personal computer users began to squeeze files and then place them into libraries. One popular program, LUE, appeared for the purpose of simultaneously extracting a squeezed program from a library and expanding it to its original form. Under CP/M, no program was available to do the squeezing and archiving at the same time. With the switch to MS-DOS, it was only a matter of time before someone came up with a program to provide archiving, compressing and extracting routines in one convenient package. That package was ARC(tm), from Systems Enhancement Associates. It didn't take long for ARC(tm) to become a standard. Where someone spots gold, others will follow, and ARC(tm) began to receive competition from PKware's PKARC program. As the result of a lawsuit between System Enhancement Associates and PKWare, the latter abandoned PKARC in January, 1989, and developed PKZIP(tm), a similar but incompatible system for compressing and archiving files. At about the time that PKWare made its move, other competing compression/archiving schemes appeared, most notably PAK from Nogate Consulting and LHARC from Haruyasu Yoshizaki in Japan. The author of PALRUN, watching the unfolding of this competitive drama as if watching a soap opera, started doing comparative tests of all the available compression programs, with whatever objectivity he could muster. These tests, together with narrative comments, can be found in a series of reviews that have been released over time. You can find them on the PAL BBS and on many other BBS's. At this writing, the most recently available edition is known as COMP8.COM, a self-extracting LHARC file, or you may be able to find it as COMP8.ZIP, in PKZIP(tm) format. Having spent several months closely observing the developments among the compression competition, it became apparent that these programs were generally not being used to their full potential. Generally, the archiving programs are used to store programs and files which are seldom used. This provides a great method for organizing files and for saving space on a hard disk. However, an examination of the nature of files 3 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ sprinkled on most hard disks will probably show a preponderance of EXE and COM files and their associated data and support files. With the recent advances in archiving/compression technology, it seems like such a waste to have all of these files strewn about, taking up all that disk space. Enter PALRUN. PALRUN is designed to permit you to conveniently and transparently extract a program or batch file from an archive, run it, and then delete the file that's been run. By intelligently constructing batch files, you can have all support files housed in archives until you need them. Once you start using PALRUN, you may become astounded by the amount of space you save on your hard disk. But you may be further amazed by PALRUN, since it goes way beyond merely helping you save disk space! For instance: * If you run PALRUN from its own prompt, you will be provided with an easy method to edit and/or repeat your prior commands. * PALRUN will allow you to nest calls to batch files, even if your DOS version is earlier than DOS 3.3. * PALRUN gives you the ability to issue several commands at a time on the command line, thus allowing you to construct "batch" files on the fly. PALRUN relies on PKZIP(tm) and PKUNZIP(tm), products of PKWare, Inc. You will need PKZIP(tm) to compress your files. PALRUN itself calls on PKUNZIP(tm) to do the extraction. The reason that we chose the PKWare products rather than some other archiver is that (1) they seem to be very popular and (2) their performance specifications are appropriate for this application. The degree of compression is quite good and the extraction speed (which you will be most concerned with in using PALRUN) is excellent. PAL Software NY, Inc. has no affiliation with PKWare, Inc. If there is demand for it, we may extend future versions of PALRUN to permit it to work with other archiving products. For a quick start with PALRUN, see the next chapter. 4 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ *********** Quick Start *********** To get a quick look at how PALRUN works, observe the following steps: 1. Place PALRUN.EXE in any subdirectory within your DOS path. 2. Make sure that you have PKZIP.EXE and PKUNZIP.EXE in a subdirectory in your DOS path. These programs are shareware offerings of PKware, Inc. 3. Take the sample file named PALHOUSE.ZIP, which is included with the distribution files of PALRUN, and place it into any subdirectory within your DOS path. 4. You're now ready to check out how PALRUN works. Issue the following command: PALRUN MAPMEM Watch PALRUN find the program MAPMEM, extract it and then execute it. Once execution is completed, the program file of MAPMEM.EXE will be deleted from your hard disk. MAPMEM is a product of TurboPower Software. We gratefully acknowledge their permission to use MAPMEM as an example for PALHOUSE.ZIP. You will see in MAPMEM's report that PALRUN takes only about 3K of memory. The rest of PALRUN's code is swapped to EMS if you have any available, otherwise to your disk. By the way, the software technology for this method of using so little RAM was contributed by TurboPower Software. Also included in the sample PALHOUSE.ZIP is a batch file called PALVIEW.BAT. This is set up to use PKZIP(tm) to report on what files you actually have in PALHOUSE.ZIP; make sure that you modify the drive and subdirectory setting for PALHOUSE.ZIP within that batch file to match the location of your own PALHOUSE.ZIP. For more details on PALVIEW.BAT, see the last question in the question and answer section of this documentation. 5 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ***************** How to Run PALRUN ***************** PALRUN can find and execute any program or batch file in your DOS path or in PALHOUSE.ZIP. ----- USAGE ----- The syntax of PALRUN is: PALRUN Commandline -or- PALRUN /P [Commandline] where "Commandline" is the normal set of commands that you would ordinarily type on the Dos command line. For instance, if you wanted to issue the command "LIST PALRUN.DOC", you can now issue the command "PALRUN LIST PALRUN.DOC". PALRUN will execute the entire Commandline for you, looking in PALHOUSE.ZIP first for the name of program that you have chosen to invoke. If PALRUN cannot find the program in PALHOUSE.ZIP, it will look in your DOS path. PALHOUSE.ZIP is a file which must be produced with PKZIP(tm). PALHOUSE.ZIP should reside in a subdirectory in your DOS path. You may place it someplace else if you make the appropriate changes using PALRUN's setup procedure. To enlarge the sample PALHOUSE.ZIP which is included with PALRUN or to create your own, choose the program or batch file that you want to include (any COM, EXE or BAT file) and use the following syntax: PKZIP -a PALHOUSE.ZIP NameOfProgramToAdd where "NameOfProgramToAdd" is, you guessed it, the name of the program or batch file you want to add. See the PKZIP(tm) documentation for complete instructions. You will probably want to delete the program or batch file after it's added to PALHOUSE.ZIP. You can do this manually, or you can have PKZIP(tm) do it by specifying "-m" above instead of "-a". PKZIP(tm) is a product of PKWare, Inc. and is not included with PALRUN. At this writing, the most recent version of 6 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ PKZIP(tm) is available under the name PKZ102.EXE. You should be able to download it from the PAL Software BBS. ----------------------------------------- ALTERNATIVE 1 - EXECUTE AND RETURN TO DOS ----------------------------------------- The first alternative above will run the command and then exit back to DOS. --------------------------------- ALTERNATIVE 2 - THE PALRUN PROMPT --------------------------------- The second alternative replaces the DOS system prompt with PALRUN's own prompt. You may optionally specify a "Commandline" after the "/P", in which case PALRUN will immediately execute that Commandline before showing you its own prompt. For more details on using this option, see the next chapter in this documentation, entitled "Running PALRUN From Its Own Prompt". ------------------------------ NESTED BATCH FILES WITH PALRUN ------------------------------ Please note the very special feature that if the "PALRUN Commandline" was issued from within a batch file, then when PALRUN finishes its job it will return control back to the next line of that batch file. This is what gives you the ability to make nested calls to batch files even if your DOS version is earlier than DOS 3.3. To ensure that you do return to the batch file, make sure that you invoke PALRUN without the "/P" switch. Using the "/P" switch will leave you at PALRUN's prompt when the processing is completed, and you would have to type QUIT to get out of PALRUN. ----------------------------------------- INPUT/OUTPUT REDIRECTION ON A COMMANDLINE ----------------------------------------- When using I/O redirection (the >, >>, < and | commands that DOS provides) on a Commandline executed from PALRUN's prompt, everything will work hunky-dory. However, if you use redirection when invoking PALRUN from the DOS prompt, you'll have to do some special things. Here's the problem. Suppose you want to do something simple 7 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ like type a file and send the output to your printer. Your favorite "typing" program is not DOS's TYPE command, but something called XTYPE (That's just a fictitious name, folks. Don't go looking for it). The normal command that you would run would be "XTYPE FILENAME > PRN". If you wanted to invoke this by calling PALRUN from the DOS prompt, you would think that all you have to do is execute "PALRUN XTYPE FILENAME > PRN". This will NOT give you the result you might be expecting, because DOS sees the redirection character (the ">") and stops passing that information to PALRUN. In effect, DOS thinks that what you want to do is redirect the output of PALRUN, when what you really wanted to do is redirect the output of XTYPE. To bypass DOS's stubborn insistence on stripping out all redirection from the Commandline, we have to fool DOS. To do that, you'll have to use certain substitute characters that PALRUN can detect so that DOS will pass the entire Commandline to PALRUN. PALRUN will look at your Commandline, and if it detects the substitute characters, then it will interpret them as the proper DOS redirection characters. These are the substitutions that you need to use to fool DOS: If You Want to Use: Then Substitute: > ) >> )) < ( | ! PALRUN will recognize the foregoing substitutions if and only if there is a space preceding and a space following the substitution. It will not recognize the substitution if any character other than a space precedes or follows the substitution. The purpose of this is to make sure that if you need to use any of the substitute characters for any other reason, such as within some command you are giving, PALRUN will not misinterpret it. To illustrate the foregoing: PALRUN XTYPE FILENAME ) PRN -- PALRUN will execute: XTYPE FILENAME > PRN and then return to the DOS prompt PALRUN XTYPE FILENAME )PRN -- PALRUN will not replace the ) with > This is because the ) is not followed by a space 8 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ PALRUN /P DIR *.* ! SORT ! MORE -- PALRUN will execute: DIR *.* | SORT | MORE and then return to the PALRUN prompt The only time you need to worry about these substitution characters is if you want to perform any redirection operation while calling PALRUN from the DOS prompt. This is the case whether or not you are using PALRUN's "/P" switch. If you are at PALRUN's own prompt, you don't have to worry about these substitutions. However, for the sake of transparency, if you happen to use any of the substitute characters at the PALRUN prompt, PALRUN will detect them and make the substitutions. ---------------------------------- MULTIPLE COMMANDS ON A COMMANDLINE ---------------------------------- One additional special feature is that you may construct your Commandline to contain a series of commands by separating each individual command with the caret character: the ^ above the 6. You can have as many as 30 commands on a single Commandline. For instance: "PALRUN /p edwin c:autoexec.bat^wp run.doc^chkdsk c:" will tell PALRUN to execute three successive commands and then remain at the PALRUN prompt. When you construct a multiple command Commandline from the DOS prompt, remember that DOS will accept only 128 characters, including the "PALRUN" command with which you start your typing. This will provide a practical limit to the number of commands that you can execute. PALRUN extends DOS's 128 character buffer to 254 characters if you issue your multiple commands from the PALRUN prompt. Since DOS accepts only 128 characters and PALRUN has a 254 character space for editing, it is conceivable that you could run into a situation where you are trying to construct from the PALRUN prompt a single command whose length exceeds 128 characters. If you do so, your command will be truncated beyond the 128th character. 9 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ---------------- WHAT PALRUN DOES ---------------- When PALRUN executes a Commandline, with either of the two alternatives, it goes through the following sequence of tests: 1. First, PALRUN determines whether the program being invoked is an internal DOS command. If so, PALRUN loads a new copy of the DOS command processor and runs the Commandline. 2. Second, if the program or batch file is not an internal DOS command, PALRUN will look in PALHOUSE.ZIP (which must reside in your DOS path), extract the file and then shell to DOS and run the Commandline. After running a program or batch file that was extracted from PALHOUSE.ZIP, PALRUN will delete the COM, EXE or BAT file that it extracted. 3. Third, if the program or batch file is not an internal DOS command and cannot be found in PALHOUSE.ZIP, and if PALRUN finds it in your DOS path, PALRUN will shell to DOS and run the entire Commandline. It is not necessary for you to specify the extension (COM, EXE or BAT) with the first parameter of the Commandline. PALRUN will first look in PALHOUSE.ZIP for a batch file of that name, then a COM file, then an EXE file. If it finds none of the foregoing, it looks in your path in the same sequence. Even though it's not necessary to specify the extension, you may certainly do so. If you do specify the extension of the program or batch file, then PALRUN will not bother checking for files with a different extension, and you may save a fraction of a second of time. 10 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ********************************** Running PALRUN From Its Own Prompt ********************************** You can avoid having to type "PALRUN" every time you want to execute a command by running PALRUN from its own prompt. To obtain the PALRUN prompt, all you need to do is invoke the program as follows: PALRUN /P [Commandline] The "[Commandline]" in the above expression means you may optionally specify a Commandline to execute immediately. After PALRUN loads, you will see something like the following: PALRUN | C:\COMM\DOWN | Type QUIT to leave PALRUN > [Note: If your printer does not show IBM graphics characters, what shows following the ">" above is supposed to be a shaded line.] The above picture assumes that you have not specified an optional Commandline when you invoked PALRUN. The cursor will be located right after the ">" character. Type in any regular Commandline (remember, don't type in "PALRUN" at the beginning of the Commandline), hit the carriage return, and let 'er rip. If you specified an optional Commandline when you invoked PALRUN, then as soon as that Commandline is executed the PALRUN prompt will appear. You will see that the prompt will not be a blank, shaded area but instead will contain your original Commandline. Please note that even though the shaded area in which you will be entering your Commandline appears only to have room for 79 characters, it will accept 254 characters. This will give you plenty of room to construct a multiple command Commandline, as described above under the heading "MULTIPLE COMMANDS ON A Commandline". Each time that PALRUN executes the Commandline, it will return to the PALRUN prompt. Notice what happens: the Commandline that was just executed appears once again. At this point, you have several options: 11 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ 1. Execute the same Commandline: If you want to execute the same command, just hit the return key. 2. Execute a different Commandline: If you want to execute a different command, just start typing it; the old command will disappear once you hit any normal character on your keyboard. 3. Edit the Commandline: If you want to edit the command that shows following the prompt, you may do so. To add something to the Commandline, hit the space key first, then continue typing. To change something in the Commandline, you can move the cursor with the cursor keys or with other key combinations that ought to make either Wordstar or WordPerfect users very comfortable (See Appendix A for a table of editing commands). You can change something just by typing over it, or if you want to insert something you can strike the INS key to change to insert mode (the cursor will change to a large block cursor to let you know that you are inserting rather than typing over); strike the INS key once again to toggle back to overwrite mode. For instance, let's say that you run the following command from the DOS prompt: PALRUN /p chkdsk f: After running CHKDSK on drive F:, you'll be returned to PALRUN's prompt, which will show "chkdsk f:" as your previous command. If you now want to run CHKDSK on drive C:, just hit the left arrow key twice, hit "C", then the return key, and you're in business! As you will note from the PALRUN prompt you see on your screen, in order to exit PALRUN all you have to do is type in "quit" and then hit the return key. 12 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ****************************************************** Changing PALRUN's Assumptions With the Setup Procedure ****************************************************** You may change many of PALRUN's assumptions as to how to do its work. These assumptions can be loosely grouped in three categories: 1. PALHOUSE defaults 2. PKUNZIP(tm) defaults 3. Miscellaneous To make changes you have to call up PALRUN's setup procedure. This is done by invoking PALRUN in the following manner: PALRUN /S Alternatively, for your convenience, you may summon the setup procedure directly from the PALRUN prompt by issuing "/S" as your command. As soon as you call up the setup procedure you will be presented with the following screen: ****************************************** These are your current defaults in PALRUN: ****************************************** PALHOUSE defaults----------------- A. Name of "PALHOUSE" :PALHOUSE B. Search path before "PALHOUSE" :NO C. Path for "PALHOUSE" : Anywhere in the DOS path PKUNZIP defaults------------------ PKUNZIP [optional switches] [output path] PALHOUSE extractfile [redirect] D. Optional switches :-o E. Output path for extraction : Current Subdirectory F. Redirection :> nul Miscellaneous---------------------- G. Command Separator :^ H. Output Substitute > :) I. Input Substitute < :( J. Pipe Substitute | :! K. Quiet Mode :ON L. PKUNZIP substitute name : 13 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ You will be prompted to select items A through L to make a change. When you are finished making changes, then you can save those changes by hitting the "S" key on your keyboard. If you want to exit without saving the changes, then hit the "X" key. If you ever want to restore the original distribution defaults, as set forth in the above picture of the setup screen, then invoke the following: PALRUN /R You may also summon this restore procedure directly from the PALRUN prompt by issuing "/R" as your command. ----------------- PALHOUSE DEFAULTS ----------------- The distribution version of PALRUN contains the following defaults with regard to PALHOUSE: A. Name of "PALHOUSE" :PALHOUSE B. Search path before "PALHOUSE" :NO C. Path for "PALHOUSE" : Anywhere in the DOS path Item A indicates the name of the file (without the .ZIP extension) that will house all the programs and batch files that PALRUN will look for. Item B indicates whether PALRUN will search the DOS path before looking in PALHOUSE.ZIP. Item C specifies a path in which you know that PALHOUSE.ZIP will be residing. This permits you to designate a specific location so that PALRUN does not need to hunt through the DOS path for PALHOUSE.ZIP. You should specify the full drive and subdirectory of your choice, but do not include the actual filename in your specification. 14 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ -------------------- PKUNZIP(tm) DEFAULTS -------------------- When PALRUN invokes PKUNZIP(tm) to extract a specified program or batch file from PALHOUSE.ZIP, it uses the following command. PKUNZIP [optional switches] [output path] PALHOUSE extractfile [redirect] Item D Item E Item F The items in brackets may be changed by you to your liking if you so desire. The distribution version of PALRUN contains the following defaults with regard to PKUNZIP(tm): D. Optional switches :-o E. Output path for extraction : Current Subdirectory F. Redirection :> nul Item D specifies the switches that PKUNZIP obeys. Ordinarily, you want to use the -o switch to make sure that whatever is extracted will automatically overwrite any existing file of the same name. If you change item D, make sure you include the -o switch, or else you may wind up with PALRUN pausing and asking your permission to overwrite a file before it proceeds. You may desire to specify additional switches. This permits you, for instance, to specify a password when extracting from an encrypted ZIP file. Item E indicates to what location the program or batch file will be extracted. You may find that performance improves substantially if you specify a ramdisk for this operation. Item F permits you to add characters following the basic PKUNZIP(tm) command. This would most often be used for redirection of some of PKUNZIP's reports. The distribution version of PALRUN redirects PKUNZIP's reports to the "NUL" device, which means that you don't get to see what PKUNZIP ordinarily writes to the screen. ------------- MISCELLANEOUS ------------- This category of changes deals with special characters used 15 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ by PALRUN and a couple of other miscellaneous defaults. On distribution, the miscellaneous values are as follows: G. Command Separator :^ H. Output Substitute > :) I. Input Substitute < :( J. Pipe Substitute | :! K. Quiet Mode :ON L. PKUNZIP substitute name : Item G specifies the character that separates multiple commands on the Commandline. Items H through J specify the substitution characters that permit redirection commands to be passed to the command line of the program that PALRUN is invoking. It is unlikely that you need to change any of the distribution values for the special characters unless they conflict with your normal computer usage. Item K permits you to silence many of the comments that PALRUN provides to you as it goes about its tasks. Persons who have not registered PALRUN may toggle quiet mode from off to on and back again, but quiet mode will not be recognized by PALRUN except for registered users. Item L could be handy if you have changed the name of PKUNZIP.EXE on your system. For instance, you may have changed it to UNZ.EXE for speed of typing. If this is the case, then PALRUN will recognize the UNZ.EXE if you make the change in this place of the setup procedure. PALRUN will accept the name of any COM, EXE or BAT file that you designate, so long as it can find the file on your DOS path. ------------------------------------ BATCH FILES TO SUBSTITUE FOR PKUNZIP ------------------------------------ Why might you want to specify a BAT extension for item L? You might want to have PALRUN use a special batch file of your own making. We leave that to your own ingenuity. Just remember the order of parameters that PALRUN will pass to your batch file. PKUNZIP [optional switches] [output path] PALHOUSE extractfile [redirect] Item: L D E C+A+.ZIP F "Extractfile" is the full name of the program or batch file (including extension) that PALRUN has found within PALHOUSE.ZIP. If PALRUN does not find such a file in PALHOUSE.ZIP, then PALRUN 16 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ will refuse to try the PKUNZIP(tm) process and will therefore never invoke your batch file. After the program or batch file is extracted with your custom batch file and then executed by PALRUN, please remember that PALRUN will be expecting to find and delete "Extractfile". If an output path (Item E) is specified by you, then PALRUN will look in that output path, otherwise PALRUN will look in the subdirectory which was current at the time that your extraction process commenced. You may find that your custom batch file is more bulletproof if you do specify your own output path in Item E. One might think that it could be possible to make a custom batch file in order to make use of ARC(tm), LHARC, PAK or some other competitor of PKUNZIP(tm). This is not presently the case, since PALRUN automatically assumes a ".ZIP" extension for PALHOUSE and will not continue processing your command if it finds something other than a .ZIP kind of archive. If demand warrants, future versions of PALRUN may implement features for these other archiving programs. ------------------- SAVING YOUR CHANGES ------------------- Once you have completed making all your desired changes, you can either save your changes by striking the "S" key. If you want to leave PALRUN.EXE unchanged, you can discard the changes by exiting with the "X" key. If you have chosen to save your changes, then you will be asked whether you want to create a new EXE file with a different name. If you just want to modify the PALRUN.EXE that you originally invoked, then hit either the "N" key or the return key. If you do want to create a new EXE file, answer "Y", and you will be prompted for the new name. This ability of creating a file with a new name could be useful where a single computer is used by several users who each need their own unique version of PALRUN. If you invoked the setup or restore procedures directly from PALRUN's own prompt, your changes will be immediately made for you in that computing session. For instance, if from the PALRUN prompt you changed the output path to designate a ramdisk rather than the current subdirectory, then with the very next command you issue, PKUNZIP(tm) will be instructed to extract to that ramdisk. 17 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ************************************ Programs to Keep Out of PALHOUSE.ZIP ************************************ Once you get the hang of using PALRUN, you may be tempted to throw every single EXE, COM and BAT file into PALHOUSE.ZIP. Don't. Some files are simply inappropriate for inclusion in PALHOUSE.ZIP. Here's a listing of what we think you ought to keep outside: 1. Files that you will need available just to run PALRUN: PALRUN.EXE PKUNZIP.EXE 2. Programs that install themselves as resident programs, for instance: SK.COM SideKick PALARM.EXE Resident alarm handler for PAL Do not load a resident program from PALRUN. Your system may lock up. 3. Programs which are called by other programs. We'll refer to this type of program as a "helper program". Just as PALRUN relies on PKUNZIP(tm) as a helper program, some of your programs may rely on a supplemental program. For instance, on our BBS, one of the door programs relies on BRUN30.EXE to operate; if BRUN30.EXE was stuck within PALHOUSE.ZIP, then the door program would never know how to find it. Notwithstanding our categorization of helper programs as being inappropriate for being placed in PALHOUSE.ZIP, that doesn't mean that you have to leave them uncompressed on your hard disk. One way of keeping such a program within a ZIP file is to construct a batch file to be housed in PALHOUSE.ZIP. Let's say that you've stored both your main program and your helper program in YOUR.ZIP; the batch file will first change to the drive and directory of your choice, issue the PKUNZIP(tm) command to extract all pertinent files from YOUR.ZIP, run the main program, then tidy up by deleting all the files that were 18 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ extracted from YOUR.ZIP. The last step in this sequence is very neatly handled by the command "PKZIP -mf YOUR". For an example of this kind of a batch file, see the sample batch file PALWP.BAT, which is included with this distribution. 4. Programs which you use all the time. For instance, notwithstanding our use of WordPerfect as an example in our sample batch file PALWP.BAT, you may be a heavy WordPerfect user, going in and out of WordPerfect several times a day. Each time you invoke PALWP.BAT with PALRUN, you will suffer impatiently as all the support files get extracted. The time penalty may not be worth the disk savings. Only you can balance that decision. 5. Programs whose setup routines modify the programs themselves. Examples of this type of self-modifying programs include Vern Buerg's LIST, and PAL Software's PAL, both of which permit you to clone new versions of the program to include changes that you have made to start-up defaults and information. Since the very last thing that PALRUN does after executing such a program is to delete that program from your disk, any changes which have been made to that program will be lost. This may not be a major problem with LIST, since you may not change it often, but for a program like PAL, which you may modify daily to change the appointments records contained internally, this could be a real hassle. One way of getting around this problem with self-modifying programs is simply not to store them within PALHOUSE.ZIP. Instead, store them in a separate ZIP and summon the program from a batch file that IS stored in PALHOUSE.ZIP. Then when you have finished executing the program, use the magical "-mf" switch with PKZIP(tm) to get any changed version back into your separate ZIP file. See the included sample batch file PALWP.BAT for an example. 19 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ***************************** PALRUN Tips, Tricks and Traps ***************************** Q: What is PALHOUSE.ZIP? A: PALHOUSE.ZIP is the name of the ZIP file created with PKZIP(tm) which you will use to house the compressed programs or batch files that you want to execute with PALRUN. Q: My system is locking up when I try to install a resident program with PALRUN. What's happening? A: Please do not try to load a resident program with PALRUN. It is not possible to do so without confusing the system, since the chain of interrupts will be messed up when PALRUN exits. Q: Why does PALRUN also execute programs and batch files that it can find on the DOS path? Why not just restrict it to what it can find in PALHOUSE.ZIP? A: Once you start using PALRUN, you may forget what you've stored in PALHOUSE and what you've decided to leave in outside of PALHOUSE. If you had to stop to think where a program is whenever you want to execute it, you might soon stop using PALRUN. This way, you can start every command line with PALRUN, and your command will be faultlessly executed no matter where you have stored your program or batch file. PALRUN will also execute internal DOS commands like COPY or DELETE. The ability to run internal DOS commands and programs found on your path is also critical to being able to run PALRUN from its own prompt. Q: That's an awful lot of extra keystrokes to use to execute PALRUN every time I want to do something! A: There are two simple and effective responses to that. First, you can run PALRUN from its own prompt. Just invoke 20 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ it with the following sequence: "PALRUN /P" Then PALRUN will load and give you its own prompt. You can then initiate any series of commands that you like without having to type in "PALRUN" at the start of the command. To exit back to the DOS prompt, type "QUIT" and hit the return key. The second method you can use is to simply rename PALRUN.EXE to some shorter name, such as P.EXE. Then the number of extra keystrokes is minimized. Q: Are there any programs that I should NEVER execute with PALRUN? A: Yes. Never, never execute a program that becomes resident, ..such as SideKick or Desqview. Your computer system will probably become hopelessly confused and lock up. The implication of this for those who want to use PALRUN from its own prompt is that you have to load all your resident programs prior to using PALRUN. For instance, you may have an AUTOEXEC.BAT file which loads a series of resident programs when you boot up. Make sure that all resident programs are available outside of PALHOUSE.ZIP and can be loaded without resort to PALRUN. Furthermore, you may desire to have the last command in your AUTOEXEC.BAT file a "PALRUN /P" command. Make sure that all resident programs are already loaded before going to the PALRUN prompt; otherwise, you'll just have to quit PALRUN, load the resident program, then reload PALRUN. Q: How much memory does PALRUN use? A: When executing a COM or EXE file, PALRUN uses only about 3K of memory. It shrinks itself by swapping most of itself to disk (or to EMS memory if available), leaving in memory only what it needs to restore itself and clean up after the command has been executed. We gratefully acknowledge TurboPower Software for contributing the software technology that makes this super- efficient use of memory possible. When executing a batch file or an internal DOS command, PALRUN must first load a portion of COMMAND.COM. So in these cases the memory usage will be the 3K used by PALRUN plus a few kilobytes that COMMAND.COM needs to load to process the command. 21 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ Q: How much space can I expect to save by using PALRUN? A: That's not an easy question to answer. It depends on how you use it. Let's take batch files for example. Assume you have about 20 batch files, averaging about 200 bytes each for a total of about 4000 bytes. If you move them all into PALHOUSE.ZIP, their aggregate compressed size won't be much different from 4000 bytes. But if you were to run CHKDSK before and after the move, you would find that you save several thousand bytes. This is because each individual file residing on your disk takes up space based on clusters, which are usually measured in thousands of bytes. Thus, your 200 byte batch file may actually be absorbing 2048 bytes of disk space. You will be recovering quite a lot of this slack space by using PALHOUSE.ZIP. As a drastic example of the way that small files eat up disk space, we have a separate directory on our hard disk for testing the compression results for PKZIP(tm), ARC(tm), LHARC and so forth on a lot of small files. Norton's FS program, which checks on free space, reports the following: 7,232 total bytes in 65 files 532,480 bytes disk space occupied, 98% slack If we move all of those small files into a single ZIP, the size of that ZIP is only 11,051 bytes. While that's more than the apparent size of 7,232 bytes of the total bytes of the files, that's an actual disk savings of 521,429 bytes! The 8K cluster size on our hard disk can produce some pretty great inefficiencies; even if your cluster size is only 2K, you'll still see a savings of about 122K. With larger COM and EXE files, your space recovery is likely to be between 30% to 50% of their size. If you start playing around with batch files like the sample PALWP.BAT in order to start ZIPping up your support files, you'll gain even more space. Your experience will vary markedly from application to application. One of our beta testers reported that Flight Simulator didn't decrease all that much, but that a financial application reduced itself to about 1/3 of its original size. Q: Thanks for the great idea about using a batch file to 22 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ extract what I want from a ZIP with the "-o" switch and then, when done with the operation, simultaneously freshening up the ZIP and deleting the files with the combined "-mf" switch. Now, tell me honestly, what can PALRUN do for me that I can't do just by constructing such batch files? A: Well, first of all, each batch file you construct will take up a full cluster on your hard disk, regardless of the actual number of bytes you really need. Secondly, you probably have a lot of EXE and COM files that you will want to execute from time to time, but for which it makes no sense to construct a batch file. For instance, with Vern Buerg's popular LIST program, are you going to stick that into a ZIP file and write a separate batch program to extract and run it? With PALRUN, you can throw ALL of your EXE and COM programs into PALHOUSE.ZIP, and PALRUN will extract and run any one of them without the need to write an additional batch file. Third, PALRUN gives you the ability to call a batch file from within a batch file, something that users of DOS versions earlier than version 3.3 have not been able to do. Fourth, if you run PALRUN from its own prompt, you will have a very flexible method of editing the commands that you wish to give. Fifth, PALRUN allows you to construct a Commandline with multiple commands, the equivalent of putting together a batch file on the fly. Q: Do you have any suggestions on how to organize my use of PALRUN? A: Sure. We recommend that simple EXE and COM programs that don't require any support files (e.g., CHKDSK, FORMAT, LIST) be placed directly into PALHOUSE. More complex programs which require support files (e.g., SuperCalc, WordPerfect, Procomm Plus) can be set up in separate ZIP files which can be extracted by means of a batch file (in PALHOUSE) which you summon with PALRUN. For an example of how this can be done, see the sample batch file PALWP.BAT. If you examine PALWP.BAT, you will see that the batch file deals with two separate ZIP files -- WPSPRT.ZIP for all WordPerfect program and support files, and WPEDIT.ZIP for all documents being edited. When you're not running WordPerfect, all 23 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ these files remain comfortably ensconced, in compressed form, within their respective ZIP files. When you're ready to run WordPerfect, a simple "PALRUN PALWP NameOfFileToEdit" will allow everything to jump into readiness for your editing pleasure. Q: Can I use PALRUN on a line of my batch file to call another batch file? A: In constructing your batch files, there is no constraint against using PALRUN as a command. Thus, you can accomplish quite a bit of gymnastics in this fashion. For instance, from within any batch file you can call PALRUN to invoke another batch file. Users of versions of DOS earlier than 3.3 (which has a CALL command to permit nested batch calls) may find this facility to be of extra special value. Just remember, in setting up those batch files, that every time PALRUN calls a batch file it has to load a portion of COMMAND.COM to do the processing, so if you set up heavily nested batch file calls you could be eating up a lot of RAM. Q: Why do I get a notice from PALRUN that it cannot do a SET or PATH command? A: First of all, you'll only get this notice if you're calling these DOS commands from a PALRUN Commandline that is not going to leave you back at the PALRUN prompt but back at the DOS prompt. The reason for this is that when PALRUN exits back to the DOS prompt, all changes which you may have tried to make to the environment will be lost. If you make changes to the environment and are returning to the PALRUN prompt, PALRUN knows how to retain those changes, but once you finally quit back to DOS, those environment changes will be lost. The moral of the story is: If you want environment changes to be retained after PALRUN quits, then make sure you make those changes from the DOS prompt before running PALRUN. Q: I tried running a command from PALRUN that uses DOS redirection to send output to my printer, but it didn't work. What's going on? A: Read the section of this documentation entitled "INPUT/OUTPUT REDIRECTION ON A COMMANDLINE". 24 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ Q: Suppose I have several users on a single machine, each of whom would prefer to have his or her own PALHOUSE.ZIP, which should be secure from tampering by other users. A: Each of your users can create his or her own version of PALRUN.EXE through the setup procedure. Each user can specify the name and location of that user's ZIP file. The setup procedure can also be used to indicate additional switches for the PKUNZIP(tm) command, which could include, for instance, the password that PKUNZIP(tm) needs to see from that user to extract from an encrypted ZIP file. Lastly, when exiting the setup procedure, the user will be given the opportunity to create a new EXE file with the defaults that have just been chosen; you could wind up with a SUSAN.EXE, a ROBERT.EXE and a JIMMY.EXE, all of which are merely new copies of PALRUN.EXE but with unique personal defaults selected. Q: What can I do to enhance the speed with which PALRUN works? A: The thing that you can do which will have the most discernible effect is to use a ramdisk to extract your files. The distribution version of PALRUN extracts files from PALHOUSE.ZIP into whatever is your current subdirectory at the time of the extraction. You can use the setup procedure to tell PKUNZIP(tm) to extract to whatever drive and subdirectory that you choose. If you can create a ramdisk that has enough room for the largest file you want to extract, then use the setup procedure to force PKUNZIP(tm) to extract the files there. This use of a ramdisk can be extended to any number of purposes. For instance, in the sample PALWP.BAT file, the WordPerfect support files are presumed to be in a separate ZIP file. They are extracted into the E:\WP directory. If instead of extracting onto your hard disk you extract onto a ramdisk, then the extraction process will go much faster. The one thing for which you ought to be watchful with a ramdisk is the fact that you lose everything on the ramdisk if your system locks up or you turn off the computer. Therefore, you might want to make sure that any file that you're going to edit or change in any way is edited on the hard disk and not the ramdisk. Another technique for adding some speed to PALRUN is to be aware of how PALRUN searches for a file. The distribution version of PALRUN searches first in PALHOUSE.ZIP and then in your DOS path. If you have most of your programs in your path, then 25 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ you might want to reverse that order of searching by making the appropriate change with the setup procedure. Also, if you have a very long series subdirectories strung together to make up your path, this could take longer for PALRUN to search than if you just have one or two subdirectories in your path. Q: Boy, it sure takes a long time to ZIP up all those files into PALHOUSE.ZIP. What can I do to make it go faster? A: You can do one of two things. Either (1) create a batch file to move the files into PALHOUSE.ZIP so you don't have to sit around watching, or (2) use the "-ES" option with PKZIP(tm) to get "extra speed" and less compression. We recommend choice number 1. Remember, you're only going to ZIP up these files once, but you'll be extracting them again and again and again. Your main concern here should not be speed of compression but rather the speed of extraction and the amount of space that the compressed file takes. This dictates that you stick with PKZIP's default imploding algorithm, despite the long time it may take. Q: You wouldn't believe how forgetful I can be! My PALHOUSE.ZIP is growing very large, and I don't remember what's in there. Is there some easy way for me to figure that out? A: We have included a simple batch file by the name of PALVIEW.BAT just for that purpose. We have included it right within the sample PALHOUSE.ZIP which is distributed with PALRUN. Before you try calling up PALVIEW.BAT, please note that it is written to look for E:\UTIL\PALHOUSE.ZIP. You will probably have to edit that line of the batch file in order to take into account the location of PALHOUSE.ZIP in your own system. This PALVIEW.BAT summons PKZIP(tm) to report all the files in PALHOUSE.ZIP. Invoke it as follows: PALVIEW %1 %2 where %1 and %2 are optional additional parameters. %1 is the filespec of the files that you want to look for and %2 is the extra sorting specification that you want to pass to PKZIP(tm). The "filespec" is the specification of the file that you're checking for. You may use wildcards like "*" and "?". The extra sorting specification permits you to tell 26 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ PKZIP(tm) how you want the report sorted. It is not necessary for you to specify either of the optional parameters. If you do not specify either of them, then PKZIP(tm) will give you its report in its own preferred manner. See the PKZIP(tm) documentation for details. If you want to specify the filespec without the sort specification you may do so without a problem. However, if you want to specify a sort order without a particular filespec, you must indicate *.* as your filespec. If you fail to indicate the "*.*", then the batch file will think that your sort specifications, which are then the first parameter for the batch file, comprise the name of the file you want to look for. For your sort specifications, you can specify any of the following values: b brief listing c show comments d sort by date e sort by extension n sort by name p sort by percentage s sort by size r reverse order t show technical info If the information flies by so fast that you can't see it, remember to use CTRL-S to pause the screen. You can then hit any key to resume scrolling. 27 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ********************* Registration Benefits ********************* If you use and like this product, please register. To register, send your check in the amount of $20, payable to PAL Software NY, Inc. to the following address: PAL Software NY, Inc. 51 Cedar Lane Ossining, NY 10562 If you register PALRUN, you will be entitled to the following: 1. You will be provided with an exclusive password which will tell PALRUN not to continually remind you that you need to register. 2. You will be provided with free support by mail for one (1) year following the date of registration. The level of support which we agree to provide is to answer questions and fix serious bugs. We are not required to modify the program for specific hardware or software environments or features. 3. You may access the PAL Software BBS at any time. The telephone number is (914) 762-8055. The BBS runs 24 hours a day and accepts calls at 300-9600 baud (US Robotics HST Dual modem). In addition, you can communicate with us on Compuserve; the PPN is 70475,1071. 4. You will be added to our mailing list. 5. You will be able to set quiet mode (see the description of PALRUN's setup procedure). 28 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ********************************************************** Association of Shareware Professionals Ombudsman Procedure ********************************************************** This program is produced by a member of the Association of Shareware Professionals (ASP). ASP wants to make sure that the shareware principle works for you. If you are unable to resolve a shareware-related problem with an ASP member by contacting the member directly, ASP may be able to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide technical support for members' products. Please write to the ASP Ombudsman at P.O. Box 5786, Bellevue, WA 98006 or send a Compuserve message via easyplex to ASP Ombudsman 70007,3536. 29 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ ******* License ******* PALRUN (the "Licensed Program") is the exclusive property of PAL Software NY, Inc. (the "Licensor"). Holders of the share- ware version are granted a license to try the Licensed Program for a limited period of time. If you use the Licensed Program at least once a week or over a period in excess of one month, then it is understood that you are satisfied with the Licensed Program and must register and pay for the Licensed Program. If you continue to use the Licensed Program under such circumstances without registering and paying for it, then you are in violation of this limited license. The plain English limitation here is: If you like and use the program, then register and pay for it. If, after a period of time of using the program you choose not to pay for the it, then stop using it. Persons in possession of a copy of the Licensed Program are encouraged to share it with others by uploading it to computer bulletin boards, sending copies to friends, etc. You are permitted to re-distribute the Licensed Program so long as no changes are made to the program or the documentation and the entire archived set is distributed unaltered. A reasonable charge may be received for the expense of copying and transmitting the program, but in no event must the person with whom you are sharing the Licensed Program be lead or permitted to believe that payment of such amounts constitutes registration or satisfies the requirements to register which are imposed by this license. Disk distribution services are encouraged to distribute the shareware version of the Licensed Program so long as the ser- vice's catalog or other indexing material contains a clear statement that the Licensed Program is shareware, not public domain, and that the user is expected to pay for the Licensed Program if the user likes it and intends to continue to use it. Disk distribution services are encouraged to contact the Association of Shareware Professionals for suggested language. Computer consultants and hardware sellers are permitted to distribute the Licensed Program along with their products and services so long as it is made clear to the end user that the Licensed Program is shareware and that the Licensor requires pay- ment if the end user continues to use the Licensed Program. In no event may the end user be lead or permitted to believe that the fee paid for consulting, hardware or software includes the 30 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ registration fee required for the Licensed Program. For information concerning site licenses and dealer pricing, please contact the Licensor. In no event is any person permitted to modify the Licensed Program or any of the associated documentation. THE LICENSOR DOES NOT WARRANT THAT THE LICENSED PROGRAM IS FIT FOR ANY PARTICULAR USE OR IS MERCHANTABLE. THE LICENSED PROGRAM IS NOT WARRANTED TO BE FREE OF BUGS, NOR IS IT PROVIDED WITH ANY WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. IT IS YOUR RESPONSIBILITY TO DETERMINE WHETHER THE LICENSED PROGRAM IS SUITABLE FOR YOU. IN NO EVENT SHALL THE LICENSOR, ITS OWNERS OR AGENTS BE HELD RESPONSIBLE FOR INCIDENTAL, SPECIAL OR CONSE- QUENTIAL DAMAGES, OR LOST DATA OR PROFITS TO ANY PERSON OR ENTITY THAT MAY ARISE OUT OF THE USE OF THE LICENSED PROGRAM, EVEN IF THE POSSIBILITY OF SUCH DAMAGE HAS BEEN BROUGHT TO THE ATTENTION OF THE LICENSOR. RECOVERABLE DAMAGES IN ANY EVENT SHALL BE LIMITED TO NOT MORE THAN THE PRICE PAID FOR THE LICENSED PROGRAM. 31 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ APPENDIX A LINE EDITING COMMANDS FOR THE PALRUN PROMPT When PALRUN returns to its prompt, it will always show you the previously executed Commandline. If you want to rerun that Commandline, hit enter. If you want to add to it, hit the spacebar and continue typing. If you want to enter a new Commandline, then start typing whatever you want to execute, and the previous Commandline will disappear. If you want to edit the previous Commandline, use the following key codes, which should make anyone familiar with WordStar or WordPerfect very comfortable. <Enter> Accept Line <Esc>, <CtrlBreak> Quit without changing line <Left>, <CtrlS> Cursor left one character <Right>, <CtrlD> Cursor right one character <CtrlLeft>, <CtrlA> Cursor left one word <CtrlRight>, <CtrlD> Cursor right one word <Home>, <CtrlQ><S> Cursor to beginning of line <End>, <CtrlQ><D> Cursor to end of line <Del>, <CtrlG> Delete character at cursor <Bksp>, <CtrlH> Delete character to left of cursor <CtrlEnd>, <CtrlQ><Y> Delete to end of line <CtrlY>, <CtrlX> Delete entire line <CtrlHome> Delete from beginning of line <CtrlT> Delete word to right of cursor <Ins> Toggle insert mode. Fat cursor means insert mode; thin cursor indicates overwrite mode. 32 PALRUN 1.0 Documentation Copyright 1989 PAL Software NY, Inc. _________________________________________________________________ <CtrlR>, <CtrlQ><L> Restore original contents of line 33