kaye@FSCORE.dec.com (Mark Kaye - Where's my Kama Sutra pop-up book for Zero-G) (02/18/91)
Why can't it save the External Protocol settings. I set the path to something like HD1:SCRATCH/ and have to do it everytime i power up. Mark Kaye | | | Box 72, Munster Hamlet | 613-838-3580 | kaye@fscore.dec.com | Ontario, Canada K0A 3P0 | | DEC fscore::kaye or kaye @kao |
thad@public.BTR.COM (Thaddeus P. Floryan) (02/19/91)
In article <2534@shodha.enet.dec.com> kaye@FSCORE.dec.com (Mark Kaye - Where's my Kama Sutra pop-up book for Zero-G) writes: >Why can't it save the External Protocol settings. I set the path to something >like HD1:SCRATCH/ and have to do it everytime i power up. RTFM. The external protocol specs clearly state you put a file in your ENV: directory containing the protocol's settings. In the docs for the xprzmodem.library, it is written that you put a file name "xprzmodem" in the ENV: directory, and the contents of that file are clearly documented. Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]
WGLP09@SLACVM.SLAC.STANFORD.EDU (02/20/91)
Actually, how external protocol configurations are saved is up to
the comm program. Since comm programs in principle don't know which protocol
is running at the time (except for the name), and since a new protocol can
come along at any time, and since there's no way to ask the XPR what its
current settings are, it is just kind of hard to have the comm program
take care of the default settings. The only way it can really do that is
by "explicitly" supporting certain XPR's. VLT for example "explicitly"
supports xprxmodem and xprkermit: VLT has menu items to change various
settings for these two and saves them in the VLT config file.
For the general case, the XPR docs *suggest* to use environment
variables, though the comm program *could* in principle allow the user to
type in an init string for each XPR and save it in the config file, and
then use it whenever the protocol by that name is requested. But since the
init string depends on the XPR, the comm program can't make any assumptions
about it, and it will have to be typed in verbatim by the user.
If there were ever an XPR 3.0, one of the new functions would be to
get an init string from the XPR for the current defaults.
Willy.