#Starterm
05-Jul-86 23:42:00
Sb: #25416-#Starterm
Fm: Larry Phillips/ICUG 74025,636
To: Jim Nangano/SYSOP 76703,4254
This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.
Just a short note to talk about Starterm Jim. As you know from the messages
we exchanged the other night, I too would love to see the search paths.
Here's how I run with Aterm6.11: CD RAM: RUN ATERM
Since ATERM is in my C: directory, it loads and runs, looking in RAM: first
for a file called "init.keys". If not found, it looks for "S:init.keys".
Having found that, I can then just go ahead and use it, or call up another
Function key file. When specifying the filename, I merely call it by name and
it will look in the S: directory if not found in the root directory.
As you can see, the whole thing is designed to be easy and quick (it actually
doesn't matter that I am running from CD=RAM:, except that I happen to like
downloading to RAM:).
One more small point. The character I use for stopping the stream on CIS is
CYTRL O, rather than CTRL P. The reason for this is that at one time I was
forced to use Datapac to access CIS, and a CTRL P caused Datapac to butt in
and wait for commands. If there are users on Datapac (or any overseas packet
network) they will probably have the same problem. Suggest an additional
entry on the top line for this. (There's just room.)
Oh.. another.. (so I lied about one more.. <grin>)
The Function key edit window has no "OK" or "DONE" box to click. I figured it
out after a short time, but perhaps it would be best to have one to save
users the effort of figuring out that "CANCEL" doesn't wipe out everything.
Oh, and I tried "^m" for C/R, but it doesn't send a C/R, but does send a "- "
(minus space). Will diddle around with it to see what's what.