| -----------------------------------------------------
TeamLinks Mail for Windows, V3.0
-----------------------------------------------------
We are pleased to announce the availability of the EFT1
kit for TeamLinks Mail for Windows, V3.0. This version
of TeamLinks adds support for the Microsoft Exchange
Server. If you're going to use TeamLinks with Exchange,
you need to be sure to have the Exchange client working
first. Please review the README.TXT that's in the kit
before installing it.
You may copy the kit from:
XANADU::TLPUBLIC:[OFFICE_PUBLIC.KITS.T30_EFT1]LICENSE.DOC
TLMKIT.EXE
\\xanadu\tlpublic\kits\t30_eft1 would be another way to
reference that same directory. You could use FTP and CD
to the VMS directory spec given above as yet another way
to get at the kit.
Note 11.2 in this conference details how to enter bugs
into our Problem Trackg and Reporting System. You can
also ask questions in this conference.
Thanks.
-------------------------------------------------------------------------------
TEAMLINKS FOR WINDOWS VERSION 3.0 FIELD TEST 1
RELEASE NOTES
March, 1997
This document provides information on late technical
changes, restrictions, and corrections not covered
elsewhere in the TeamLinks(TM) for Windows� documentation.
Be sure to read it before using TeamLinks.
Digital Equipment Corporation
Proprietary Information
Furnished for Field Test Purposes Only
The information contained herein is furnished in
confidence and is subject to the terms and conditions of a
license agreement for field testing Digital Equipment
Corporation software.
CONTENTS
1. NEW NOTES FOR TEAMLINKS T3.0 FIELD TEST 1
1.1 BEFORE YOU INSTALL TEAMLINKS T3.0
1.1.1 Prerequisite Microsoft Exchange Software
1.1.2 Microsoft Exchange Server Support Incompatible
with Simple MAPI
1.1.3 Updating the Path Manually on Microsoft Windows NT
Systems
1.1.4 Information for System Administrators
1.2 FEATURES NOT YET IMPLEMENTED
1.2.1 Features Not Implemented When Microsoft Exchange
Server is Primary
1.2.2 Features Not Available for Any Server
1.3 Microsoft Exchange Server Restrictions
1.4 Problems Related to Microsoft Exchange Servers
1.4.1 Changing to a Different Microsoft Exchange
Profile
1.4.2 TeamLinks Cannot Read Microsoft Exchange
Notifications
1.4.3 Sending a Text Copy of a Rich Text Message
1.4.4 Cannot Use TeamLinks Setup Mail Profile While
Connected to a Microsoft Exchange Server
1.4.5 BCC Messages Sent from an Exchange Server Show
Incorrect Information
1.4.6 Application Integration Problems
1.4.7 WordPerfect V6.1 Application Integration Problem
1.4.8 System Default Address Validation Setting
2. ASSOCIATED DOCUMENTS
2.1 Information about New Features
2.2 Error Information
2.3 Application Integration Information
2.4 TeamLinks for Windows Multimedia Overview
3. NOTES CARRIED OVER FROM TEAMLINKS VERSION 2.7
3.1 Problems Related to Microsoft Windows 95
3.1.1 Simple MAPI Support Incompatible with Microsoft
Exchange
3.1.2 Simple MAPI Support with Microsoft Office 95
Applications
3.1.3 Cannot Export to Existing File
3.1.4 Password List Problem with Microsoft Windows 95
Service Pack 1
3.1.5 TeamLinks Remote Communications Port Activity
Lights
3.2 Problems Related to Microsoft Windows NT
3.2.1 Print Setup Dialog Settings Not Preserved
3.2.2 TeamLinks Message Notification Tries to Run Again
3.3 TeamLinks Internet Mail Problems
3.3.1 Error Sending with Internet Mail Using PATHWORKS
V5.0
3.3.2 Problem Creating an Internet File Cabinet Using a
Network Path
3.4 Problems Working with MailWorks for UNIX
3.4.1 Do Not MIME Encode or uuencode Messages with
Multiple Attachments
3.4.2 Do Not Send a Text Copy of a Rich Text Message
3.4.3 Changing the Cover Memo Style of a Draft Message
3.4.4 Miscellaneous Problems
3.5 Problems That Are Independent of Operating System
3.5.1 Messages Received with Incorrect Time Stamp
3.5.2 ALL-IN-1 Connects Leaving Links Behind
3.5.3 TeamLinks Customizations Using the TLEXTERN
Interface Do Not Work with RTF Messages
3.5.4 Problem Setting the Local File Cabinet
Reservation Identity
3.5.5 Distribution Lists Stored in MailWorks for
OpenVMS Server Drawer
3.5.6 Text Attachments with Long Lines Are Truncated
3.5.7 TeamLinks Hangs when FIX1MB Is Installed
3.6 RESTRICTIONS
3.6.1 Auto-forward and Redirection Features in ALL-IN-1
3.6.2 Moving TeamRoute Masters Across Mail Resources
3.7 GENERAL ISSUES
3.7.1 TeamRoute and Template Designer Issues
4. CONVERTERS AND VIEWERS
5. TRADEMARKS
___________________________________________________
1. NEW NOTES FOR TEAMLINKS T3.0 FIELD TEST 1
1.1 BEFORE YOU INSTALL TEAMLINKS T3.0
This section contains information you should know before
you install TeamLinks Version 3.0 Field Test 1, especially
if you intend to install support for a Microsoft Exchange
Server file cabinet.
1.1.1 Prerequisite Microsoft Exchange Software
If you intend to install support for a Microsoft Exchange
Server file cabinet with TeamLinks T3.0 Field Test 1, you
must have a functioning Microsoft Exchange Client running
on your PC, one that can connect to the Microsoft Exchange
Server.
The Microsoft Exchange Server must be running Microsoft
Exchange Server Version 4.
The TeamLinks user's PC must be running Microsoft Exchange
Client Version 4 plus Microsoft Exchange Client Service
Pack 2.
The Microsoft Exchange Client software must be operating
correctly on each user's PC. To test whether the
Microsoft Exchange Client software is set up to access a
Microsoft Exchange Server:
1. On your PC, click the right mouse button on the
Microsoft Exchange Inbox icon. The Properties dialog
for your Microsoft Exchange profile appears.
2. In the Services tab, make sure that Microsoft Exchange
Server is shown in the list of information services
that are set up for your profile.
1.1.2 Microsoft Exchange Server Support Incompatible with
Simple MAPI
In TeamLinks T3.0 Field Test 1, you cannot have support
for a Microsoft Exchange Server file cabinet and still
have TeamLinks Simple MAPI support.
If you are installing TeamLinks on a system where
TeamLinks Simple MAPI has been installed previously, and
you now want to install Microsoft Exchange Server support,
follow these steps:
1. Reinstall the Microsoft Exchange Client software on your
PC. This will install the Microsoft Simple MAPI DLL files.
2. Install TeamLinks on your PC. During the TeamLinks
installation, when you see the screen titled "Installation
Options", select the Customize Selected Option check box.
3. Click the appropriate Installation Option button:
Complete, Typical, or Minimum. The Customized
Installation dialog appears.
4. Make sure the TeamLinks Simple MAPI Integration option is
not selected. If it is selected, click the check box to
clear it.
5. Click the Install button and proceed with the rest of the
TeamLinks installation.
If you are installing TeamLinks on a system where TeamLinks
Simple MAPI has not been installed previously, follow steps
2 through 5 above to make sure TeamLinks Simple MAPI support
does not get installed.
1.1.3 Updating the Path Manually on Microsoft Windows NT
Systems
If you are installing TeamLinks on a PC running Microsoft
Windows NT, you must update your path to include the
directory where TeamLinks is installed. Follow these steps:
1. Run the Windows NT Control Panel application. From the
Start menu, choose Control Panel from the Settings menu.
2. Double click the System icon in the Control Panel group.
3. In the System dialog, click the Environment tab.
4. Position the cursor within the User Variables list and
double click.
5. Click on the Variables field and type the variable name
Path.
6. Click on the Value field and type the directory where
TeamLinks is installed (for example, C:\Teamlink).
7. Click the Set button.
8. Click the Apply button.
9. Click the OK button.
1.1.4 Information for System Administrators
The TeamLinks for Windows Client Administration Guide is
now available in online format only. This guide contains
important information about customizing the TeamLinks
installation, including suggestions for adding Microsoft
Exchange Server support.
To view the TeamLinks for Windows Client Administration
Guide, run the CDHELP.EXE program in the HELP directory on
the CD-ROM. (If you have the CD-ROM AutoPlay feature
enabled, click the TeamLinks Information button in the
window that appears when you insert the CD-ROM into the
drive.)
To view the guide after you install TeamLinks, click the
TeamLinks Client Admin Guide icon in your TeamLinks folder
(Windows 95 or Windows NT V4.0) or double-click the
TeamLinks Client Admin Guide icon in your TeamLinks
program group (Windows 3.x or Windows NT V3.51).
1.2 FEATURES NOT YET IMPLEMENTED
This section lists features that are not available in
TeamLinks for Windows T3.0 Field Test 1.
1.2.1 Features Not Implemented When Microsoft Exchange
Server is Primary
- New mail notification
- Information Manager scripts
- In the Directory Services dialog, the Narrow Search
Scope is identical to the Wide Search Scope. This is
also the case in the TeamLinks Setup Mail Profile, in
the Addressing section.
- Viewing and processing Microsoft Schedule+ documents
- Auto reply
1.2.2 Features Not Available for Any Server
- In the Read Message window Options menu, the Font
command and the Rewrap Text Attachment command are
not enabled
1.3 Microsoft Exchange Server Restrictions
TeamLinks does not provide a user interface to all of the
Microsoft Exchange functionality. In most cases, you can
work around the problem by using the Microsoft Exchange
Client to perform these tasks.
You cannot perform the following tasks from TeamLinks:
- Create a drawer
Workaround: Use the Microsoft Exchange Client to add
another Personal Folder resource. TeamLinks will
display this new Personal Folder as a drawer.
- View nested folders
Workaround: Use the Microsoft Exchange Client to move
the nested folder to be a top level folder. Then
TeamLinks can view it.
- View nested folders in the All Public Folders drawer,
or add folders in the All Public Folders drawer to
your Favorites drawer
Workaround: Use the Microsoft Exchange Client to drag a
folder from the All Public Folders folder into your
Favorites folder. TeamLinks will display this folder in
your Favorites drawer.
1.4 Problems Related to Microsoft Exchange Servers
1.4.1 Changing to a Different Microsoft Exchange Profile
TeamLinks supports the capability to change to a different
Microsoft Exchange profile from within TeamLinks. However,
the Choose Profile dialog always displays your default
Microsoft Exchange profile name, rather than the profile
that was last used.
1.4.2 TeamLinks Cannot Read Microsoft Exchange
Notifications
TeamLinks cannot read Microsoft Exchange notification
messages (for example, non-delivery notifications) that
appear in your Inbox. When you try to read a
notification, you see the following message:
"Object is no longer available. The object was previously
moved or deleted and is no longer in the current drawer or
folder."
1.4.3 Sending a Text Copy of a Rich Text Message
You may experience problems if you use the Send with
Options feature to also send a text copy of a rich text
message.
1.4.4 Cannot Use TeamLinks Setup Mail Profile While
Connected to a Microsoft Exchange Server
On systems running Microsoft Windows for Workgroups
Version 3.11, you cannot connect to a Microsoft Exchange
Server file cabinet from Information Manager and access
the Mail Profile in TeamLinks Setup at the same time.
When you attempt the second connection, you see the
following Microsoft Exchange Server message:
"Your Microsoft Exchange Server is unavailable....
Network Problems are preventing connection to the
Microsoft Exchange Server computer. Contact your system
administrator if this condition persists."
1.4.5 BCC Messages Sent from an Exchange Server Show
Incorrect Information
Sending a mail message to a BCC recipient does not work
correctly when a Microsoft Exchange Server is your primary
file cabinet. BCC recipients will be able to view the To
and CC recipient lists.
1.4.6 Application Integration Problems
Any 32-bit application (for example, a Microsoft Office 95
or Microsoft Office 97 application) that uses any form of
TeamLinks file cabinet integration will encounter a general
file cabinet error when it accesses a TeamLinks file
cabinet containing a Microsoft Exchange Server drawer. The
error results in a File Open dialog that does not show any
drawer names.
Applications using ODMA integration (for example, Microsoft
Office 97 or WordPro 97) can work around this problem by
doing the following:
1. Open OFFICE.INI and locate the [ODMA] section. If the
file does not have an [ODMA] section, create a new
[ODMA] section at the end.
2. Set the value of the OpenMode setting to 0 (OpenMode=0).
If the file does not have this setting, add it to the
[ODMA] section.
3. Save the changes and exit OFFICE.INI.
4. Exit and restart TeamLinks.
The integrated application will still encounter the error,
but the resulting File Open dialog is usable. It simply
excludes the Microsoft Exchange Server drawers from the
list.
For applications using TeamLinks built-in integration (for
example, Microsoft Office 95), you can work around this
problem by using the File Cabinets section of TeamLinks
Setup to remove the Microsoft Exchange Server file cabinet.
The application integration will then work correctly.
1.4.7 WordPerfect V6.1 Application Integration Problem
Any Corel WordPerfect V6.1 application that is integrated
with TeamLinks using ODMA cannot open or save documents to
a Microsoft Exchange Server drawer. WordPerfect will save
the document, but then it will hang. Later, if you try to
open the document, WordPerfect will hang again.
1.4.8 System Default Address Validation Setting
When your default address validation setting is set to
System Default (either through TeamLinks Setup Mail
Profile - Addressing, or through the right mouse button
popup menu in the Create Message window), TeamLinks
interprets the address as a first name. For example,
assume you are trying to locate the address for George
Washington. If you type Washington into the Create Message
window's addressing field, TeamLinks searches for all users
with the first name Washington. The user George Washington
would not be found.
To work around this problem, change the address validation
setting to Mail User List. Then TeamLinks will interpret
addresses correctly.
2. ASSOCIATED DOCUMENTS
In addition to the TeamLinks for Windows documentation and
extensive online help, you can find additional TeamLinks
documentation and troubleshooting information in the files
described in this section.
2.1 Information about New Features
To see a complete list of new and changed features in
TeamLinks, do one of the following:
- If you are installing from the CD-ROM, run the CDHELP.EXE
program in the HELP directory on the CD-ROM. (If you have
the CD-ROM AutoPlay feature enabled, click the TeamLinks
Information button in the window that appears when you
insert the CD-ROM into the drive.) When the TeamLinks
Information graphic appears, choose the New Features
button.
- If you are installing from diskettes, after you install
TeamLinks, click the TeamLinks Information icon in your
TeamLinks folder (Windows 95 or Windows NT V4.0) or
double-click the TeamLinks Information icon in your
TeamLinks program group (Windows 3.x or Windows NT V3,51).
When the TeamLinks Information graphic appears, choose
the New Features button.
2.2 Error Information
The file TRBLSHOT.WRI is copied to the TeamLinks directory
(C:\TEAMLINK by default) during installation and has lists
of error codes with brief explanations.
(You can view or print .WRI files by using the Windows
Write application that comes with Microsoft Windows
Version 3.1 or the WordPad application that comes with
Windows 95.)
2.3 Application Integration Information
The file TL_INT.TXT is copied to the TeamLinks directory
(C:\TEAMLINK by default) during installation and contains
useful information about integrating TeamLinks with other
Windows applications. In particular, you should look at
this document if you will be using WordPerfect.
On Windows V3.1 systems, the file TL_INT.TXT is too large
to be viewed in Notepad. Instead, use the Windows Write
application to open the file.
2.4 TeamLinks for Windows Multimedia Overview
A Multimedia Overview is included on the TeamLinks for
Windows CD-ROM. For information about viewing the
Overview, see the TLWINOVR.TXT file in the OVERVIEW
directory on the CD-ROM.
Note: The Multimedia Overview has not yet been updated
from TeamLinks Version 2.7. It will be updated for
TeamLinks T3.0 Field Test 2.
3. NOTES CARRIED OVER FROM TEAMLINKS VERSION 2.7
3.1 Problems Related to Microsoft Windows 95
3.1.1 Simple MAPI Support Incompatible with Microsoft
Exchange
If you install TeamLinks Simple MAPI support, TeamLinks
puts its version of MAPI32.DLL in the Windows system
directory and renames any existing MAPI32.DLL to
MAPI32.BAK. Microsoft Exchange on Windows 95 does not
work properly with the TeamLinks version of MAPI32.DLL.
If you want to use Microsoft Exchange, you must delete the
MAPI32.DLL that TeamLinks installed and rename MAPI32.BAK
to MAPI32.DLL.
To check which version of MAPI32.DLL you have, use the
Explorer interface in Windows 95 to show a directory of
the Windows system directory, right click on the
MAPI32.DLL (or MAPI32.BAK) file, and select the Properties
menu option. If you then select the Version tab, you see
the name of the company that produced the file.
Alternatively, you can reinstall the appropriate version
of the Microsoft Exchange Client software on your PC.
This will install the correct MAPI32.DLL file.
3.1.2 Simple MAPI Support with Microsoft Office 95
Applications
If you install TeamLinks Simple MAPI support, TeamLinks
will be used for mail enabled applications.
To have TeamLinks Simple MAPI work with Microsoft Office
95 applications, you may need to reinstall Office 95 after
you have installed TeamLinks.
3.1.3 Cannot Export to Existing File
It is not possible to export a message to an existing file
under Windows 95. This is a known Windows 95 problem. If
you try to do so, you see the following message:
"This path does not exist. Make sure that you have
specified the correct path".
3.1.4 Password List Problem with Microsoft Windows 95
Service Pack
Windows 95 Service Pack 1 is an update that corrects some
problems in Windows 95. It changes the Windows Password
List to use a better encryption algorithm, thus making it
much more secure.
TeamLinks can save passwords in the Windows Password List.
After the Windows 95 Service Pack 1 has been installed,
TeamLinks can experience problems either clearing one
password or a group of passwords from the Windows Password
List. This is especially possible if there were TeamLinks
passwords in the Password List at the time the Windows 95
Service Pack was installed.
The workaround for this problem is to delete your .PWL
file from the Windows directory. The next time you log
onto Windows 95, the PWL file will be recreated by
Windows.
After the PWL file has been recreated, TeamLinks should
not have any problems clearing passwords.
3.1.5 TeamLinks Remote Communications Port Activity Lights
The TeamLinks Remote communications port activity lights
do not work when using Microsoft Windows 95 or when using
IBM OS/2 Version 3 (Warp). They can be disabled via the
TeamLinks Remote Preferences dialog box. To display this
dialog box, choose Preferences from the Options menu.
Depending on the communications port driver installed on
your system, the lights may work erratically. Contact
your driver vendor for an updated driver.
3.2 Problems Related to Microsoft Windows NT
3.2.1 Print Setup Dialog Settings Not Preserved
On Microsoft Windows NT, changes you make in the TeamLinks
Print Setup dialog (choose Print Setup from the File menu)
are not used.
There are two workarounds to this problem:
- Change the default print settings through Windows NT.
TeamLinks will honor those settings.
- Choose Print from the File menu, then click the Setup
button. Changes you make in that Print Setup dialog will
be honored for the current print job.
3.2.2 TeamLinks Message Notification Tries to Run Again
When using TeamLinks with Microsoft Windows NT, the
TeamLinks Message Notification Application tries to run
again when you have the following the New Message
Notification options set:
Enable new message notification
Enable on each connection to mail service
Under these conditions, when you exit TeamLinks, the
TeamLinks Message Notification is still running minimized.
When you restart TeamLinks, the following message appears:
TeamLinks Message Notification
A network error has occurred.
Could not listen for incoming connections.
This message is caused by TeamLinks Message Notification
trying to start a second time.
The workaround is to ignore the message and click OK. The
first instance of TeamLinks Message Notification still
works correctly.
3.3 TeamLinks Internet Mail Problems
3.3.1 Error Sending with Internet Mail Using PATHWORKS
V5.0
If you are using PATHWORKS Version 5.0 and you send
Internet Mail, you may receive an error saying that there
was a problem and to check CFCDEBUG.LOG for more details.
If you see the following lines in CFCDEBUG.LOG:
CFCIMAIL: Send error [10040] Message too longERROR 960: A
fatal error was returned by the socket.
then you can fix the problem by adding the following line
to the [POP3] section of your OFFICE.INI file:
sendbuf=1000
This problem does not occur if you are using PATHWORKS
Version 5.1.
3.3.2 Problem Creating an Internet File Cabinet Using a
Network Path
When creating an Internet file cabinet, if the path used
is on a network drive and it is the same path already used
to create an Internet file cabinet on a different PC, the
error "Invalid Drawer identifier" appears.
TeamLinks does create the file cabinet and the drawer
appears in the Information Manager list of file cabinets.
You can open the drawer and access its contents, but you
cannot use it to send or receive mail. If you attempt to
send mail, a general protection fault occurs. If you
attempt to retrieve mail, the mail is copied to your local
system, but it cannot be placed in the Inbox.
To work around this problem, you can modify the OFFICE.INI
file on the system where the failures are occurring. In
the file cabinet section for the file cabinet with
problems (file cabinet sections begin with [file cabinet
name]) add the following lines:
$VNewMF=Inbox
$VRefiF=Read
$VDrafF=Drafts
$VSelfCF=Outbox
The strings Inbox, Read, Drafts, and Outbox are the
default values. If the user has different values for
these special folders, they should be substituted for the
defaults.
3.4 Problems Working with MailWorks for UNIX
The problems listed in this section are related to the
interoperability of TeamLinks with the MailWorks for UNIX
server.
3.4.1 Do Not MIME Encode or uuencode Messages with
Multiple Attachments
Do not use the TeamLinks feature (which is found on the
Send with Options dialog) to MIME encode or uuencode
messages that contain more than one attachment. MailWorks
may tag the attachments improperly, or in some cases, lose
the attachments.
Because the MailWorks for UNIX server Version 2.0 supports
both MIME encoding and uuencoding, you can work around the
problem by allowing the MailWorks server to perform the
encoding. Note that the MailWorks server only encodes
messages for recipients with SMTP addresses.
3.4.2 Do Not Send a Text Copy of a Rich Text Message
Do not use the feature (which can be found on the Send
with Options dialog) that lets you send a text copy of a
rich text message. Using this feature may cause MailWorks
for UNIX to lose attachments.
3.4.3 Changing the Cover Memo Style of a Draft Message
Do not change the cover memo style of a draft message that
has been saved in a MailWorks for UNIX server drawer.
When you reopen a saved draft message in the Create
Message window, you should not change the cover memo style
from plain text to rich text or vice versa. This may
result in MailWorks for UNIX sending the RTF-encoded form
of the text rather than the properly formatted text.
To work around this problem, use the Save As command to
save the message as a new draft message, and then delete
the old draft message.
3.4.4 Miscellaneous Problems
- You cannot use the Attributes dialog box to change a
format attribute. MailWorks for UNIX ignores the change.
- MailWorks for UNIX does not include the phone and
location information with messages sent from TeamLinks
- When you perform a search to find unsent messages,
MailWorks for UNIX returns a list of the sent messages
instead.
- When you edit an object that is stored in a MailWorks
for UNIX drawer, the date and time of modification does
not change.
3.5 Problems That Are Independent of Operating System
3.5.1 Messages Received with Incorrect Time Stamp
If you are using TeamLinks with Microsoft Windows V3.1 or
Microsoft Windows NT, messages sent from other time zones
may display an incorrect time in the message header. To
fix this problem, add the following line to your
AUTOEXEC.BAT file:
SET TZ=<variable>
where <variable> takes the following form:
1. A 3 character representation of the standard time zone
name (for example, EST for Eastern Standard Time).
2. A number representing the difference between the
standard time zone and GMT (Greenwich Mean Time),
measured in hours West of GMT. A plus or minus sign is
optional.
3. A 3 character representation of the daylight savings
time zone name (for example, EDT for Eastern Daylight
Time). The second time zone name can be omitted if no
daylight savings adjustment is used.
Examples:
Eastern Time Zone in the USA: SET TZ=EST5EDT
United Kingdom: SET TZ=GMT0BST
3.5.2 ALL-IN-1 Connects Leaving Links Behind
With PATHWORKS for Windows Version 1.0, every
connect/disconnect to the ALL-IN-1 file cabinet server
leaves behind an idle link to port 73. The solution is to
upgrade to Version 1.0A or later of PATHWORKS for Windows.
3.5.3 TeamLinks Customizations Using the TLEXTERN
Interface Do Not Work with RTF Messages
Any DLL customization written with the TLEXTERN interface
that operates on the text of a created message cannot save
the message afterward if the user has selected a Rich Text
(RTF) style as the cover memo style of the message.
DLL customizations still work with messages created using
a text cover memo style.
3.5.4 Problem Setting the Local File Cabinet Reservation
Identity
When you edit a document in a local file cabinet before
using a primary mail server, you may see the following
error:
"The document could not be reserved, so you cannot make
updates to it.
No reservation identity defined for local cabinet.
Local file cabinet reservation support requires an
identifier for the reservation holder.
Connect to the primary file cabinet to establish a
reservation identity."
There are these workarounds for the problem:
- When ALL-IN-1, MailWorks, or Microsoft Exchange Server
is the primary mail server, connect to the mail server.
The information for the reservation identifier is then
available.
- When Internet Mail is the primary mail server, all that
is needed is for the user to send a message. Once a
send has been completed, the information for reservation
identifier is then available.
- Alternatively, when Internet Mail is the primary mail
server, the user can fill in the server and return
address information for the Internet Mail file cabinet
in the File Cabinets section of TeamLinks Setup.
3.5.5 Distribution Lists Stored in MailWorks for OpenVMS
Server Drawer
If you use the MailWorks for OpenVMS server and you store
your TeamLinks distribution lists in a MailWorks server
drawer, do not compress the drawer (which can be done
using the MailWorks video terminal client). If you
compress the drawer, the document IDs of the distribution
lists will change, and, as a result, TeamLinks will not be
able to find the distribution lists.
3.5.6 Text Attachments with Long Lines Are Truncated
Text attachments containing lines longer than 1024
characters may be truncated if sent through Message
Router.
3.5.7 TeamLinks Hangs when FIX1MB Is Installed
Starting TeamLinks when the FIX1MB utility is running may
cause TeamLinks to hang. This utility should not be run
until after TeamLinks has been started.
3.6 RESTRICTIONS
3.6.1 Auto-forward and Redirection Features in ALL-IN-1
TeamLinks does not provide a user interface to all of the
ALL-IN-1 Server functionality, particularly selective Auto-
forward and the option to retain a copy of the forwarded
message in the file cabinet. A user with access to a VT
client could choose to set these options from the VT, in
which case they could only be cleared by the VT client CF
(Cancel auto forward). Canceling Auto-forward from
TeamLinks would not clear these options, so any further
use of Auto-forward from TeamLinks would honor these
settings.
Further, if the TeamLinks user uses the VT Client to set
Redirection, any usage of Auto-forward from the TeamLinks
Client will be ignored. This is because Redirection
happens in the MTA (Message Transfer Agent), independently
of the server, and is unaffected by Auto-forward. To
enable usage of Auto-forward from TeamLinks in this case,
the user must first cancel redirection from the VT Client
(CF).
3.6.2 Moving TeamRoute Masters Across Mail Resources
Moving completed TeamRoute masters across mail resources
(for example, from an ALL-IN-1 file cabinet to a MailWorks
file cabinet) is not supported and can lead to
unpredictable behavior.
3.7 GENERAL ISSUES
3.7.1 TeamRoute and Template Designer Issues
Although it appears that you can send TeamRoute templates
from your file cabinet to other users simply by attaching
a template to a new mail message, the template will not be
recognized as a template by the receiver. The preferred
method for distributing templates is documented in the
TeamLinks Template designer online help.
Under some circumstances, TeamRoute templates that are
disabled can be saved in the TeamLinks File Cabinet.
Disabled templates are not usable by the TeamRoute client.
In order to enable the template, do the following:
1. Load the disabled template into the TeamRoute Template
Designer and choose the Verify command from the File
menu.
2. If any items are marked NO, fix them (see the online
help for the Verify Template dialog box). Then choose
Save from the File menu.
3. If all items are marked YES, edit the Template Type
field by deleting the last character and adding it
again. Then choose Save from the File menu.
4. CONVERTERS AND VIEWERS
TeamLinks includes many converters and viewers. The
viewers are designed to present a reasonable facsimile of
the document. It is expected that you will see some
differences between the viewer and the application.
Complicated document features such as flowing text around
a rectangle or tables that span pages can exceed the
design of a viewer. In this case, you should launch the
application to see all the features of the document.
Digital Compound Document Architecture (CDA) converters
are not included with TeamLinks. However, if CDA
converters are on your system, TeamLinks will work with
them. The TeamLinks installation procedure detects the
presence of CDA converter files and updates the internal
TeamLinks tables to include the CDA converters in the
lists of formats that are presented to users.
If you add or delete CDA converters, you should reinstall
TeamLinks (choosing a customized installation) so that the
internal table of converters is regenerated.
This is the complete list of converters and viewers in
TeamLinks Version 3.0:
Key:
* These formats are Read-only
# These formats are Output-only
Ami Professional 1.x, 2.0, 3.0
Ami Professional Graphics (SDW)
ASCII (plain, standard, smart, stripped)
ASCII (comma delimited)
Autocad (DXF, *DXB))
CEO Write
*CompuServe GIF
CGM (Computer Graphics Metafile)
*Corel Draw Preview
CTOS DEF
dBase III, III+, IV (1.0) for databases
DCA/FFT (Final Form Text)
DCA/RFT (Revisable Form Text)
Digital DX
Digital WPS-PLUS
DisplayWrite 2, 3, 4, 5, 5.2
DEF/Document Designer
EBCDIC
Enable (1.1, 2.0, 2.15)
EPS Preview, Bitmap Level #1, #2
FAX (see TIFF)
FoxPro for Windows 2.5
FrameMaker for Windows, Unix, Mac, 3.0, 4.0, 5.0
Framework III 1.0, 1.1, IV
GIF
HP AdvanceWrite Plus 1.0, 2.0
#HP PCL
HP Graphics Language (HPGL)
HTML Level 1, 2, 3
IBM Writing Assistant 1.0
IGES
Interleaf Graphics
Interleaf Publisher 1.1 (ASCII markup)
Interleaf Publisher 5.2
JPEG
Legacy 1.x, 2.0
Lotus 1-2-3 1A, 2.0, 2.1, 3.0, 4.0, 5.0
Lotus 1-2-3 for Windows
Lotus AmiPro 1.1, 1.2, 2.0, 3.0
Lotus AmiPro SDW (graphics)
Lotus Freelance (PRE)
Lotus Manuscript 2.0, 2.1
Lotus PIC
Macintosh PICT
MacPaint
MacWrite 4.5 - 5.0
MacWrite II 1.0, 1.1
MacWrite PRO
MacWord 3.0, 4.0, 5.0
Mass-11 Classic 8.x-9.0
*Micrographx
Microsoft Access 2.0
Microsoft Excel for Windows 2.1, 3, 4, 5
Microsoft Excel for Macintosh 3.0, 4.0
Microsoft FoxPro for Windows 2.5
Microsoft Paint (MSP)
*Microsoft PowerPoint 4.x (Version 4 only)
Microsoft RTF
Microsoft Word 3, 3.1, 4, 5, 5.5, 6.0
Microsoft Word for Windows 1.x, 2.0, 6.0
Microsoft Word for Macintosh 3, 4, 5.0-1, #6.0
Microsoft Word for Windows 6.0 Mail Merge
*Microsoft Word Graphics Object
*Microsoft Works (DOS 2.0, Win 3.0)
Microsoft Windows Write 3.x
MultiMate 3.3, 4
MultiMate Advantage I, II
Navy DIF
OfficeWriter 4.0, 5.0, 6.0 - 6.2
onGO
OfficePower 6 7
OS/2 Bitmap,
*OS/2 icon resource
*Paradox 3.5, 4.0
PC Paintbrush PCX, *DCX
PeachText 5000 2.12
PFS:First Choice 1.0, 2.0, 3.0
PFS:WRITE Version C
Portable Network Graphics (PNG)
#PostScript
Professional Write 1, 2.0 - 2.2, PLUS
Quattro Pro for Windows 1.0 5.0
Q&A 3.0, 4.0
Q&A Write 1.x
Rapid File 1.0, 1.2
RGIP
Samna Word IV, IV Plus, 1.0, 2.0
Signature 1.x
Sun Raster (RAS)
TIFF (Tagged Image File Format)
Total Word 1.2, 1.3
Uniplex WP (V7)
Volkswriter 3, 4
Volkswriter Deluxe 2.2, 3 V1, 4
Wang PC, Version 3
Wang SWP
Wang WP Plus
Windows Bitmap (BMP, *DIB, RLE)
Windows Clipboard Graphics (CLP)
Windows Icon Resource
Windows Metafile (WMF)
WITA
WiziDraw (DRW)
WiziWord
WordPerfect 4.1, 4.2, 5.0, 5.1 - 6.0
WordPerfect Graphics (WPG 1, WPG 2)
WordPerfect for Macintosh 1.0, 2.0, 2.1, 3.1
WordPerfect for Windows 5.x, 6.1
WordPerfect 5.1 Mail Merge
WordStar 3.3 - 7.0
WordStar 2000, Rel. 3.0, 3.5
WordStar for Windows
Write Now 3.0
Xerox XIF 5.0, 6.0
XIF Graphics
X-Windows PixMap (XPM)
XyWrite III, III Plus, IV
XyWrite IV for Windows
NOTE: The viewer "Run Application" button does not save
changes back to the file cabinet, so it is always
disabled.
5. TRADEMARKS
The following are trademarks of Digital Equipment
Corporation: ALL-IN-1, CDA, DEC, DECnet, Digital,
MailWorks, OpenVMS, PATHWORKS, TeamLinks, TeamRoute, VAX,
and the DIGITAL logo.
The following are third party trademarks:
Microsoft, Windows, Windows 95 and Windows NT are
registered trademarks of Microsoft Corporation.
CORELDRAW and WordPerfect are trademarks of Corel
Corporation.
1-2-3 and Lotus are registered trademarks of Lotus
Development Corporation.
OS/2 and IBM are registered trademarks of International
Business Machines Corporation.
UNIX is a registered trademark in the United States and
other countries, licensed exclusively through X/Open
Company Ltd.
All other trademarks and registered trademarks are the
property of their respective holders.
|