MBBS MEXPCP MEXPCP-WARNFIXPCPMEX DOCÿ ÿ ÿ READ PCP 213 653-6398  Date: 08/07/86 To : All PC Pursuit II Users Re : Aborted Uploads Fix The following warning submitted by Bob Freed only applies to users of the new PC Pursuit services which allow for multiple system connections without having to redial (nor does PC Pursuit call you back). Those of you who continue to use the old PC Pursuit services will not experience this problem. All is not as bleak as Bob makes it seem... If you do experience a problem of the sort described below, the following commands will provide a fix: <-- from anywhere, during connect @ <-- returns you to command mode SET? 1:0 <-- enter this entire line PAR 1:0 <-- PC P's acknowledgement CONT <-- return to terminal mode Note: This fix disables the special feature which allows you to return to the command mode for making additional calls, so you will have to call PC Pursuit back when finished with this particular connection (i.e. all " @ " sequences will be ignored for the remainder of your connection). Special thanks to Bob Kramer (Rock Island MBBS-RCPM), whom GTE gave this special fix to and who posted same on my system during the time he was beta testing PC Pursuit II for them. Without his notes, this fix might not be discovered and those of us using PC Pursuit II would be cussing up a storm. As it is, we now have only a bit of inconvenience to put up with... Tom Brady Decibel RCP/M (PBBS) (404) 288-6858 DSC KSET PARITY EVEN STAT WTECHO OFF DIAL ???-???? # <-- Put your local Telenet access # here WAIT SILENCE 2 (leave the "#" after the number..) SENDOUT "^M" WAIT STRING 3 "TERMINAL=" SENDOUT "D1" WAIT STRING 2 "@" SENDOUT "C DIAL{1}//12,????????" <-- Put your PC Pursuit User ID here WAIT STRING 2 "PASSWORD = " SENDOUT "????????" <-- Put your PC Pursuit password here WAIT STRING 3 "CONNECTED" (and take out these comments and KSET PARITY NONE you should be ready to roll.) SENDOUT "ATZ" WAIT STRING 2 "OK" SENDOUT "^M@" WAIT STRING 2 "@" SENDOUT "SET? 1:0" WAIT STRING 2 "PAR 1:0" SENDOUT "CONT" CALL {2} # PCP.MEX -- Auto dialing via PC Pursuit using MEX script file Version 1 - 08/23/86 - by Kim Levitt This .ARC contains a PCP.MEX file which can be used directly or indirectly (via another .MEX file if you wish) to call a system via PC Pursuit.. It includes a special sequence which is performed as described in the PCP-WARN.FIX file included in this .ARC. The MBBS.MEX file used PCP to call the MBBS HQ PDSE.. NOTE that before you can use PCP.MEX, you must edit it (use your favorite word processor in "normal" text mode (non-document mode for WordStar users)..) and change the fields indicated with question marks ??? to include your local Telenet access number and your PC Pursuit user ID and password. You can then invoke it from the command line with a command like: READ PCP 213 653-6398 or you could invoke it from a MEX file.. If you have the READ CMD extend feature on, you can use PCP as a command in and of itself as in: PCP 213 653-6398 Note that you should log off of the remote system and let it hang up, then disconnect (by dropping carrier) on your end to totally disconnect from PC Pursuit (you should set your modem switches so the DTR line controls the switchook and do a STAT SMDISC OFF and clone MEX. These command files were written for MEX-PC v1.65, but should work with the CP/M version of MEX-PLUS as well, but I can't be sure about that.. Oh yeah, when you edit PCP.MEX, be sure to take out the arrows and comments I added to help you find the places to update.. Hope this .MEX file does the trick for you.. It sure works great for me... (After I got the MEX STAT settings right.. Be sure you disable the TRIGGER char by using a STAT TRIGGER "" if you haven't already..) -- Kim Levitt sysop, MBBS HQ PDSE (213) 653-6398