versions of a Notes client. For instance, you might be in a helpdesk
environment where client users are in different organziations or companies and
who are all standardized on a different version. You mght be in mid-migration
to R5 and have active users in both versions. Or you might be a consultant who
needs to become a user in your client's network, and you do not wish to disturb
your own firm's installation. On the other hand, you may have multiple users
who are painfully trying to share the same Notes installation. Either way,
there is a method to have multiple installations of the Notes client that are
either partially or completely segmented from each other. Here's how:
In Example A, Bob needs to provide support for a third-party Notes application.
His end-users could be running anything from 4.15 up through 4.6.4.
Bob first installs the 4.1.5 client to his workstation. However, during
installation, he changes the name of the /notes/ directory to /notes415/. He
also changes the name of the notes data directory to /notesdata/ instead of
/notes/data/. After installation and configuration are complete, he moves the
notes.ini file from the /windows/ directory to the /notes415/ directory. He
then creates a shortcut to the client on his desktop, calling it "Notes 4.15".
He right-clicks on the shortcut and goes into the Properties, clicking on the
Shortcut tab. The "target" line currently reads "C:\notes415\notes.exe". To
that line he adds a space and then "=C:\notes415\notes.ini" and clicks OK. This
addition means that when the shortcut is double-clicked on, the .ini file that
will be loaded will always be the one in the /notes415/ directory, regardless
of the presence of other .ini files in the system. Bob can now repeat this
procedure with other versions of the Notes client. Each time he does so, he
points the client to the
/notesdata/ directory. Thus, no matter which client he's running, it always
pulls up the same ID file, and the same application that he is supporting. As
long as he doesn't try to run them at the same time, there will be no problems.
In example B, 3 users in a 24x7 helpdesk environment are all sharing the same
workstation, one per shift. Rather than fight conflicts in sharing one Personal
Address Book, they lay down multiple installations like the above, but maintain
seperate data directories for each installation. This allows each user a
segmented client to work from without additional pain and suffering from