Boldly Go Collection

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

/ Boldly Go Collection / version40.iso / TS / 05B / PCHELP.ZIP / TECHHP.TXT

Wrap

Text File | 1992-03-15 | 22.7 KB | 549 lines

FILE TRANSFER ABORTS WITH NO CARRIER When a file download aborts immediately with the message NO CARRIER, try changing the ABORT XFER IF CD LOST setting (Alt-S, PROTOCOL OPTIONS, GENERAL OPTIONS, option C) to NO. Please note: this option affects ASCII transfers also. VT220 VT320 TERMINAL EMULATION FUNCTION KEYS PCPLUS.KBD If you are using the VT220 or VT320 terminal emulation and are experiencing problems with some function keys, your keyboard remapping may be missing "~" (tilde) characters at the end of the escape sequences. This can be corrected by replacing your pcplus.kbd file with an upgraded version available on the DATASTORM BBS or on CompuServe, library 3. File is called PCPLUS.KBD. The .KBD file distributed with the 2.01 version of the program does not have this problem. MODEMS.DAT MODEM INSTALLATION RECONFIGURATION PCINSTAL The modems installation data file (MODEMS.DAT) is available on the DATASTORM distribution bulletin board and on our CompuServe Forum (GO DATASTORM) in library 3. This file will be updated periodically to include setups for new modems and corrections to existing setups. To reconfigure your modem using MODEMS.DAT, copy it to your PROCOMM PLUS directory, type PCINSTAL, choose "RECONFIGURE PROCOMM PLUS" from the INSTALLATION OPTIONS menu, and choose "INSTALL A NEW MODEM OR DIRECT CONNECTION". CREDIT CARD LONG DISTANCE DIALING FROM DIALING DIRECTORY Here are some tricks that will get you past the Hayes-compatible modem's command "buffer", which usually holds about 40 characters, and allow you to use long distance credit card numbers for dialing: 1. Pull up the dialing directory. (ALT-D) 2. Select P for long distance codes. 3. Define A as your access number. For example: 1800nnnnnnn;^M~~~~~~ATDT where "nnnnnnn" is a seven digit number. Notice the ";^M~~~~~~ATDT" at the end. This flushes the modem's buffer, pauses 3 seconds (the tilde is PROCOMM PLUS' half-second delay), and leaves it ready for another list of characters to dial. 4. Define B as: ;^M~~~~~~~~ATDTnnn nnn-nnnn nnnn again, where the n means a digit. You may have to experiment with the length of the pauses. The idea is to delay the string in the "B" dial code until the long distance service prompts you for it. 5. Save the LD codes and go back to the dialing directory. 6. Define your long distance number to dial as Annn-nnn-nnnnB (for example, the DSTORM BBS entry looks like this: A314-875-0503B [the dashes are optional]). When setting this up, remember that PROCOMM PLUS allows up to 60 character total in the dial string going to the modem. 7. Save the entry and dial it as usual. CARRIER DETECT ALWAYS HIGH ONLINE LONG HANGUP HOST MODE SCROLLS If your screen shows "ON-LINE" in the lower right-hand corner when you start the program, even though you're not online with another computer, then you'll need to set the "Send init if CD high" option (Alt-S,M,G,F) to "Yes". Starting with version 2.0, this option is set to "No" by default, and will prevent Procomm Plus from initializing your modem if it thinks you're "ON-LINE". Incorrect handling of the CD signal, and failure to initialize the modem, may cause a wide variety of problems. Here are some of the most common: - Hanging up (Alt-H) seems to take forever. - Your status line still says "ON-LINE" even after you've hung up. - When you exit the program (Alt-X), it always asks "HANGUP LINE? (Y/N)". - Host mode (Alt-Q) seems to talk to itself, and scrolls off the screen. In most cases, setting "Send init if CD high" to "Yes" will solve these. ASPECT SCRIPT DEBUGGING ADVICE TECHNIQUES Here is an explanation of techniques to use when debugging ASPECT scripts: STYLE ============== Always write your script file as though your sixth grade teacher is looking over your shoulder. This may sound funny, but Mrs. Jones was looking for neatness, readability, clarity, application and creativity. o Neatness. A clean, well-organized script file is a pleasure to work with, and a pleasure to return to for upgrades and modification. A procedure is nothing more than a paragraph in your code -- don't make it do more than one straightforward task. o Readability. Use descriptive variable and procedure names. "current_time" means so much more than "int_one", yet both can be used as an integer name in ASPECT. A call to "proc get_user_name" has obvious effects, whereas a call to "proc getit" a mystery. o Clarity. Mrs. Jones wanted your readers to see, and understand what you wrote. Do the same for your script files, using vivid comments where useful. Do not place comments to fill white space, but only to explain code: NOT: inc counter ; Add one to counter BUT: inc counter o Application. A script task has a specific goal -- lose sight of that goal and your script will suffer as well. o Creativity. Have fun, and stretch your horizons. Don't try to write the script all at once, unless it's a short one. Frustration is your enemy -- don't give him time to build walls. TACTICS ======= ASPECT 2.0 has no trace mode. Instead, we can develop our own 'trace tactics' to discover why something is not working. The first line in any complex script should be: define DEBUG 1. Subsequently, as each procedure is being developed, include strategic test statements: $ifdef DEBUG fatsay 1 1 $termbold "PROC MINE %d %s" number my_string $endif One can easily comment out either/both the $if block, to remove that specific block, or the define DEBUG, to remove condition-reporting altogether. Conditional reports are also easily added/removed from smaller scripts, as well. When editing a script, make one change at a time, and test each change. Nothing is more frustrating than realizing the change in PROC B was fine, but the change in PROC C, which you ignored, caused the whole script to explode. Discipline yourself, and save time and energy. LOGIC ===== A good writer plans before writing. A good programmer must plan, as well. The problem can be taken in steps: o What is the goal? What is the purpose of the script? What must it do? What can it do? What features can I add? o Can the goal be reached? Can the task be accomplished in the chosen language? What obstacles are there? For example, in writing a card game, you must have a means of describing a deck of cards, of shuffling, dealing, and displaying them. Can you do this? o In the code, what steps must I take? What procedures are required? How do they interact? In the card game, the procedure which deals the card must be able to access the deck in the same way as the procedure which shuffles them. The method you devise must be flexible enough for both. o Where do I start? What is the beginning point? For the card game, is it dealing the cards? Drawing the playing board? Shuffling? Don't be afraid to invest a measure of time EXPLORING an idea -- some great scripts have their origins in such exploration. Write experimental procedures which can be quickly tested and either saved or erased without pain. SUMMARY ======= In short, ASPECT programming, like other programming, is a matter of personal style. Your ability to script, and to debug scripts, is going to depend heavily on your personal style, and your willingness to explore. TERMINAL EMULATION COLORS BOLD REVERSE The terminal color options for bold and reverse apply to terminals that do not support cumulative attributes. In 1.1B we were incorrectly emulating some of the ANSI/DEC terminals by not supporting cumulative attributes; in 2.0 this is changed. For reverse we turn on the reverse bit rather than setting to the user choice in terminal color options, for bold we turn on the bold bit rather than setting to the user choice. This is the only way to support stacked attributes such as bold-reverse-blinking. This change applies to the entire ANSI/VT family of terminals. TERMINAL KEYS TERMKEY ASPECT LOCAL COMMANDS You can pass actual PROCOMM PLUS commands to the executive loop using the ASPECT "termkey" command. termkey 0x2000 ; for example, will call the dialing directory, just as ; though the user had pressed ALT-D. The following short script will call up the dialing directory, then execute a linked script after PROCOMM PLUS has made a connection to another system: proc main termkey 0x2000 ; Call the dialer execute $d_script ; Execute the linked script endproc Other termkey values can be found by accessing PROCOMM PLUS's help utility. ASPECT SCRIPT CONVERSION 1.X TO 2.0 FORMAT To convert a script from PROCOMM PLUS 1.xx to 2.0 format, simply type: CONVERT MYFILE<return> where MYFILE.ASP is the name of the file. The convert utility will process your file, reporting any changes that it makes along with any errors that it cannot cope with. Correct any errors that CONVERT reports. Often, these 'errors' are no more than syntax problems: transmit"There is no space here!" ; will generate an error for a missing space ; between 'transmit' and the quoted string. Other errors are more serious. Deeply nested goto's and gosub's, for example, can snarl CONVERT. Once the errors and warnings from CONVERT have been dealt with, you'll need to compile the script: ASPCOMP MYFILE . ASPCOMP will begin to compile the file, reporting any errors and listing warnings. It is recommended that you run ASPCOMP from the command-line, since it runs somewhat faster, and you can watch the error messages generate directly. If you run ASPCOMP from within PROCOMM PLUS itself, you'll have to view MYFILE.ERR to see the errors which stopped the compiling process. Typical errors on CONVERTed script files are transmit SEND THIS! ; 1.xx ignored missing quotation marks, transmit "RANDY! ; sending the string anyway Or: if not connected then ; will generate an error for the unexpected ; ( and illegal ) 'then', which 1.xx ignored. After the script has been converted, and compiles normally, you'll need to test it on the host system or application. Keep in mind that you may need to add or subtract delays, to adjust for PROCOMM PLUS 2.0's enhanced script abilities. One final note: in some cases, it may be more desirable to completely revamp the script file. This is especially true when the old script relies upon several layers of goto's and gosub's. A modular script, properly segmented into one-function procedures, is much more easily maintained and improved. AT&T6300 SCREEN DISPLAY MISSING STATUS LINE If you have an At&T 6300 or compatible your display will appear to be missing a status line. Also the dialing directory will appear to be missing the information box at the bottom of the screen. This is because a non-standard address is reported and we think you have a 60 row screen. You need to download the latest patches file for PROCOMM PLUS 2.0x, unarc it, and install the following patchs: 6300E.DTP (for PCEDIT), 6300H.DTP (for PCHELP), and 6300P.DTP (for PCPLUS). PATCHES DTP CORRECTIONS CHANGES BUG FIXES ENHANCEMENTS "Patches", or "field patches", are changes to one of the executable modules distributed with a product. This is accomplished by providing the user with a text file that serves as a source or script to DT_PATCH.EXE program, which actually writes the changes to the executable file. A patch file will always have an extension of .DTP. When you view this file, you will find a description at the top of what the patch does, and which program it changes. You should not edit or change a patch file in any way before installing. Any patch you install should be provided by DATASTORM. All available patches for DATASTORM products are bundled in an archive file. This file is updated as new patches become available, and is posted on DATASTORM's distribution bulletin board and on the DATASTORM support forum on CompuServe. If you haven't downloaded the patches archive yourself, be sure you trust the source that did. The DT_PATCH.EXE, required to install a patch, is included on your distribution diskette, and installed on your hard drive by PCINSTAL. Here is a list of the patches issued by DATASTORM for PROCOMM PLUS 2.01 as of June 13, 1991. These patches are specific to the 2.01 maintenance release of PROCOMM PLUS. This list is in a file called PATCHES.TXT in the patches archive in the DATASTORM Forum on CompuServe: The following patches are provided on the PROCOMM PLUS distribution diskette: CURSBIOS.DTP, ESCTIME.DTP, HOSTKEYS.DTP, PADCHAR.DTP, SFTIMOUT.DTP All other patches are provided in most recent patch file (DTP613.ARC file (CompuServe, DATASTORM Forum, library 3 as of 6/13/91) and PATCH20.ARC on the DATASTORM distribution bulletin board. The DT_PATCH.EXE program (included on your distribution diskette, and installed on your hard drive by PCINSTAL) is required to install a patch. MOUSPCE.DTP Target File: PCEDIT.EXE version 2.0 This patch disables the mouse support in PCEDIT. Necessary to run under DOS 2.x. MOUSPCI.DTP Target File: PCINSTAL.EXE version 2.0 This patch disables the mouse support in PCINSTAL. It's necessary to install this patch if you need to install on a system running DOS 2.x. WARNING!!!! This patch is for the PCINSTAL.EXE with a file size of 121950 bytes. Do not use this patch on any other version of the program. Doing so will cause incorrect operation of the program. MOUSPCP.DTP Target File: PCPCLUS.EXE version 2.0 This patch disables the mouse support in PROCOMM PLUS. Necessary to run under DOS 2.x. MOUSEPCS.DTP Target File: PCSETUP.EXE version 2.0 This patch disables the mouse support in PCSETUP. Necessary to run under DOS 2.x. MOUSPCH.DTP - for use with DT_PATCH.EXE Target File: PCHELP.RTE This patch disables the mouse support in PCHELP. PADCHAR.DTP Target Program: PCPLUS.EXE version 2.0 This patch allows the user to define which character PROCOMM PLUS uses to fill the last block sent during an XMODEM transfer. Since XMODEM sends blocks of fixed length, the data sent in the final block is almost always less than that required to fill out the block. The default character used by PROCOMM PLUS to fill out the difference is the Ctrl-Z character (decimal 26). This patch changes that default to a NULL character (0). If you wish, you can change the default to any fill character. To define your fill character, change the last line of this file to the decimal value (from 0 to 255) of the character to use. SFTIMOUT.DTP Target Program: PCPLUS.EXE version 2.0 When performing software flow control (XON/XOFF), PROCOMM PLUS version 2.0 automatically clears an XOFF if no XON is seen within a specified amount of time. The default timeout period is 20 seconds. In other words, if PROCOMM PLUS detects that it should halt transmission because it has seen an XOFF, the program will wait until an XON is received or 20 seconds elapse. This patch file can be used to update the XON wait period. The first value (following "O47417") is the number of seconds which can elapse (a value between 0 and 255). As distributed, this patch file will increase the timeout to 60 seconds. If you desire a different value, edit this file (with a standard ASCII editor) and change the value as shown. ESCTIME.DTP Target File: PCPLUS.EXE version 2.0 When an ESCAPE is received by PROCOMM PLUS, the program waits a maximum of two seconds for another character to continue the escape sequence. If another character does not arrive in this time, we no longer treat the incoming characters as part of a potential escape sequence but simply as ordinary received characters. For some packet-switching networks with extreme delays the two second wait is not long enough. This patch changes the two second wait to four seconds (the value 72 is clock ticks where each second is 18 ticks [4 * 18 = 72]). If a different timeout is desired, replace the value 72 with any value between 0 and 255 (255 = 14 seconds). CURSBIOS.DTP Target File: PCPLUS.EXE version 2.0 Certain TSR's and device drivers interfere with PROCOMM PLUS' low level cursor manipulation. This patch will force PROCOMM PLUS to use the BIOS for cursor addressing. This should eliminate conflicts with those programs which make invalid assumptions about the cursor. WARNING! This patch will slow down Terminal Mode to some degree. Use only if you are experiencing a conflict with another program. HOSTKEYS.DTP Target File: PCPLUS.EXE version 2.0 Purpose: Change the default keys used by Host mode at the main menu Instructions: Simply replace the letter below with the desired new letter. Make sure the new letter is in upper case (lower case letters will make the option unavailable). This is the default key string for normal users: F R L C D U G H T | | | | | | | | | | | | | | | | | +-- Time | | | | | | | | | | | | | | | +---- Help | | | | | | | | | | | | | +------ Goodbye | | | | | | | | | | | +-------- Upload | | | | | | | | | +---------- Download | | | | | | | +------------ Chat | | | | | +-------------- Leave mail | | | +---------------- Read mail | +------------------ Files The string for super users is the same with the addition of 'S' and 'A' for Shell and Abort CVT20.EXE - Convert 2.0 .DIR file to 1.1B format This program converts the PROCOMM PLUS 2.0 dialing directory (PCPLUS.DIR) to PROCOMM PLUS 1.1B format. Useful if you have installed PROCOMM PLUS 2.0 as an upgrade to your 1.x version, and need to restore the directory file for any reason. This executable should be run from the DOS command line in the following way: CVT20 <input file name> <output file name> 6300E.DTP Target File: PCEDIT.EXE The AT&T 6300 (and compatible) computers have a non-standard bios data area that does not report the actual number of lines on the screen. This patch corrects video display problems that occur when using PROCOMM PLUS 2.0. 6300H.DTP Target File: PCHELP.RTE The AT&T 6300 (and compatible) computers have a non-standard bios data area that does not report the actual number of lines on the screen. This patch corrects video display problems that occur when using PROCOMM PLUS 2.0. 6300P.DTP Target File: PCPLUS.EXE The AT&T 6300 (and compatible) computers have a non-standard bios data area that does not report the actual number of lines on the screen. This patch corrects video display problems that occur when using PROCOMM PLUS 2.0. NOBLANK.DTP Target File: PCPLUS.EXE version 2.01 This patch turns off the Host Mode screen blanker. MONITOR.DTP Target Program: PROCOMM PLUS version 2.01 Applying MONITOR.DTP disables the key, ctrl-\, that invokes Monitor mode. *Note: Ctrl-\ is not remapped to a different key, so Monitor mode can only be invoked from the Menu line. NO_STAT.DTP Target File: PCPLUS.EXE version 2.01 This patch causes PROCOMM PLUS to send an ASCII 29 when Ctrl-Right Bracket is pressed. Note that the Status Line will no longer toggle its display when Ctrl-] is pressed. After applying the patch, the Status Line can be toggled by entering PCSETUP (Alt-S), selecting Display/Sound Options, and choosing item F. The Status Line may also be toggled from the menu line. SETTING VIDEO MODE FOR 132 COLUMN DISPLAY Generally, the safest way to set your default video mode is to follow the prompts in the PCINSTAL program. PCINSTAL includes a routine that checks your video controller's possible modes, and automatically configures PROCOMM PLUS to take advantage of your video capabilities. If you choose to manually change your display options, the following information will prove useful. Emulations: At this time, only ANSI, Wyse, and the DEC-compatible series of terminal emulations support 132 column mode. Mono & CGA video controllers: You won't be able to use a true 132 column mode because your video card does not support it. However, you will be able to take advantage of a simulated 132 column mode. To activate a split screen 132 column mode, enter PCSETUP by pressing alt-S at the terminal screen, then select TERMINAL OPTIONS and select option L. Toggle this setting to "132". Once this mode is activated, you can scroll between the two halves of the screen by pressing Ctrl-left arrow and Ctrl-right arrow. EGA & VGA video controllers: In order to use true 132 column mode, your video card must have a video mode option that provides 132 column display. If your controller doesn't support this, then configure it as if it were a Mono & CGA controller. However, you will be able to take advantage of extra lines if you wish. If your video card does suppport true 132 column mode, you can take advantage of it by entering PCSETUP (Alt-S) and selecting DISPLAY/SOUND OPTIONS from the main menu. Option 'I' of this menu sets the video mode you want when you first start PROCOMM PLUS. If you want to start in 132 column mode, set option 'I' to "USER MODE." Keep in mind that you can switch between 80 and 132 column mode as needed, so you may want to leave this set to DOS mode. Option 'J' (VGA extraline count) will have no effect unless you have placed EXTRA X 80 in item I. You can safely leave it set to the default of 50. Option 'K' (User video mode) is the setting required to invoke true 132 column mode. Your video card probably supports a number of video modes, each of which has a reference number associated with it. The manual for your video card should provide you with a listing of available video modes along with the number associated with each. This number is usually listed as a hexidecimal (base 16) number in video controller manuuals, while PROCOMM PLUS needs the decimal equivalent in field 'K' of the Display/Sound Options screen. If the numbers are listed in hex, then you must convert the numbers to decimal and enter the number of the video mode that you want into item K. The ASCII table on page 257 of your User Manual provides this conversion information. If you happen to change to a video mode that your card does not support and you are unable to read the screen as a result, just reboot your computer and run PCSETUP as a stand-alone program. Enter the PCPLUS subdirectory and type 'PCSETUP.' From here you should be able to change the video setup and use PROCOMM PLUS once again.