PT3.1 editor, etc

[badbunny@tfsp.saic.com (Brendan Hoar)]

Re-writeing the PT3.x editor to use more memory would have taken a complete 
rewrite according to Greg.  It just isn't in the plan for a ".1" upgrade.

Things that were time consuming that he did.  Rewrote the entire memory
management scheme, which took about 3 weeks of beta testing to return get the
program to a state of normalcy (most of the beta testers during the project
were calling the InTrec system at least once a day).  Redid all the modem & port
drivers in a different format, since the old formats were huge disk & memory
wasters.  Made a lot of changes to the macro system (new commands & lots of
bug fixes).  Enhanced a lot of the commands (try out the view-file command, etc)
 as well as making something work like you'd expect (eg the cursor remaing where
 you left them in editor & scrollback).  Made Zmodem much more configurable:

; $L=0-255 makes Zmodem recv Stream & flow control around disk writes
; $L=256-65024 sets an exact buffer size w/ no flow around writes.
SET $L=1 ; STREAMING (1k BUFFER) - better for EC modems & some disks
;SET $L=0 ; STREAMING (63.5k buffer) - better for Null Modem Connections

Currently values of 2-255 should map to the same routine as 1 or 0, but I
haven;t played with it.  The Streaming 1k buffer tells the other side to
stream, but at every 1k, PT3.1 will lower RTS, write & raise RTS.  Its neat
to watch.  My guess is that you'd want $L=0 if you were using hardware flow
control and floppies.  I use $L=1 since I have a RF.

Oh yeah, you'd insert $L=x in your @1 macro in your PT3.GLOBAL file, or anywhere in your PT3.STARTUP file.

You can also pass the names of Macro files or dial list files to PT3.1 from
finder or ProSEL and it will run/dial that system automatically - good for
using PT3.1 as an extension from other programs (as long as they use the
standard ProDOS parameter passing).

Also, neat feature:

Command (?=Help): ?
 
ProTERM Unattended Commands:
 
S = Send    R = Receive
L = Log     D = Dir
C = Chat    V = View
H = Hangup  M = Macro
 
Command (?=Help): M
 
Macro Command: YO
 
No Macros Available!
 
Command (?=Help): M

Yep, you can run Macros remotely.  Most likely you'd hardcode it so that the
Macro command used was like a password that would run another macro that made
more features available.  Basically, you could write a macro that would
allow you to do many more things from remote.  This feature is not mentioned
in the documentation since its a very big security hole if used improperly.

Here's a chunk from my PT3.GLOBAL file that may be of interest:

@@7 ; Remote Macro execution through this routine
 ;Currently this is a null operation & returns caller to Unattended
 ;Activate by putting @ or A-I in the Timeout box and then using the new
 ;Macro command with an argument from the remote menu
 pr "No macros available."
 DO "misc:un","[]"
ex

Anyway, this is just a few things off the top of my head.  We spent months
in the beta test and the program has gotten a lot cooler, IMHO.  Its not
obvious by just looking thru the menus, though.

BTW, if you had a PTM.something file for a modem that isn't listed in the
install for the demo (Assuming the demo has all the same modems listed),
bug Greg about getting one created for PT3.1.  Or send me a note and I'll pass it on.

Enjoy!

PS - how do I decode the AT20... file on cco?  GS Shrikit wont touch it
...
Brendan