README.TXT

Additional Information for Lotus Organizer, Release 1.1 
====================================================================

(See the end of this file for new information about Release 1.12.)

TIPS.TXT File
-------------
TIPS.TXT contains further information about Lotus Organizer, 
Release 1.1. It is intended for advanced users and administrators. 
It covers the following topics:

1.  Customizing .INI files (ORGANIZE.INI, LOTUS.INI, WIN.INI)
2.  Printing tips
3.  How to print a 4-week view
4.  Adding a front-page logo
5.  Starting the Organizer automatically and opening files
6.  Using cc:Mail
7.  Uninstalling the Organizer
8.  Address-section sorting
9.  The ORGFILES subdirectory
10. Sizing the Organizer window
11. Alarms
12. Using the Organizer as a Windows shell application
13. How an assistant can manage an executive's Calendar
14. How to handle conflicting appointments
15. How to use the Organizer with OS/2
16. A complete ORGANIZE.INI file


TEMP Environment Variable
-------------------------
The TEMP environment variable should be set on each user's 
workstation. Usually it is in the AUTOEXEC.BAT file. Make sure 
that the environment variable is set to point to a valid directory. 
However, do not set it to point to the root (\) directory. 


Running cc:Mail and Notes
--------------------------
If you have both cc:Mail and Notes installed on the workstation, 
make sure that the cc:Mail program path appears before the Notes 
program path in the PATH command line in the AUTOEXEC.BAT file.


File/Open Dialog Box May Not Display the Previous Directory (..) 
-----------------------------------------------------------------
In some versions of Novell NetWare, users may find that the 
previous directory option (..) does not appear in directory lists. 
This makes it difficult to navigate through network directories in 
dialog boxes such as File/Open.

To resolve this problem, follow these instructions:

1. Add the following entry to SHELL.CFG or NET.CFG in the user's 
   root directory--usually c:\--or in the directory from which the 
   Novell network drivers are started:

     show dots = on

2. Reboot the user's computer, and start the Netware shell and 
   communication programs--NETX.COM and IPX.COM. You'll see a 
   NetWare message acknowledging the new entry.  

3. The ".." directory option should now be displayed.


CONFIG.SYS Settings
-------------------
Be sure that the "FILES=" parameter in users' CONFIG.SYS files is 
set appropriately.  A value of 30 should be sufficient both for 
workstations running the Organizer client and also for the 
workstation that is running the AGENT.EXE program.  In Novell 
NetWare, you may also need to increase the value for the File Handles 
parameter.


Running SHARE.EXE
-----------------
SHARE.EXE is provided with your standard DOS operating system. 
Include it in a user's AUTOEXEC.BAT file. If you run Windows from 
your AUTOEXEC.BAT file, make sure you have SHARE.EXE before the 
WIN command line.


Using Superlist of Public Mailing Lists when Selecting Attendees
----------------------------------------------------------------
Selecting a Superlist of Public Mailing Lists from the main cc:Mail 
Directory when creating a meeting will not display users' free-time 
bars.  Use regular public or private mailing lists instead. 


Using IBM ThinkPad with Organizer
---------------------------------
If you're using the IBM ThinkPad configured with the IBM VGA driver 
directly connected to a LAN, the screen may repaint incorrectly 
when you exit the Schedule Meeting dialog box after creating a group 
meeting.  You need to use the standard Windows VGA driver.

To install a new driver:

1. In the Windows Program Manager, double-click the Windows Setup icon.
2. Select Change System Settings from the Options menu.
3. Select VGA in the Display list.
4. Choose OK.
5. When prompted to restart Windows, choose Yes.

Alternatively, you can add the following line to the 
[Settings] section of your ORGANIZE.INI file in the 
"Windows" directory:

  [Settings]   
  NoRoundRegions=1


Inviting a Person Who Is Not an E-Mail User to a Meeting
--------------------------------------------------------
If you wish to invite a person to a meeting who is not listed
in the mail Directory, you may do so by performing the following steps:

1. Type the person's name in the Add field of the Scheduling dialog box.  

2. Organizer will inform you that a meeting notice will not be sent to this
   person.

3. Choose OK to add the name to the attendee list.


Information for Network Administrators Only
===========================================

Managing Resources
------------------
The Lotus Organizer Administrator's Guide, page 34, describes 
setting up Organizer files for resources such as conference rooms 
and equipment. There are two ways to manage resources:

1. Resources are managed by an Organizer scheduling agent. In this 
case, resources are automatically booked by the scheduling agent 
on a first-come, first-served basis. 

