Welcome to TeamTalk, the graphical groupware that GETS YOUR PEOPLE TALKING! Contents -------- 1. INSTALLATION 2. HARDWARE AND SOFTWARE CONSIDERATIONS 3. NETWORK CONSIDERATIONS 4. FILES 5. TEAMTALK UTILITY PROGRAM 6. HOW TO REACH US --------------------------------------------------------------------- 1. INSTALLATION: There are two steps in the TeamTalk installation - database installation and workstation setup: 1) Run SETUP.EXE on the distribution diskette. This will install the TeamTalk files and database on your network, as well as the setup program TTCSETUP.EXE. 2) Run TTCSETUP.EXE from each workstation that will be accessing TeamTalk. This ensures that SHARE and OLE are installed, as well as creating a TeamTalk program group in Program Manager. *** If you are upgrading from TeamTalk version 0.93 or 0.94 you will need to convert your database to the new format. To do this: 1) Back up the entire TeamTalk directory. 2) Install the new version of TeamTalk over the old one. 3) From the File Manager, run the conversion utility TTCON96.EXE. It will present you with a dialog box - press the "Convert" button. 4) Run TTCSETUP.EXE from each workstation. --------------------------------------------------------------------- 2. HARDWARE AND SOFTWARE CONSIDERATIONS: TeamTalk requires an IBM compatible personal computer with an 80286 or higher CPU, at least 2 megabytes of RAM, 4 megabytes of network file space, DOS version 3.1 or higher, and Microsoft Windows version 3.1 or higher. FILES - we recommend that you set your FILES= value in CONFIG.SYS to 40 or higher for best OLE 2.0 results. SHARE.EXE - you must have SHARE running (installed in CONFIG.SYS or loaded from AUTOEXEC.BAT) - it is used for record locking. If SHARE or an equivalent facility (such as Windows For Workgroups, see below) isn't running, when you try to start TeamTalk it will put up a file-lock error message (suggesting you check your SHARE parameters) then quit. The recommended minimum settings are /L:500 and /F:5100. An example of the line to add to AUTOEXEC.BAT is: C:\DOS\SHARE.EXE /L:500 /F:5100 Performance problems - for best performance, we recommend at least 4 megabytes of RAM and Windows running in 386 enhanced mode. If you have less storage than this, TeamTalk may run slowly and/or have problems painting the topic background screens. If this happens, try running TeamTalk in Text-only mode (selected from the View menu). In this mode, TeamTalk doesn't use bitmaps to display topic icons and comment headers, so it uses less space and runs faster. This is also useful if you are running TeamTalk over a remote system. --------------------------------------------------------------------- 3. NETWORK CONSIDERATIONS: TeamTalk will run on any network that supports file locking through SHARE.EXE. SHARE.EXE: even though most networks provide emulation of SHARE on redirected drives, you will still need to run SHARE because it is used by OLE 2.0 when accessing files on your local hard drive. The exception to this is Windows for Workgroups running in 386 enhanced mode: SHARE.EXE is not needed in this case since WFW has its own virtual device driver, VSHARE, which provides all necessary file and record locking capabilities. FILES: Some peer-to-peer servers supply all open network files from the same pool of file descriptors. On these systems, TeamTalk will experience Windows out-of-files situations, system share violations and/or file lock errors if the file settings in CONFIG.SYS and/or the server's startup script are too low. If this happens, consult your network manual to determine the proper file settings as well as any file, share or lock settings needed in your server's startup profile. The recommended minimum files setting is 80 for the file server. 10NET 5.0: Recommended minimums for the TeamTalk file server's file settings: CONFIG.SYS setting of FILES=80 and SUPER.PRO settings of OPENFILE=80, OPENHNDL=80, LOCKS=160 and SHAREFIL=160. Raise these values if you experience system or lock errors, and remember that the best settings will depend on the number of clients accessing TeamTalk. Also, TeamTalk will have problems running if you use 10NET's SHARMAT3=Y option, which tells 10NET to use the DOS 3.2 SHARE matrix. Automatic login: If your network supports Microsoft Windows, be sure to load its Windows driver. That way TeamTalk can retrieve login information from the driver and log you into TeamTalk automatically. If your network doesn't support Windows, or if you aren't running TeamTalk on a network at all, when you start up TeamTalk it will ask for your login name. If you decide to protect your TeamTalk membership with a password, TeamTalk will prompt you for it and not log you in automatically. LANtastic 4.1: the login name reported to TeamTalk by LANtastic's Windows driver (MSNET.DRV) is the machine name, not the user name you may have used to login to LANtastic resources. Running TeamTalk on a server: some peer-to-peer networks give priority to network users of disk drives over the physical owner of the drive. So, if your machine is the TeamTalk server, be sure to access TeamTalk through a redirected network drive rather than directly through your hard drive. Otherwise, when there is heavy network traffic TeamTalk's performance may suffer. --------------------------------------------------------------------- 4. FILES: The TeamTalk files and basic database file set use about 3.5 megabytes of disk space. Extra space is allocated as needed for topic appends and indices, as well as a small amount for each new user and topic you add. Once installed, your TeamTalk directory will contain these files: TEAMTALK.EXE - TeamTalk program module TEAMUTIL.EXE - TeamTalk Utility program module (not included in evaluation versions) TTHELP.HLP - help file CTPW60D2.DLL - database module TRAXCT.CFG - configuration file README.TXT - this file - last minute information xxx.CTD,xxx.CTI - sample topic files (see below) *********** After TeamTalk has been initialized, its directory will contain the following data files. These files constitute TeamTalk's database, so they should be backed up as a unit. 1) Topic data files, one set per topic Bnnn.CTD Bnnn.CTI Cnnn.LOK Dnnn.CTD Dnnn.CTI 2) Additional data files TTCONF.CTD TTCONF.CTI TTDATA.CTD TTDICT.CTD TTDICT.CTI TTLOCK.CTD TTLOG.CTD TTMEMBER.CTD TTMEMBER.CTI 3) OLE object files, as necessary Snnn.CTD --------------------------------------------------------------------- 5. TeamTalk Utility Program: The TeamTalk Utility program (TeamUtil) is designed to be used by the administrator or supervisor of the TeamTalk system. It can be used to check the database for errors that may have been introduced by system crashes, hardware errors, etc. It can also check for certain conditions that can be created inadvertently by the supervisor, such as a topic whose moderator userid has been deleted from the system. NOTE: This program is not included in the evaluation version of TeamTalk. --------------------------------------------------------------------- 6. HOW TO REACH US: Voice: (310) 649-5800 (Monday - Friday, 7 AM - 6 PM Pacific time) FAX: (310) 649-6200 Or write to us: Trax Softworks, Inc. 5840 Uplander Way Culver City, CA 90230-6620