þ GENERAL DESCRIPTION --------------------- In my experience with PCBoard, it seems that only PCBoard sysops know how to effectively read messages. Most people press 'r' then they get that little crappy prompt, hit 'h/?' for help, see how long the help file is and quit the help file. They then decide it's too much work to read messages, so they hit 'q' thinking that will quit the message read prompt, but then realize that doesn't work. Anyway! I've seen a lot of decent message read replacements, but none that do quite want I want. Whitewater Technologies' RPROMPT by far one of the better RPROMPT replacements, but it's not for the 'R' command. (I strongly urge you install RPROMPT if you already haven't -- it's free, and THE best 'End of Message command' replacement I've seen to date and it's the perfect compliment to K-READ). So then I actually found a freeware (I don't bother with shareware PPEs) 'r' replacement. But it either wasn't configurable, or was meant to be configurable but didn't work if you tried to change its looks ;). Since my board is heavily customized, I have to be able to change a PPE aesthetically if I am to use it. That one got the boot. Finally, I did find another 'r' replacement, and I did like everything about it, but it just didn't have all the commands I wanted for message reading; it seemed to leave a few important message functions out. (I'll admit: if you wanted to have EVERY possible message function, you'd have a list that'd be quite long. PCB's message system does EVERYTHING). So, for a while I was just using a PCB .MNU file (pretty much the 'k-rmnu' that's included with this package). This worked great for a while, but I have to have lightbar options ;). So thus I produced the result you see today. Give it a try right now! If pcboard?.exe is in your path (which it REALLY should be), type 'Pcboard /ppe:k-read' (minus quotes) and take it for a test drive. I think you'll be pleasantly suprized. þ DISCLAIMER ------------ This software is provided "as is." I make no warrantees or guarantees as to this PPEs operation. I, the author of this product, am not in ANY way responsible for these files. You, the user, take FULL responsibility for this product. I am NOT liable for any accidents or mishaps. YOUR computer is YOUR responsibility. This product works okay for me -- it may not for you! ALWAYS backup your system before making changes/modifications. Use at your own risk. I deny liability for the quality of this documentation as well. þ REGISTRATION -------------- With the release of v.40, I did away with the registration system. It's completely free. þ INSTALLATION -------------- Quick rundown for those who know PCBoard well: Install this PPE in your CMD.LST (probably want it to be an 'R' replacement). If you need more verbose instructions: I. File Placement/Directory Creation. A. Goto your PCBoard directory (usually \PCB) 1. If you have a directory for all your PPEs, such as \PCB\PPE, then goto that. a. Make a directory for this PPE. I recommend \K-READ 2. If you don't have a PPE directory, just make a directory for this. I suggest \K-READ. a. NOTE: Just use \K-READ as your sub-directory name. It will make things a lot easier. 3. Unzip this archive into your newly created directory. a. I assume you've already unzipped the archive, so just move all the files into the new directory. b. However you do it, make sure all the files get put in the \K-READ directory. II. CMD.LST changes A. Load up PCBSetup (you do NOT have to do this for each node) 1. Caress the 'B' key, then sack the 'B' key again. 2. Highlight "CMD.LST" and smash the enter/return key. a. Now hold down the ALT key, and while holding press the 'I' key. - oh my! you've inserted a command! b. Edit this newly Inserted command. 99% of the time, you'll want to have the command keys as 'R' (no quotes). - make sure you provide the full path to this ppe, or nothing will happen. i.e. '\pcb\ppe\K-READ\k-read.ppe' B. Pound the Escape key two or three times (God, please let them know how to use PCBSetup by now. Please. Amen.) 1. Make sure you save everything. III. Make sure it works. A. Logon to your board, either remotely or locally. 1. Type 'R' at the main prompt. If it doesn't work, do some trouble shooting. a. If you really have problems, leave me mail, and I'll be happy to help. I promise I won't take the same sarcastic tone I've taken in writing these docs (seriously, I'm a nice guy, I just don't like writing docs). IV. Customization - SEE SECTION BELOW FOR MORE INFO ON CUSTOMIZATION! A. Please do some customizing to this! It'll look crummy if you don't add some type of personal touch! B. Edit the K-READ.CFG file. 1. The K-READ.CFG is really pretty self-eplanitory. Instructions are at the bottom of the file. C. Make, buy, or whatever a background screen ('K-READ.'). 1. You CAN have language, graphic, and security specific background display files. V. Notes A. What about the 'K-RMNU.*' files? 1. I added this as an after thought, and do not know if it even works. 2. This is a PCBoard *.MNU (k-rmnu.mnu) and its accompanying display file (k-rmnu.). a. If all goes to plan, if a user who does not have ansi tries to use the PPE, he/she will be taken to this menu instead, so that he/she can still have a simplified way to read messages. b. Again, I never got around to testing this, so it may not work. However, you should use MkPcbMnu to provide a full path name to the display file for K-RMNU.MNU. þ HISTORY --------- Does anybody ever really read the history files for PPEs? Let's see, here's some quick info on it: I wrote it in about 2 hours, worked a few bugs out, then worked on it for about another hour or two to enhance and debug it. I spent tidbits of time here and there erasing bugs, and this and that with new releases. I spent about an hour on v.40. v.02 - v.024 áetas: personal testing stage v.24 áeta: first public release v.28 áeta: 'QUIT' option added to highlight selector v.31 áeta: Tab added as cursor movement key; added code to retain normal PCB 'r' options (i.e., if 'R Y A' was typed, K-Read used to load up...fixed) v.40 áeta: memory requirements lessened; lightbar routines optimized; source code reduced by about 1/3; removed registration crap þ CUSTOMIZATION --------------- With the release of .40, the customization of K-READ is now slightly more complex. Realizing this may be a problem for some people, I included some pre-made config files and background screens, hoping the sysop could find something that matches his board, and he therefore would not have to mess around with the config files. First: two files needed for LIGHTBAR customization: K-READ.(no extention) K-READ.CFG note: K-RMNU is the display file for the K-RMNU.MNU file (used when the caller does not have graphics). The customization of it should be self-explanitory). Okay, the K-READ. is the background display file. This file should include any designs, pictures, etc, PLUS *ALL* the commands available...NONE of them should be highlighted. Note the Row (y position) that the options begin on. Once you have the background designed, make sure it is no longer than 23 lines, or it will scroll up and wierd things will start to happen (aesthetic problems). Also, you will probably want to put the AT (@) macro @poff@ at the start of the background display. Note, when you actually put the @poff@, you'll have to use all caps (POFF) or PCBoard will not recognize it. This turns off PCBoard's more prompting, so you don't get 'Press (Enter) to Continue' while your backdrop screen is being displayed. The K-READ.CFG file is slightly more complex (at first). The first two lines should ONLY be numbers. On the second line (starting with second line because it's easier ) you must put the row that the options start on. For example, the first option is 'normal pcboard message prompt'; we'll say that the 'n' from 'normal' is at ansi position (27,5). Thus, you would enter '5' (without quotes) on the second line of your K-READ.CFG file. The first line contains the number that represents the LEFT-most X value for the highlighted text options. Okay, what this means is this: say you have options that are at ansi position (4,15) and (10,16). For those two ordered pairs alone, FOUR (4) would be the left-most value. For the different reading options in K-READ, you'll have an ordered pair for each option, thus making 18 ordered pairs, since there are 18 options. Now, since K-READ uses the SAME X position for every command, you may have to include pieces of your background ansi in the config file. This may not make sense, but... I suggest you look over the examples I've provided; they've all been tested with the PPE and should work for you, plus I tried to include every possible circumstance for the config files. They're all in the file EXAMPLES.ZIP (included in this archive). If you wish to use a background ansi and config file that I've created, REName your K-READ. file to something like BACK.BA~ and the K-READ.CFG file to CFG.BA~ (or anything, they are just for backup). Now ren the BACK?.PCB of your choice (from the EXAMPLES.ZIP file) to K-READ., and its corresponding CFG?.PCB to K-READ.CFG. Unfortunately, you can't mix and match config files and backdrop screens; that would look rediculous. If you can't get a certain background/config setup to work properly, don't hesitate to contact me, and I'll straighten it out for you. Note, however, the only way I will handle such requests is through my BBS. þ REACHING OUT -------------- raw sewage bbs: (309) 389-4754, USR v.Everything using my board gets the quickest reply ;) email: mgarman@heartland.bradley.edu Salt Air: Matt Garman