Forum unknown
· Telecommunications
#Starterm
9 messages in this thread
Hi Jim! This is being composed on-line, so please pardon any lack of
cohesiveness. I want to make some suggestions for StarTerm 4.0 <grin> since
I am having real problems with some of the things in StarTerm 3.01. Before I
start, let me say that I think version 3 is *very* well done and I am using
it at this very moment and intend to continue using it. Now: the things that
bug me:
1. I don't like having to name the disk it's on "starterm". That makes it
difficult to place on winchester unless I want to name my whole winchester
volume "starterm" (which I don't!). What you should do is have it look for
it's macro files etc. using a search path. ie: Look first in the current
directory, then look for "St.Stuff" on the current disk, then look for
"St.Stuff" on SYS: (which is the device booted from). When writing out the
"star.dir" file go ahead and write it in the current directory, perhaps with
a message telling the user to copy it to his "St.Stuff" directory if he wants
it to be global.
2. CR/LF translation should be handled separately for display purposes and
download purposes. On BIX, for instance, lines are delimited with a single
CR, yet download files often have CR-LF termination. If I forget to set up
Starterm *every* time I download, then I can't read the resulting file. If I
*do* make the change, then lines overlap after the download is complete.
3. It would be nice to have set up info (baud rate, CR/LF handling, parity,
etc) stored along with the phone number in the directory. That way, the act
of dialing a service will automatically set up for that particular service.
Rick, I'm going to add a search path to Starterm, so it won't have to be on a
disk named starterm, or have an ST.Stuff directory either. If you set up your
terminal and click the little save gadget next to the service in the dial
requester. those params will be saved for future loading when you call the
service. Jim
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.
Carriage return is a | and a one second pause (for dialing macros) is a ~ .
Ahh… I finally got it working with a "^M" (Capital M).
Strange.
Ahh… I finally got it working with a "^M" (Capital M).
Strange.
Carriage return is a | and a one second pause (for dialing macros) is a ~ .
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.
Rick, I'm going to add a search path to Starterm, so it won't have to be on a
disk named starterm, or have an ST.Stuff directory either. If you set up your
terminal and click the little save gadget next to the service in the dial
requester. those params will be saved for future loading when you call the
service. Jim