BUG 11

home *** CD-ROM | disk | FTP | other *** search

/ BUG 11 / BUGCD1998_02.ISO / email / sime / install.txt < prev next >

Wrap

Text File | 1997-12-04 | 17.8 KB | 431 lines

Simeon Mail Client Version 4.1.x Windows/WindowsNT/Windows95 INSTALLATION INSTRUCTIONS Last Updated: December 04, 1997 Table of Contents ----------------- 1.0 System Requirements 2.0 Installing Simeon Mail 2.1 Preparation 2.2 Licensing 2.3 Where to Install 2.4 Running the Setup Program 2.4.1 Network Install 2.4.2 Local PC Install 2.4.3 Workstation Install 2.5 Information About DLL's 2.5.1 Manually Installing CTL3Dx, MSVCRT40, and MAPIx DLL's 3.0 Configuring Simeon Mail 3.1 How Users will Run Simeon Mail 3.2 Configuring the Windows Environment 3.3 Simeon Configuration Files 3.3.1 Site Defaults 3.3.2 New User Startup Script 4.0 Upgrading from Previous Versions 1.0 System Requirements ----------------------- Running Simeon Mail requires a 386 or better machine running one of the following: - Microsoft Windows 3.1, - Windows for Workgroups 3.11 - Windows NT - Windows95 - OS/2 2.1 (with the DOS/Windows compatibility toolkit), Disk space required for a complete (Mail plus LDUA and Kerberos) installation of Simeon Mail is approximately 7.5 Mb for Windows and 4 Mb for WindowsNT/95. Additional space will be required if users store mail or address books locally. Memory requirements are a minimum 4 Mb, with 8 Mb or more recommended. Simeon also requires a TCP/IP network, and a TCP stack supporting a Winsock 1.1 compliant DLL. This stack must be properly installed. IMPROPER INSTALLATION OF THE TCP STACK OR WINSOCK DLL IS THE LEADING PROBLEM IN INSTALLING Simeon Mail. The following stacks are known to work with Simeon Mail: - Beam & Whiteside - BWTCP 3.x - FTP Software - PC/TCP 2.2 - Novell Lan Workplace 4.1 (BETA Winsock) - NetManage Chameleon - SuperTCP 1.1 - Trumpet Winsock - PC/NFS 5.0b through 5.0w - TCP/IP included with Windows NT/95 2.0 Installing Simeon Mail -------------------------- 2.1 Preparation --------------- If you obtained your distribution via the Internet: If you obtain a version of Simeon Mail over the Internet, you will be provided with a self-extracting archive executable. Create a temporary directory on the machine where Simeon Mail will be installed, and copy the executable to that directory. For example: C:\> mkdir tmp C:\> copy 32full.exe tmp 1 file(s) copied C:\> cd tmp C:\TMP> You will then need to run this file to extract the files from the archive, or you may extract them using an "un-zipping" tool of your choice. The resulting files will include the "setup" program. If you obtained your version via Diskette: If you have obtained a version on diskette, the setup program is provided directly, there are no intermediate steps to unpack the program. 2.2 Licensing ------------- You require one license of Simeon Mail for every CPU, even if Simeon Mail is installed on a shared, networked volume. 2.3 Where to Install -------------------- You have the option of installing Simeon on each PC that will be running it, or placing it on a networked drive that is NFS mounted by the client PCs. We recommend installation on a shared network drive if this is possible, to make upgrades and user support simpler. It is also possible to have some clients running from a network drive while others run from their local drives, as will certainly happen with notebook users. If Simeon is installed on a networked drive, the Workstation setup will need to be run at each workstation accessing Simeon Mail. * Note: * DO NOT install Simeon 4.1.x into your Simeon V3.x or v4.0.x program directory. Select a new directory. You may (and are encouraged to) use the same working directory as was used for Simeon 3.x or v4.1.x so that Simeon 4.1.x can access your previous configuration and local folder and address book files. 2.4 Running the Setup program ----------------------------- From within Program Manager in Windows, choose "File / Run" and select the setup.exe program you obtained, either on diskette or the Internet copy you unpacked onto your hard disk. The program will prompt you for a choice of install type: Network or Local PC. An Evaluation version of Simeon is also available, and has the same features a Local PC install, except many of the steps of configuration have been done. This version has a 30 day expiration date. * Note 1: Workstation installation is only available when running setup.exe from a network installation. * Note 2: The setup program will not install the CTL3Dx, MSVCRT40, or MAPIx dll's into the Window's System directory. This must be done MANUALLY, if required. See section 2.5.1 for more details. 2.4.1 - Network Install The setup program will prompt you for the directory where Simeon Mail and its supporting files (DLL's, system configuration files and so on) should be installed. It will prompt you for the components to install: - Mail only - Text reference files Then after selecting and verifying your choices, Simeon setup will install the requested program files into the selected directory. 2.4.2 - Local PC Install The setup program will prompt you for the directory where Simeon Mail and its supporting files (DLL's, system configuration files and so on) should be installed. It will prompt you for the components to install: - Mail only - Text reference files - [ LDUA ] - only if installed to network Then after selecting your choices, you will be asked for a Working directory in which your local configuration files will reside. Once you have verified your selections, Simeon setup will install the requested program files into the selected directory. The setup program will create the requested directories if necessary, and then copy the needed files into that directory. 2.4.3 Workstation Installation If you have installed Simeon on a networked drive, each user who access it should first run the network setup program and select the Workstation installation option. This will install the Simeon configuration components, and create a program group and icon with the desired working directory. To run the Workstation installation after Simeon has been installed on the network, select File->Run from the Program Manager menu and enter the following: p:\simeon41\setup.exe replacing p:\simeon41 with the network file path where Simeon 4.1.x has been installed. The setup will ask for the Simeon 4.1.x program directory on the network and ask you to identify the Working (user) directory on the workstation. This can be your V3.x or v4.0.x working directory if you wish. 2.5 Information About DLLs -------------------------- The first thing to know about DLLs in regards to Simeon is that the Simeon setup program will only install the necessary system DLLs to your system directories if you are doing a "Local PC" or a "Workstation" install. If you are doing a "Network" install, the necessary DLL files will be placed into the Simeon 4.1.x program directory, but not into your system directories on the PC hard drive. Simeon requires the presence of several system files in order to function properly. The setup program will detect whether a necessary system DLL is missing, or not up-to-date, and will install replacements as necessary. If the setup program is required to replace an already existing DLL file it will create a copy of the file in the directory where it originated, replacing the .DLL extension with .SIM, before installing the new version. Any system files that have been replaced will be backed up into the same directory where they originated, with a .SIM extension. If for any reason you wish to restore any of these files, you may do so by renaming them as follows: if you find: rename it to: ------------ ------------- 16 bit - D2HNAV16.SIM D2HNAV16.EXE D2HLNK16.SIM D2HLNK16.DLL MSOUTLIN.SIM MSOUTLIN.VBX D2HTOOLS.SIM D2HTOOLS.DLL 32 bit - D2HNAV32.SIM D2HNAV32.EXE D2HLNK32.SIM D2HLNK32.DLL MFC30.SIM MFC30.DLL MSVCRT20.SIM MSVCRT20.DLL Remember that you can run the Simeon setup again to restore the system DLL files to a state in which the Simeon program can use them. 2.5.1 Manually Installing CTL3Dx, MSVCRT40, and MAPIx DLL's Installation of the CTL3Dx, MSVCRT40, and MAPIx DLL files has become a complex issue, and one which has required us provide the best option without infringing on the smooth running of an individual's computer system. Simeon requires the Window's user to utilize a combination of the above DLL's (depending on platform). However, many other programs utilize these DLL's as well, and it would be presumptuous of us to replace them without knowing the type of configuration you wished for your system. For this reason, we have moved the installation of these DLL's out of the installer, and leave that for you to do manually, if you wish. The following is a list of instructions on installing these DLL's, and some comments on why you may or may not wish to install them. 1. In the PROGRAM DIRECTORY of your recently installed version of Simeon, you will find the following files: MS System Simeon MAPI --------- ----------- 16 bit - CTL3D._DL MAPI.DLL 32 bit - CTL3D32._DL MAPI.DLL MSVCRT40._DL MAPI32.DLL The MS System files are DEFINITELY required to run Simeon. If you do NOT have these files in your Window's system directory, then you need to install them. The latest version of these files are available on with Microsoft Service Packs and often with the latest Microsoft software. We provide them for your convenience. Though they may not always be the latest and greatest, they should work with your system. The Simeon MAPI files are necessary if you require MAPI capabilities. Windows 95/NT provide MAPI support with the OS install. Other networking software either utilize the Microsoft MAPI, or provide their own. In any case, you will need to decide which MAPI to use based on what software you will be using. Simeon provides a Simple MAPI DLL with Simeon extensions. If this is not sufficient to run other software you need, then you will not want to install the Simeon MAPI. 2. To install the desired DLL file(s), Copy from the Simeon Program To the Window's directory: System Directory -------------- ---------------- 16 bit - CTL3D._DL CTL3D.DLL MAPI.DLL MAPI.DLL 32 bit - CTL3D32._DL CTL3D32.DLL MSVCRT40._DL MSVCRT40.DLL MAPI.DLL MAPI.DLL MAPI32.DLL MAPI32.DLL Remember, the question is not one of whether you should have these files in your Window's system directory, but one of whether you should use OUR DLL's or stick with the one's you have! 3.0 Configuring Simeon Mail --------------------------- Simeon Mail is designed to support administration at the server and individual level. Ideally, one copy of Simeon Mail is stored on a file server, and all users access the Simeon Mail installation directory from the network. Simeon Mail will work equally well in a standalone installation, but the potential benefits of sharing configuration information will not be available. Simeon Mail will potentially share many different kinds of configuration information including: * communication and user preference configurations * address book information * multipart message file type Helper Applications Configuration stored in the Simeon Mail installation directory is by default the "server configuration". Any configuration information located in this directory is automatically inherited by all users. Most (but not all) information stored in the server configuration can be overridden by user-specific configuration information. Each Simeon Mail user is provided with a user configuration directory - or "Working" directory. The Working directory contains all of the user's personal configuration information. Users can modify any of their configuration information using the configuration editing facilities of the Simeon Mail user interface found under the Options/Edit menu. Following is a description of the procedures that the "administrator" would use to configure Simeon Mail for use in a TCP/IP workgroup environment. Note that if the installation is going onto a single machine (standalone), then the installer can be thought of as "the administrator of a workgroup of one". 3.1 How Users will Run Simeon ----------------------------- Simeon Mail makes a distinction between the Program directory and the Working directory. The Program directory is the directory containing the application and its associated files, which may be either on the user's hard disk or on a shared disk. The Program directory is never written to. The Working directory on the other hand, should be on the user's hard disk. It stores information particular to that user, which may include local folders, address books, or configuration. A user will run the Simeon workstation installation program in order to configure their PC for use with Simeon. See the section "WorkStation Installation" above. 3.2 Configuring the Windows Environment --------------------------------------- Simeon Mail is WinSock compliant application that *requires* a Winsock DLL from your TCP/IP stack. You must make the Winsock DLL file from your TCP/IP stack available for Simeon Mail to use. If the Winsock DLL has been installed correctly on your Windows workstation, this should not be a problem. To verify that a "winsock.dll" file is available for use by Simeon Mail, check that the correct Winsock DLL file is available: *1) In a directory specified in the DOS "PATH" variable, 2) OR in the Windows installation directory, 3) OR in the Simeon Mail installation directory (INSTDIR). Option #1 is the recommended approach. The winsock.dll file that is distributed with the TCP/IP stack should remain in the stack installation directory, and be included in the DOS PATH. IT IS HIGHLY RECOMMENDED THAT YOU USE THE "OFFICIAL" WINSOCK DLL THAT COMES WITH YOUR TCP/IP STACK. If you don't have a Winsock DLL, then you should contact your vendor and request one. If they don't have one by this time, you should consider changing TCP/IP vendors. 3.3 Simeon Configuration Files ----------------------- 3.3.1 Site Defaults -------------------- When a user runs Simeon Mail, various pieces of information are read from the site default files in the Simeon program directory. These files contain various system-wide defaults that specify such things as message services, host names and the default user interface settings. This information, along with changes the user makes in the course of using Simeon Mail, are then stored in the user directory under the name "default.tcl", or optionally to an IMSP server. As a system administrator, you can customize the site default files for your environment before providing the application to individual users. This will allow you to provide valuable configuration information to your users, simplifying their job in setting up and running Simeon and thereby your job as well. The site default files are found in the Simeon program directory and are named sysdflt.tcl and sysdflt2.tcl. If you are a site administrator it is STRONGLY recommended that you read both files in their entirety, however the sections named below are the ones which we feel would be the most likely candidates for modification prior to distribution. The files themselves contain the complete documentation on the options, their purpose and the possible value settings. To modify these files, you may use any text editor. STARTUP DEFAULTS (sysdflt.tcl) MESSAGE SERVICES (sysdflt.tcl) DEFAULT FOLDERS (sysdflt.tcl) AUTHENTICATION (sysdflt.tcl) HELPER APPLICATIONS (sysdflt2.tcl) 3.3.2 New User Startup Script ----------------------------- When a user runs Simeon for the first time, Simeon executes the TCL script in the startup.tcl file located in the Simeon program directory. This file may be customized to add or remove questions which will be asked of the user the first time he or she runs Simeon. Many sites typically customize the sysdflt.tcl file with the server information and remove all of the questions from the startup script with the exception of the User Name and email address. For more information on modifying this file, please see the startup.tcl file itself and the documentation for the corresponding option in the sysdflt.tcl file. * NOTE: * The sysdflt.tcl from 4.1.1 or earlier may be used with Simeon 4.1.4, however we do recommend upgrading to the new format for the following reasons: - one sysdflt.tcl file for all platforms - customized folder prefix/location settings for Mac and Motif - additional helper applications for Windows and Motif - customized settings on a per platform basis - customized windows sizes and positions for display size - debug trace stmts. throughout which may be toggled on and off easily 4.0 Upgrading from Previous Versions ------------------------------------ Please refer to the following documents included in this distribution. See "ECStoV4.txt" for instructions on how to upgrade from ECSMail 2.x to Simeon 4.x.x. See "V3toV4.txt" for issues regarding upgrading from Simeon 3.x to Simeon 4.x.x. End Simeon 4.1.x Windows/WindowsNT/Windows95 Installation Instructions