The resources are defined as remote "R" users in the cc:Mail 
Directory. No Organizer licenses or cc:Mail licenses are required 
for these resources. 

(If you have an assistant monitoring the remote resource's .ORG file, 
have the assistant open the .ORG file in read-only mode. Otherwise, 
you need to define the resource as a local "L" user, which requires a 
valid cc:Mail license.)

2. Resources are managed by somebody; for example, by an 
administrative assistant. In this case, you define the resources in 
the cc:Mail Directory as local "L" users. 

Since resources managed in this way are local cc:Mail users, they DO 
require valid cc:Mail licenses. No Organizer licenses are required.

NOTE: The Organizer License Packs include extra cc:Mail licenses to 
be used exclusively for resources.


No Scheduling Information Needed for Aliases or Bankshot Mailing Lists
----------------------------------------------------------------------
If you schedule a meeting with an alias that you select from the
cc:Mail Directory, Organizer will find the user name to which the alias 
points. There is therefore no need to enter scheduling information 
for aliases in the cc:Mail Directory. 

If you have manually added scheduling information for alias entries in
your Directory, you should remove this information and add it to the 
entries to which the aliases point, if it is not already there.

Likewise, scheduling information should not be entered for cc:Mail 
bankshot mailing lists, even though these have a location of 'r' in 
the directory.


Setting PATH on Novell Netware Networks
---------------------------------------
Organizer and cc:Mail for Windows, Version 2.0, require that the cc:Mail
program path containing the VIM DLLs be listed in the user's PATH
environment variable. The install programs for both products optionally
set this path in the user's AUTOEXEC.BAT file. 

Because the length of the PATH value is limited, we recommend that 
NetWare administrators write the NetWare log-in script for cc:Mail and 
Organizer users to add the cc:Mail program-path directory as a search 
path when the users log on to the network.

This will reduce the chances of exceeding the maximum PATH length.
It won't matter if users don't answer "Yes" to the prompt to add the 
path to the AUTOEXEC.BAT file during installation. 


~ORGAGNT and Server Entries
---------------------------
If you have multiple post offices and you don't have cc:Mail
Automatic Directory Exchange, you need to make an entry for the agent
(for example, ~ORGAGNT) in every post office.  Make the agent entry
in the same way that you'd make a post office entry, as in the example
below.

In post office Silver-HQ:
~ORGAGNT   P    

In the other post offices: 
~ORGAGNT   p   Silver-HQ

The same is also true for server entries.  You can use SRVADMIN.EXE to
create server entries in each post office that is used by Organizer.


Read/Write Access Rights to cc:Mail Post Office
-----------------------------------------------
The Organizer network guest account, referred to in the Administrator's 
Guide as ORGACCT, requires both read and write access rights to the 
cc:Mail post office directory; for example, M:\CCDATA. 


IBM OS/2 LAN Server, Version 3.0 
--------------------------------
When running Organizer in Windows-OS/2 under IBM OS/2 LAN Server,
Version 3.0, you may find that the following occur:

- When users go to the WinOS/2 desktop, the error message 
  "LANSRV.DRV not found" appears. 
  
- WinOS/2 under IBM OS/2 LAN Server treats network drives as local
  drives.

- Users can't open files by selecting user names.  Consequently, they
  cannot use group scheduling.

If these things occur, do the following:

1. Install Organizer.  Do not use SETUPDIR.  Use DIRADMIN to 
   add scheduling information for the Organizer users.

2. In the Organizer program directory, delete ORGNET.DLL and rename
   PORTABLE.DLL as ORGNET.DLL.
   
3. Run WORKSTN.EXE.

4. Find the DOS LAN requester diskettes, and unzip LANSRV.DRV and 
   WINDLP.DLL.
   
5. Copy these two files to OS/2\MDOS\WINOS2\SYSTEM.

6. Set a path to the files in the CONFIG.SYS file.

7. Add the following lines to CONFIG.SYS:

   DEVICE=C:\IBMCOM\PROTOCOL\LANPDD\OS2
   DEVICE=C:\IBMCOM\PROTOCOL\LANVDD\OS2

8. Add the following line to the AUTOEXEC.BAT file:

  <path>LTSVCFG N1=1 S=H C=10 N=2


SETUPDIR May Not Run Properly in OS/2 on a IBM LAN Server Network
-----------------------------------------------------------------
If you choose to run SETUPDIR during installation, or if you run
SETUPDIR.EXE after installation, the program may not work properly 
in OS/2 running on IBM LAN Server.  A DOS window will appear briefly 
and then disappear without any updates being done.

To update your directory if this happens, use DIRADMIN instead of 
SETUPDIR; refer to the Administrator's Guide section on using the 
DIRADMIN command.


UPDVIM.BAT May Fail if VIM DLLs Are Read-only
---------------------------------------------
UPDVIM.BAT is a script file that the Install program may write if 
your cc:Mail and Organizer DLLs are incompatible and your post office 
is open at the time of installation.  Install gives you the choice 
of quitting, shutting down the post office, and updating the DLLs;
or of continuing and running the UPDVIM.BAT script later.

Install may find some incompatible DLLs but be able to fix them,
in which case the UPDVIM.BAT file will not be written.

Starting with cc:Mail for Windows, Version 2.0, the mail engine and
VIM DLLs in the cc:Mail program directory are read-only files.  If
Install indicates that you should run the UPDVIM.BAT script to update
your DLLs, you may need to make them writable by using the 
ATTRIB -R <filename> command for each file listed in UPDVIM.BAT.  
You can do this easily by modifying UPDVIM.BAT to add the ATTRIB 
command before each COPY command.


Running the Organizer Agent from a Local Drive
----------------------------------------------
The Organizer agent (AGENT.EXE) must have read, write, create, and
erase rights to the ORGANIZE\ADMIN directory, which is where it
runs by default.  

You may prefer to copy AGENT.EXE and the resource files (*.RI) to 
a local drive and run it from there instead.


Native Code-Page Support for the Organizer Agent
------------------------------------------------
In order for international characters in scheduling messages to be
displayed properly in cc:Mail, the Organizer agent must have support
for the native code page on the machine on which the agent is running.
The Organizer agent supports the following code pages: 437, 850, 852,
860, 863, and 865.  If the agent machine has a different code page
installed, the agent will display a warning message that indicates
that international characters may not be displayed properly.


Using Organizer with a Mobile Post Office 
------------------------------------------
The DIRADMIN utility will not run on a Mobile post office.
Use an ADE message or the IMPORT utility to update the post office 
Directory with the user information that Organizer requires.


Additional Information for Lotus Organizer, Release 1.12
====================================================================

Using DDE Links with 1-2-3
--------------------------
In the Organizer User's Guide, the description of how to get DDE data
from Lotus 1-2-3 applies only to Release 3 of 1-2-3.


Changes in Release 1.12
-----------------------

1. Removed run-time dependencies on Lotus Licenser DLL (L1WNET.DLL).
   This DLL is no longer installed or loaded by Organizer.

2. Install updates the PATH statement in AUTOEXEC.BAT to include the
   cc:Mail directory. It disregards commented-out PATH statements. 

3. Organizer can now launch a mail program that had "." in its path. 

4. Temporary files named ORG*.TMP created by the Organizer or the
   Organizer Scheduling Agent are always deleted after being used.

5. Users are now warned when creating, deleting, or modifying a meeting 
   if it is in the past.  They are given the option of sending out 
   messages anyway, not sending out messages but still making the change,
   or canceling the operation. 

6. Workstation Install now handles all low-disk-space situations.

7. Organizer can now be installed in a directory with a name containing
   a "." character.  Help will always be available regardless of the 
   Organizer directory name.

8. The Scheduling Agent now handles meetings with links at all times.
   Also, it will always find Calendar sections that have been renamed.

9. The Scheduling Agent now handles zone qualifiers (for Macintosh users)
   properly in the server\volume field of the Directory.

10. SetupDir has been improved so that you can choose to have both a 
    server\volume field and a drive letter in the cc:Mail Directory 
    comment field.  When doing free time-search, Organizer for 
    Windows will attempt to read an attendee's busy time by using the 
    server name first, then the drive letter.
 
    You can also add a zone qualifier to the server\volume name.  
    Organizer Scheduling for Macintosh requires that the server\volume 
    field is always specified, and will use the zone name if present.
 
11. Organizer now handles old versions of VIM; the "Error: No Error" 
    message will no longer be displayed in these situations. 

12. Organizer now allows adding new attendees to a meeting even if any 
    of the attendees has a conflict.

13. Users can now add Organizer files of non local ("R") cc:Mail users 
    to the File menu.

14. Organizer now allows you to process meetings even when you log in 
    using the Public password.

15. Organizer now allows you to open a file automatically in standalone
    configurations at all times.

