HAM Radio 1/HamRadio.cdr/misc/goldtd/trythis.doc

Text File | 1991-01-16 | 19KB | 421 lines

                           Welcome

The Packet-GOLD test drive disk contains a self-extracting program,
GOLDTD.EXE that creates a runtime version of the  commercial program
along with minimal documentation, a quick reference guide, and some
other useful files. Copy GOLDTD.EXE to a hard disk and run the program
to unpack the files it contains. First time Packet-GOLD users may
wish to run through these "test drive" as part of your own introduction
to the program.

As a functional demo program, it can be used several times. You can
make multiple connects, Shell to DOS, Cut/Paste, and do many experiments
with the program. The program will run for 15 minutes at a time, which
is plenty of time to work through each of the following suggested
exercises.

If you like the program, please consider purchasing a copy. That way
we can provide you with updates, technical support, and you can provide
us with some incentive to keep at it, improving things to make your
operation easier, simpler, faster, and above all, more fun.

                       Things to Try

The program has many features and settings, but operating is simple
and efficient. To start with, on your first 15 minute tour, just
make a couple of connects to see what's involved.

If you're an experienced packet user, have a couple of callsigns ready
that you can connect to. You'll be doing a multiple connect right off
the bat.

Get the program going. Enter the right COM port and Baud rate, your
callsign and name. You'll do this each time you run the program.

The program will establish a link to your TNC. It may take a minute
or so the first time you run the program, but once you've got things
working, the program "comes up" very quickly. It tries NOT to reset
your TNC, that is why it takes some time to figure out how to avoid
resetting.  We ask that you LEAVE THE BATTERIES IN the tnc, unlike
the AEA program. Our software understands how to deal with the TNC
no matter what state it is in, without resetting it, so we think
you'll want to leave batteries in your TNC, so that messages are saved,
and configuration information is retained even if you turn off your
TNC or it loses power.

LESSON #1: Single Connect

   1.  Type in just a callsign, e.g. WA4EGT or type in a path, such
       as WA4EGT  or  WA4EGT VIA DANAPT if you need to digipeat.

       Note: If you don't know who you can connect to, use the
       Mheard function, [Alt-F2]. Notice that when you depress the
       [Alt] key, the "keyline" below changes to show you what each
       key does. [Alt-F2] is shown as MHEARD.

   2.  Hit the [F7] key (connect key) when you've typed in a callsign.
       Don't type C CALLSIGN, just CALLSIGN.

   3.  After connecting, use [Alt-F7] to disconnect. Choose NORMAL
       disconnect. Notice that if frames are still pending, the
       dicsonnect is suspended until the frames are sent and
       acknowledged.

       If there is still time in the countdown sequence, hit [Alt-F7]
       again, and select to "cancel the disconnect" request.  Then
       you will have to do step #3 again to initiate another disconnect
       request.

   4.  Go to the NETWORK VIEW screen using [F2] if you are not there
       already.

   5.  Go to the PREVIOUS SESSIONS screen using [F3]. Notice that
       the text of your previous session is there.


LESSON #2: Multiple Connect

   1.  Type in a callsign or path (callsign VIA ...) and hit [F7].

   2.  Do step 1 at least once more, so that you have two (or more)
       sessions going.

   3.  Switch between sessions using the [F4] "NEXT" key.

   4.  Switch to the NETWORK VIEW screen using the [F2] key. Notice
       the full-screen.

   5.  See a list of stations to which you are connected by depressing
       the Ctrl key (by itself).

   6.  Go to each session using the [F4] key. Enter the operator's name
       using the [Alt-n] key sequence.  Do this for each session.
       The names are saved permanently in Packet-GOLD, but are only
       saved temporarily in the Test Drive version.

   7.  Go back to the NETWORK VIEW screen using [F2].

   8.  If text "comes in" from a session, and you are on another session
       screen, or the Previous Sessions or Network View screen, you will
       see a message "Pending From xxxx" in the upper right corner of
       the status box.  Depressing the "next" key [F4] will take you
       to that session immedately.

   9.  Go to each session using the [F4] key, and start typing a line
       but do not hit the [Enter] key to send it quite yet.  Switch
       to each session and put in a partial line.  Notice that each
       session has it's own "text entry/command entry" line. You can
       move the cursor using the "arrow" keys, overwrite or insert
       text.  The program saves the cursor "state" for each session
       as you switch from session to session.

  10.  Initiate a disconnect on each session. When all are disconnected,
       go to the previous sessions screen using [F3] and review the
       sessions.


