On Wed, 28 Aug 2002 12:12:05 +1000, Greg Chaplin
<[log in to unmask]> wrote:

>The problem is that I can't find how to set this. There's nothing useful
>in the online help files that were installed, and nothing much in the
>WRQ support website.

The procedure to set up Telnet Renegotiate Echo in Reflection is as follows:

Go to the Setup Menu and select: View Settings.
In the Search field enter: TEL
Click on: Telnet Renegotiate Echo
Under Setting Details mark the YES radio button.
Press OK

This now sets Reflection for Advanced Telnet.

Note: The items in View Settings make the entry in the Registry, not the
configuration file.  This particular item can only be done this way and
cannot be saved in the configuration file to be copied to other users.  So
you will have to set this item for each installation of Reflection.

Spend some time exploring the many items under View Settings to see some of
the hidden power of Reflection.

Most other items have the ability to be set into the configuration file as
an Event.  Event definitions are saved in the configuration file as follows:

Under the View Settings for a particular item, mark the Macro Syntax radio
button.

Note the registry value shown in the Setting Details section following the
line: Saved in the Registry

Now Save or Cancel (as appropriate) to close the View Settings window.
Go to the Setup Menu and select: Events
Click on NEW

Under Event Type select an appropriate trigger item, such as: When
Reflection Starts

Under Action mark the Commands radio button.
Under Command Type select: Visual Basic

In the command field enter (type) the macro syntax noted from the View
Settings window previously.  Note that they usually start with a period.

Press OK

Now Save the Configuration file and the Event will be saved and executed
upon each start up of Reflection.

I hope this helps.  It is not obvious stuff and I learned it by making a
support call to WRQ.

A problem we were having with users was that under some circumstances at
the end of a Reflection session the user would be prompted to Save or
Discard configuration changes that took place during a session.  If they
made some changes (by accident or otherwise) and typically Saved the
configuration, it might be ruined (such as saving with Block Mode on) for
the next use .  To fix this, go to the View Settings for: Save Changes on
Exit and change the Action from ASK to NEVER.  Then note the Macro Syntax
for this setting and make a start up Event for it as described above.  You
can also Lock the configuration (another View Setting) in a similar manner.

Good luck.

John Wolff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *