home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
tg2360.zip
/
Telgraf2.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
2000-02-19
|
43KB
|
858 lines
ΓòÉΓòÉΓòÉ 1. Quick start ΓòÉΓòÉΓòÉ
There's no way to install but the quick way! See the Installation instructions
panel for details.
ΓòÉΓòÉΓòÉ 2. General information ΓòÉΓòÉΓòÉ
Telegraf/2 is a drop-in replacement for IBM's Network Messaging.
See also:
Why "Telegraf/2"?
To install
To uninstall
Operation
Using the subject line
Compatibility with other messaging programs
Starting Telegraf/2
Who are we?
Disclaimer
The Popup Window
Version history
ΓòÉΓòÉΓòÉ 2.1. Why "Telegraf/2"? ΓòÉΓòÉΓòÉ
1. The telegraph was a significant technological advance over 2 cans and a
piece of string.
2. Telegraph has 9 letters :(.
3. We can't copyright the word "Telegraph".
4. This is exclusively an OS/2 program so "/2" was a natural. (When you're
on a good thing, stick to it!)
5. We checked on the Internet and couldn't find anyone else using
"Telegraf/2" for anything.
6. Boring names like "REXX Network Messaging" or "Replacement for IBM
Network Messaging" we can leave to the bureaucrats of IBM.
ΓòÉΓòÉΓòÉ 2.2. To install ΓòÉΓòÉΓòÉ
1. Prerequisites:
Classic REXX (default with OS/2); should also run with Object REXX
but not tested.
VROBJ.DLL version 2.1d (widely available)
RXEXTRAS.DLL (also widely available)
Warp 4 or Warp Connect English version (NLS support coming) with
NETBIOS networking installed
2. Create a home directory for Telegraf/2.
3. Unzip this archive into the home directory
4. No reboot required - just run the executable!
5. Create your own program reference object and install or shadow in your
Startup folder.
ΓòÉΓòÉΓòÉ 2.3. To uninstall ΓòÉΓòÉΓòÉ
1. Close Telegraf/2
2. Delete the Telegraf/2 home directory
3. You're done. Restart with IBM Network Messaging
4. :-( We'll be sad, but it's your choice!
ΓòÉΓòÉΓòÉ 2.4. Operation ΓòÉΓòÉΓòÉ
1. Apart from the message log file (by default
<bootdrive>:\IBMLAN\LOGS\MESSAGES.LOG), the program does not change or
create any file outside its home directory.
2. Telegraf/2 is a drop in replacement for IBM's Network Messaging and
emulates the screens and popup boxes of the original. This means minimal
relearning and maximum productivity.
3. New functions added to the original:
a. Quick Reply button on popup window - you don't have to open the main
window to reply.
b. Remembers window position and size, split bar position - "set and
forget" windows.
c. Fast type-in of destination to send
d. Default Reply To is the original Sender
e. Message management:
1. Delete original after reply
2. Delete message while viewing
3. Multiple selection for bulk deletion
4. Up/Down movement buttons in message reading window
5. Mark any message as unread
6. Distinct icons for read/unread
f. Confirmation on close - user configurable
g. Message statistics in title bar and OS/2 window list ** Registered
version only **
h. Starts requester service if necessary
i. NO POPUP OVER A DOS OR OS/2 FULL SCREEN SESSION - only a beep, and a
PM popup waiting for you when YOU choose to read it.
j. Configurable Message Log file: defaults to
<bootdrive>:\IBMLAN\LOGS\MESSAGES.LOG but you can have separate
file/s if you wish
k. Advance warning of message arrival: does not take focus immediately
- popup waits up to 2 seconds
l. If multiple popup windows on screen, newest at back
m. Hook events - run a program when certain events happen ** Registered
version only **
n. Drag a message to Desktop to save, or select Message... Save As
1. Drag&Drop to Desktop/folder:
a. If operation=Move (hold Shift), delete from container.
b. Delete temporary file (so if operation=Link ie Ctrl+Shift,
removes shadow)
2. Drag to printer illegal
3. Drag to shredder deletes message(s)
o. Subject line
p. Mini window - simply click to show the main window, or use the popup
menu to send a new message, close Telegraf/2, hide the miniwindow,
or toggle the miniwindow's title bar (if on, you can move the window
easily, but it doesn't look good).
4. Startup steps (so you don't get worried by the little windows and such):
a. The VX-REXX Console appears briefly in the window list
b. Telegraf/2 loads all necessary REXX functions and reports any errors
c. If necessary the network is started
d. Telegraf/2 then obtains message log file information.
Steps c and d generate a window list entry such as '@NET LOG
>TEMP1234.LOG'.
e. The message log is loaded and the window list entry displays the
total number of messages and the number unread (Registered version
only).
f. Without the /MIN option, the main window then opens.
5. What you won't see: Nag screens or crippleware. Everything that the
program DOES, you can see in the unregistered version (except events; but
that's advanced stuff), but you get some extra information as a byproduct
when you register.
ΓòÉΓòÉΓòÉ 2.4.1. Using the Subject line ΓòÉΓòÉΓòÉ
If the first line of the message begins Subject: (case insensitive), the 'First
Line' column in the main window has the first non-blank line after that, and
the Subject line has the subject.
When you reply, the subject is preserved - reply to message of subject Bug
report will have subject Bug report.
Compatible with IBM's Network Messaging - NetMess will merely show Subject:
<subject> as the first line.
ΓòÉΓòÉΓòÉ 2.5. Compatibility with other messaging programs ΓòÉΓòÉΓòÉ
Telegraf/2 will run when IBM's Network Messaging is running on the same
machine, but you may experience some corruption of data such as date/time sent,
from name etc but it has never been found to corrupt the message text itself.
Telegraf/2 will send messages to and receive messages from IBM's Network
Messaging (when running on separate machines) with no problems except that
Network Messaging does not recognize the Subject line (will show Subject:
<subject> as the first line).
Compatibility with WinPopup not yet tested.
ΓòÉΓòÉΓòÉ 2.6. Starting Telegraf/2 ΓòÉΓòÉΓòÉ
The following parameters are valid when starting Telegraf/2 (put these in the
Parameters box for the program object if you wish):
/MIN for minimized startup on boot
/NOMINIFMSG cancels the effect of /MIN if there are messages
/NOMINIFMSG is useful if you don't have Telegraf/2 in the Startup folder
and forget to start it. If a message arrives when Telegraf/2 is not open,
you will hear a beep and nothing else. If you then start Telegraf/2 with
both /MIN and /NOMINIFMSG, it will not minimize. However if there are no
messages, /NOMINIFMSG is ignored.
All parameters are case insensitive, order insensitive and optional.
ΓòÉΓòÉΓòÉ 2.7. Who Are We? ΓòÉΓòÉΓòÉ
Authors:
Specified by John Angelico (I'm the Dad) talldad@pobox.com.au
Co-ordinator OS/2 SIG, Melbourne PC User Group Inc., Melbourne VIC
Australia
OS/2 devotee from Ferengi days of OS/2 v2.1, now up to Warp 4 on 2
desktops and a ThinkPad 760EL
Programmed by Christopher Angelico (no. 2 son age 15)
Developed using: VX-REXX 2.1 (thanks to Watcom, but we're sorry that they
didn't survive)
Named by Michael Angelico (no 1 son age 17)
Occasionally watched by Stephen (no 5 son age 2)
(c) 1999-2000 Melbourne VIC Australia
ΓòÉΓòÉΓòÉ 2.8. Disclaimer ΓòÉΓòÉΓòÉ
This program will probably help you send messages more easily, reply more
efficiently, and make you and your co-workers happier, but DON'T BLAME US IF
THAT DOESN'T SOLVE ALL YOUR PROBLEMS. :)
As far as we know, this program won't do anything nasty to your system, but you
use it at your own risk.
ΓòÉΓòÉΓòÉ 2.9. The Popup Window ΓòÉΓòÉΓòÉ
When a message comes in (and the popup on message arrival feature is active), a
window pops up on screen (where it was when you last closed it). For normal
messages, it shows the beginning of the message, but for replies it shows 3
lines of the reply, and then the new text (handy for replies to replies to
replies, where each time several lines were typed).
Closing the window from the system menu leaves the message marked unread, but
clicking the Close button marks it read.
The Reply button takes you immediately to the Send Message window to type a
reply.
The Delete button deletes the message without requiring you to open the main
window.
If there's already one or more popup windows on screen, the new one is placed
underneath the others. This means that (for example) if three messages arrive
before you notice them (eg if you're away from the computer), the oldest
message will be on top.
ΓòÉΓòÉΓòÉ 2.10. Version history ΓòÉΓòÉΓòÉ
So far, the versions of Telegraf/2 are:
Version 1.3
(initial release; designed for small LANs)
Version 1.4
(not released to public; laid groundwork for large LAN support)
Version 2.0
(improved to support large LANs better; not released to public)
Version 2.1
(greatly improved; first large LAN version released to public)
Version 2.11
(on-line documentation added)
Version 2.2
(on-line documentation improved greatly and converted to IPF format)
Version 3.0
(made programmable)
Version 3.1
(bugs removed, groundwork laid for some version 3.2 features)
Version 3.2
(many features for the events)
Version 3.3
(minor improvements and bug fixes)
Version 3.4
(bug fixes and minor improvements to menu layout)
Version 3.5
(popup window behind other popup windows)
Version 3.6
(Read Message window bug removed; better debugging)
ΓòÉΓòÉΓòÉ 2.10.1. Version 1.3 ΓòÉΓòÉΓòÉ
Initial release to public
ΓòÉΓòÉΓòÉ 2.10.2. Version 1.4 ΓòÉΓòÉΓòÉ
Run a program on certain events
Icon changed to telegraph pole with envelope
Never released to public
ΓòÉΓòÉΓòÉ 2.10.3. Version 1.5 ΓòÉΓòÉΓòÉ
Save message as... menu item
Drag-and-Drop save message
ΓòÉΓòÉΓòÉ 2.10.4. Version 2.0 ΓòÉΓòÉΓòÉ
Multiple send
Save As... menu item (eg for import into another application)
Subject line support
Tab can be inserted into message send window (can't tab to buttons which all
have accelerators anyway)
Configurable font/color in message send window
Never released to public - beta version
ΓòÉΓòÉΓòÉ 2.10.5. Version 2.1 ΓòÉΓòÉΓòÉ
Mini window added
Drag message(s) to shredder to delete
About... dialog added
Special broadcast options - to specified domain, to users of your resources
Added Minimize button to confirm on close dialog for easy minimizing of
Telegraf (instead of closing)
ΓòÉΓòÉΓòÉ 2.10.6. Version 2.11 ΓòÉΓòÉΓòÉ
On-line documentation - press F1 for help on any object
Not released
ΓòÉΓòÉΓòÉ 2.10.7. Version 2.2 ΓòÉΓòÉΓòÉ
Configurable font/color in every window with MLE (not only message send)
On-line documentation converted to genuine IPF help - as in other OS/2 programs
Modified Popup window to show 3 lines of original text in replies (see Popup
window for details)
ΓòÉΓòÉΓòÉ 2.10.8. Version 3.0 ΓòÉΓòÉΓòÉ
Made programmable with the User Defined Commands
Tagline insertion added to Send Message window
Configurable reply header
Canned Reply feature
Undelete message
Signature insertion in message send
ΓòÉΓòÉΓòÉ 2.10.9. Version 3.1 ΓòÉΓòÉΓòÉ
Bugs removed
Groundwork laid for highly complex events (added in v3.2)
ΓòÉΓòÉΓòÉ 2.10.10. Version 3.2 ΓòÉΓòÉΓòÉ
More events
Multi-line event code
More example events
ΓòÉΓòÉΓòÉ 2.10.11. Version 3.3 ΓòÉΓòÉΓòÉ
Bugs eliminated
Stable release
ΓòÉΓòÉΓòÉ 2.10.12. Version 3.4 ΓòÉΓòÉΓòÉ
Bugs removed eg messages not marked as Read when using Up/Down in Read Message
Menu layout fixed - new 'Settings' menu with some items from 'Options';
'Message'/popup menu hides invalid/illogical menu choices depending on
context/circumstances (eg no Delete Message if no message selected)
ΓòÉΓòÉΓòÉ 2.10.13. Version 3.5 ΓòÉΓòÉΓòÉ
When a message arrives, the popup window is placed behind any other message
popup windows. This means that if three messages arrive before you notice, the
oldest message is at the top and the newest at the bottom.
Removed bug: If several messages arrived, Delete buttons on all popup windows
would delete newest message instead of current message.
ΓòÉΓòÉΓòÉ 2.10.14. Version 3.6 ΓòÉΓòÉΓòÉ
With the Read Message window, using Up, Down or Delete would disrupt the
program's record of the current message. Corrected.
Debugging improved; see Things to Try if you've got a bug.
Circular Up/Down in Read Message - if at top, Up goes to bottom, and if at
bottom, Down goes to top
ΓòÉΓòÉΓòÉ 2.11. Future enhancements ΓòÉΓòÉΓòÉ
More events - but you have to tell me what you want!
NLS support - currently works only in English, as NET.EXE output is assumed to
be in English.
Bug fixes if you inform me of bugs!
ΓòÉΓòÉΓòÉ 3. Known bugs ΓòÉΓòÉΓòÉ
Works only with the English version of OS/2. If run under non-English versions,
strange errors or incorrect operation will result. (For you programmers: the
NET commands are assumed to produce output in English. German, Danish, etc
appear different to the program and are not recognised.) NLS support is coming
in a future version.
If two messages are received from the same computer at precisely the same date
and time, the program may be confused. Also, avoid having a back quote (`) in a
computer name (I think it's an invalid character, but I'm not sure). For you
who like the technical details, messages are given unique IDs of from`date`time
where from, date, and time are the sender, date sent, and time sent
respectively.
ΓòÉΓòÉΓòÉ 4. Bug reports etc ΓòÉΓòÉΓòÉ
Bug reports, requested features, questions etc all welcome.
When you find a bug,
1. Check that it is not already in the Known Bugs section above.
2. If you have an old version, download the newest version and check the
Known Bugs section (in case it has been reported but not fixed) and
Version History (if it is fixed in a later version).
3. Note how you found it - if I know how to duplicate it, I'm half way to
removing it.
4. Email talldad@pobox.com.au with:
a. Description of bug
b. How you found it
c. Anything you tried, successfully or otherwise, to fix it yourself.
See Things to Try for ideas.
d. If possible, a variable dump.
e. Your reply-to details
f. Your Telegraf/2 version number, and registered/unregistered status
g. Other information eg version of OS/2, mixed OS/2 and Windows LAN or
pure OS/2 LAN, size of LAN etc
h. Please put 'Telegraf' in the Subject line - this email address is
used for the business as well, so there is a lot of mail.
If you have any question regarding Telegraf/2, or can think of a feature that
you'd like to see in Telegraf/2, email us at talldad@pobox.com.au with
'Telegraf' in the subject line.
ΓòÉΓòÉΓòÉ 5. Things to Try when you've got a bug ΓòÉΓòÉΓòÉ
If, when a message arrives, you hear a beep but get no popup (as if Telegraf/2
is not open), the Monitor thread may have closed for some reason. To see if
this is the case, try this:
1. From the Telegraf/2 Main Window, select the Debugging menu.
2. Select Threads from the Debugging menu.
You should get a message box with the title "Threads" and the text of the
message all numbers. If the number 2 is there, everything's normal. If 2 is
not there, the Monitor thread has gone. (Click here for sample message boxes
that you will see.)
If you find this to be true, here are some things to try:
When a message arrives (you will always hear the beep), use Message...
Reread message file and do yourself what the Monitor thread should do.
You can select Debugging... Restart Monitor thread. However, if you get a
message box when you do that, it failed.
You can close and restart Telegraf/2. This should fix the problem, unless
there's a REALLY bad problem. Check the Threads display again; if you've
got 1 and 2, it's fixed; if you've only got 1, or you got a message box
on startup, it's not. Either way, please email me as stated in Bug
Reports.
If a white box appears in the corner of the screen, with a title starting with
"VX-REXX Console", try this:
First, maximize the box by double-clicking the title bar. This will give
you more room in the box.
If the beginning of the text is something like this:
Error! Please email the logfile (TELEGRAF.ERR) to the author. The
information is duplicated here.
then you've got a REXX Syntax error inside Telegraf/2. See Handling
Syntax Errors.
If it's not, please duplicate the information in an email (you should be
able to use the OS/2 cursor movement and clipboard keys) so that I can
help you solve the problem. See Bug reports above.
ΓòÉΓòÉΓòÉ 5.1. Handling Syntax Errors ΓòÉΓòÉΓòÉ
When Telegraf/2 detects a syntax error, it will create a white box in the upper
left corner of the screen (called the Console). This will display debugging
output from the program.
There are several possible ways that an error may be reported by Telegraf/2.
Match output with these samples and take appropriate action.
1. Error! Please email the logfile (TELEGRAF.ERR) to the author. The
information is duplicated here.
Error code: 43 Routine not found
Line: 53
(the numbers 43 and 53, and the message Routine not found may be
different)
This means that Telegraf/2 could not read the REXX code out of its own
.EXE file. You will also get a message box saying "Program is unreadable"
- just click OK.
For this type of error, please email me (talldad@pobox.com.au) and
include the two numbers (43 and 53 in this example).
2. Error! Please email the logfile (TELEGRAF.ERR) to the author. The
information is duplicated here.
Error code: 43 Routine not found
Line: 53 interpret _VREEvent
Now in DEBUG mode. Press ENTER to end debug mode.
104 *-* Nop;
+++ Interactive trace. "Trace Off" to end debug, ENTER to Continue.
(again, the numbers and messages may differ)
This means that Telegraf/2 could read its own code. This type of report
is far more helpful. If you live in Australia, and especially if you live
in Melbourne (so the telephone call is cheap), the easiest solution might
be to telephone me, and I'll do a direct analysis. Otherwise, here are
some things that would help:
a. Record, as above, the two numbers.
b. Type (into the console) call dumpvars
This should produce output such as "Dumping variables to
TG2VAR01.DAT..." (the number 01 may differ)
c. Record the filename.
d. Press Enter to exit debugging mode.
e. Send an email to talldad@pobox.com.au with the information suggested
in Bug reports, plus the two numbers you recorded, and the contents
of the TG2VARnn.DAT file.
ΓòÉΓòÉΓòÉ 6. Using Events ΓòÉΓòÉΓòÉ
Telegraf/2 allows you to run a REXX program on certain events. Put simply, this
means that when (for example) a message arrives, a REXX program will be run.
You can do a custom popup, play a .WAV file (if you have multimedia support,
this is easy from REXX), or anything else you like.
Events available in Telegraf/2 as at time of writing are, by category:
General
- Telegraf/2 Opening - run just before the main window opens when
opened
- Telegraf/2 Closing - after the Confirm on Close (if active), if the
user REALLY wants to close, it does this first
- Message file changed - if a message arrives, or is deleted, marked
read/unread, or anything that changes the message file, this is
called. One parameter - 1 if it really is a new message, 0 if not.
Message sending
- Broadcast message - before a message is broadcast.
One parameter (the name of a file holding the text to be sent; you
can change this file).
- Before send message - before a message is sent (with Send or Send
Multiple, but not with Broadcast).
Similar to Broadcast above.
- After send message - after a message is sent.
One parameter - Boolean value for success/failure. Executed once for
each target on Send Multiple.
- Double-click - when the text window (Multi-Line Entryfield, or MLE)
is double-clicked.
Read Message
- Double-click - when the MLE is double-clicked.
New Message popup
- Double-click - when the MLE is double-clicked.
Events are enabled only when you register Telegraf/2. For further details, see
How to Register.
ΓòÉΓòÉΓòÉ 7. How to Register ΓòÉΓòÉΓòÉ
To find out why you want to register, see Benefits of Registering.
1. Licence Cost:
for home use (up to 4 machines) - $A25 (equal to approx $US16 or
Euro15 as at late Apr 1999)
for corporate use (5 machines and above) - $A15 per machine
all charges will be made in $A
Upgrade from previous version (eg 1.5 to 2.1, but not 1.3 to 1.5 -
that's free) costs:
- for home use - $A15
- for corporate use - $A10 per machine
2. Email to talldad@pobox.com.au with the following information:
a. Your name
b. Your email address
c. Number of machines
d. Payment details - Visa, MasterCard or Australian/New Zealand
Bankcard
(if you prefer not to send details across the 'net, ask us for our
fax number)
e. Your registration name - please be precise! May be a corporate name
for corporate use.
3. We will email you with a registration code (usually within 24-48 hours)
plus the latest version.
4. Enter your selected name and the code into Telegraf/2:
a. Open Telegraf/2 if necessary
b. Select Options... Register from the menu bar
c. Enter your registration name and the code we supplied
d. Press OK. If the code does not match, check carefully and re-enter.
5. If you have any problems, which we consider unlikely (of course<g>),
email us again.
6. Enjoy!
ΓòÉΓòÉΓòÉ 8. Benefits of Registering ΓòÉΓòÉΓòÉ
1. Keep shareware alive!
2. Feel good about doing the right thing
3. Get the latest version
4. Help us to continue development
5. Programmers have to eat, too!
6. Get the message stats in the OS/2 Window List and title bar of the main
window
7. Enable the events
8. Get free support
9. Free upgrades up to the next major version (register v2.9, but not 3.0,
with the same code as v2.0)
Now, you just need to see How to Register (you do want all that, don't you?).
ΓòÉΓòÉΓòÉ 9. Tips and Tricks ΓòÉΓòÉΓòÉ
For those who don't believe in Murphy's Law, here are some tips and tricks:
To restore messages deleted with Delete All messages:
This works only in the registered version of Telegraf/2.
From the Telegraf/2 Main Window, select User Commands... Configure.
In the Caption field, type anything at all, meaningful or otherwise, but
just don't leave it blank (and if you have two the same, you might be
confused).
In the Code field, type 'REXX MESSAGES.0=3' (without the quotes),
replacing 3 with the number of messages that you want to restore.
Click Add.
Click Save to save what you did, and Close to close the configuration
window.
Select the User Commands menu, and from that menu the item you just
created. The first 3 (or however many you chose to restore) messages
should be restored.
Don't try this if you used Delete or Delete those Read to delete the
messages. Use the Undelete command for those.
And remember, the author is not responsible for anything you do with his
program.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
To make a variable dump (a very useful debugging tool):
1. Go to the Telegraf/2 main window.
2. Open the Debugging menu
3. Select Variable Dump
4. A file dialog will come up. Select a file to dump the variables into (it
will be overwritten).
5. Attach this file to the bug report email.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Ordinary:
While sending:
If Monitor thread gone:
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Murphy was an optimist.
Murphy's Law states that "Anything that can go wrong, will go wrong."
For example:
The other queue will always move faster.
Any failed appliance, when demonstrated for the repairman, will work perfectly.
The probability that a piece of buttered bread will fall buttered side down is
proportional to the cost of the carpet.
A $1000 TV set will protect a 5c fuse by blowing first.
And many more.
Silverman's law says that "If Murphy's Law can go wrong, it will." but that's a
different story!