LESSON #3: NET/ROM Node

   1.  Identify a node, or several nodes that you use and can hit
       easily.  Determine the node ALIAS. There are a number of
       advantages to using node ALIAS names, rather than callsigns,
       such as:

         a.  You can establish multiple connects to the ALIAS that
             are not possible using the node callsign.

         b.  When a routed node disappears from the nodelist, you
             will be informed with "invalid callsign" if aliases are
             used. If just the callsign is used, and the routed node has
             been dropped or disappeared, the node attempting the
             route will drop back to an ordinary connect attempt and
             eventually retry out.  Any callsign used and not found
             in the nodelist is assumed to be a direct connect from
             the node, and not a routed connect. Using ALIASES assures
             that if the node has been dropped from the routes, you
             will be immediately informed.

   2.  Assume the node is called  NRNDE.  You want to connect to W1AW
       after connecting to NRNDE. Type:

                NRNDE|W1AW

       on the command/text entry line and hit [F7]. The program will
       establish a connect to NRNDE-n and then issue a connect to
       W1AW automatically.

   3.  Establish a few connects using the NRNDE node. You will notice
       a couple of things:

          a.  Each connect goes to a different SSID of NRNDE. For example
              you might see NRNDE-10, and NRNDE-13 etc. The program
              assures that if you use the "or bar (|)" technology, that
              multiple connects to the are established automatically.

          b.  The connect progress is shown to you on the session screen.

          c.  As you make progress, you will notice the callsign in the
              status banner indicates the current connected station.

    4.  If you have a two hop connect, like NRNDE and then to SECNDE,
        you can type:

                NRNDE|SECNDE|W1AW  [F7]

        The program will establish a connect to NRNDE-n, then request
        a connect to SECNDE, and finally ask for a connect to W1AW.

        Note: BPQ nodes may require using a "port" number in the
        connect request (except when specifying a routed node in its
        internal node list).  If W1AW is on port 1 of a BPQ node in
        the example above, you would type:

                NRNDE|SECNDE|1 W1AW  [F7]

    5.  If you need to Digipeat into the first node, and the digipeater
        is W2JUP, try:

                NRNDE VIA W2JUP|SECNDE|W1AW [F7]


LESSON #4: Quick Connects

    1.   Using the connect paths from prior examples, you can now
         setup a few "quick connects" or "point and shoot" connects.

         Once in the program, hit [Alt-S] for setup. Then highlight
         QUICK CONNECTS, then choose ADD.

    2.   Enter the name of the remote station, hit [Enter], then
         type in the path.  For example:

         Name:   ARRL HdQrtrs
         Path:   NRNDE VIA W2JUP|SECNDE|W1AW

    3.   Do this for each callsign. Some "paths" may simply be the callsign
         of a station that is nearby, and doesn't require any special
         digipeating or node usage.

         When done, use the [ESC] key to bring you back to the program
         window area.

    4.   Press the [F7] key with a blank entry on the command line. This
         causes the program to present you with a "pick list" of your
         quick connects.  Highlight one, and hit [Enter] to start the
         connect process.  Do this for all of the entries in your Quick-
         Connects list.

    5.   Note: For emergency use, when "Tactical" callsigns are contemplated,
         enter the tactical callsign under as the NAME, and the FCC call
         in the PATH. Also enter the Tactical callsign as the "NAME" of
         the station in your NAMES list (created by [Alt-n] or in the
         setup area under Names).


LESSON #5: Changing Parameters

    1.   Enter a parameter name, such as MYALIAS and hit [F10], the
         command key.  The program will display the contents of the
         parameter.

    2.   Type a parameter and a value, such as MYALIAS FIRESTN followed
         by [F10]. This will enter the parameter value.

    3.   Type DISPLAY [F10] to see a list of parameter groups. Highlight
         one and hit [ENTER].  You may now move the cursor to a parameter
         and alter it's value.  Typing DISPLAY M [F10] jumps immediately
         to the Monitor parameters.

    4.   Hit [F10] by itself (no parameters on the command entry line).
         You will see (at a minimum) STARTUP and SHUTDOWN.  These are
         the names of special parameter files with the extension .TNC.
         Highlight STARTUP, hit [Enter] and notice that all of the
         startup parameters are loaded into your TNC.

    5.   Use [Alt-S] to get to the setup menu. Select TNC files.
         Highlight STARTUP and hit [Enter].  This is a .TNC file. You
         can edit it (we suggest not editing it unless you know what
         you wish to change).  Use [F1] help to display your options.

    6.   In the setup area, under TNC files, you will notice <new> and
         <current>.  Selecting <new> allows you to create a parameter
         file with settings you may wish to try.  Experiment.

LESSON #6: Sending CQ

    1.   On the Network View screen, hit [Alt-U] to enter the CQ/UNPROTO
         mode.  Now anything you type on the screen followed by the
         [Enter] key is sent out as "unproto" or unnumbered information
         frames.

    2.   Look at the value of your UNPROTO by typing UNPROTO [F10].
         If it is not CQ, then set unproto to CQ by typing:

                UNPROTO CQ [F10]

    3.   Each time you leave the Network View screen, the CQ/Unproto
         switch is turned off. This is done to avoid sending frames
         that are by accident. If you stay on the Network View screen,
         and are in the CQ mode, all text you type is sent out as
         [UI] frames.  You might set your UNPROTO to CQ VIA (some call).
         Then you can see your CQ frames.

    4.   If you have newer ROMS, set MXMIT (monitor Xmit) to on, by
         typing MXMIT ON [F10]. This allows you to see when your frames
         are transmitted.


LESSON #7: Changing Program Options

    1.   Use [Alt-S] to bring up the setup menu. Select Setup from
         the menu.  Explore the various menu areas.

    2.   Look at the Alt-n messages. Notice that ?CALL and ?NAME are
         in one or more messages. These are "macros" that are filled
         in by the program with the current CALL and NAME of the
         connected station.  To use an ALT-N message, when connected
         to some station, hit [Alt-0] to [Alt-9] and the text will
         be placed on the text entry line.  To erase or clear the
         text entry line, use [Alt-X].  Using [Alt-n] followed by
         [Alt-x] is a convenient way to find a message if you've
         forgotten what it is. Or just type [Alt-S], S (for setup)
         A (for Alt-n), look at the messages, and use [ESC] to
         return to the program.

    3.   Look at OTHER. Here you can change the morse code speed, and
         several other interesting parameters.

    4.   If you have EGA or VGA, try changing the monitor settings. You
         can also adjust the size of the NETWORK view portion that
         appears on each session screen.

LESSON #8: Maildrop Access

    1.   If nobody is connected to your maildrop, and you are not
         connected to other stations, use [Alt-F8] to access your
         maildrop.

    2.   Use the L)list, R)ead, K)ill etc. commands. To leave the
         maildrop, use B)ye.  Notice that text read and maildrop
         commands appear in the Previous Sessions screen.

LESSON #9: Cut/Paste text

    1.   Go to some screen (any one of Network View, Session, Previous
         Session, Maildrop). Hit [F5]. Highlight "Select Lines" and
         use the [End] key to signal the start and end of some text
         lines.

    2.   When the second [End] key is hit, you will be given options
         again. You can save text, or edit it, or quit.  Quitting
         leaves this menu, but saves the text in a CUT/PASTE clipboard.

    3.   Go to some session where you'd like to Paste the text. You
         read a message from your Maildrop or a session, and send it
         to another session.  Hit [F5], choose "Copy text to session"
         and voila, the text is "pasted" into that session. You can
         paste the same text into other session, or even into the
         maildrop.

LESSON #10: Exploration

    1.   Scan through the Help list, [F1].  You will find lots of
         interesting features there. You can turn on and off the
         Binary filter, remove and insert your own text lines using
         [Alt-L], search for text using [F9] and [Alt-F9], etc.

    2.   The release version has many more features, including
         binary file transfer, conferencing etc.

LESSON #10a: For PK232 owners

    1.   Try the other modes. Use the enclosed "TNC" files if you
         wish. Hit [F10] (with no parameters on the command line)
         and highlight some mode, then hit ENTER.

    2.   Use MYALT [F10] to check your alternate callsign for AMTOR
         modes (FEC, ARQ, SELFEC, ETC). Try ALT-S (setup) TNC files and
         edit the TNC files the way you like them for the various modes.
         You may find that simply typing the mode name is all that is
         necessary to get into a non-packet mode.

    3.   The ESC key is the transmit key down and up key. In non-packet
         modes, start typing. When you want to key down and begin
         transmitting hit the ESC key. Keep typing away. When you've
         finished typing what and want your system to unkey after sending
         the text, hit ESC again. Your text will continue being transmitted
         until the text is sent, at which time it will unkey.

         To leave ARQ AMTOR, just type AMTOR [F10]. To switch modes, type in
         the mode name, followed by [F10] or use the TNC files for that mode
         by hitting [F10] with a blank command entry line.

    4.   AMTOR ARQ: Put the SELCAL on the text entry line (e.g. WEGT)
         and hit [Ctrl-F5], the ARQ key.  To end an ARQ qso, use [Alt-F7]
         and select a "disconnect" mode.

    5.   FEC: Put the TNC in AMTOR mode, it should show Receive:Idle.
         Type in text, when you're ready to transmit, just hit [ESC].

    6.   BAUDOT: Type BAUDOT [F10]. Set the shift and baud rate. The
         TXREV function is not assigned a function key (RXREV is however)
         but you can check TXREV using  TXREV [F10] to see it's setting.
         Type in your text. When you are ready to transmit, hit [ESC].
         To unkey when the buffer empties, hit [ESC] again after the
         text begins to transmit.

         You may wish to set DIDDLE ON, so that when no characters are
         being transmitted, your TNC continues to send both mark and
         space tones, allowing other stations to "tune" in your signal.

LESSON #11: Why use Packet-GOLD?

    1.  The AEA PK232 and PK88 TNCs have a very distinctive advantage
of the other units available today. The quality and completeness of
their computer interface, or "Host Mode" is unique to the
AEA products. For example, the host mode provides information about
the number of retries, and number of unacknowledged frames, which
in our parlance are known as "pending" frames No other host
mode that we know of provides this information. The AEA Host Mode
for their multi-mode TNC also supports non-packet modes, again unique
to AEA.

    2.  While we consider the hardware to be excellent, and the
Host Mode computer interface to have no equal, we believe that our
Packet-GOLD software is the best available. We invite you to compare
Packet-GOLD 1.2 to any other program, including the new program from
AEA (a modified version of Pakterm).

    3.  Packet-GOLD was the first to offer binary file transfers,
first to support the new Maildrop features, and again remains the
best software for the users of AEA TNCs. Before you invest any time
or money in other terminal software, you must consider the advanced
features of Packet-GOLD 1.21. Ask any of our users for a comparison.


LESSON #12: Ordering Packet-GOLD

    1.   Get your VISA or MASTERCARD in front of you.

    2.   Call [phone] and ask for a copy of Packet-GOLD.

                    or

    3.   Send us a check, money order, or your VISA or MasterCard
         number to:

                  InterFlex Systems Design Corp.
                  Post Office Box 6418
                  Laguna Niguel, CA  92607-6418

         Be sure to include your name, address, and callsign.
         VISA or MasterCard orders, please include a telephone
         number to call if any problems arise.

Note: Price: $59.95 + $5 shipping. CA residents add 6.25%.
      Subject to change.


Good luck. We appreciate your business, and look forward to providing
you the best software available.