Installing from the Network
---------------------------

To set up an installation directory on a network, copy each disk to 
subdirectories labeled DISK1, DISK2, etc. SETUP can be run from the 
DISK1 directory. SETUP will automatically access the other 
directories without further prompting.

Installing to the Network
-------------------------

Installing to the network is not much different than installing to a 
local hard disk. Use SETUP's Typical Install option the first time 
to set up the program on the network directory. SETUP places a copy 
of itself in the program directory on the network. Each workstation 
running the program should then launch SETUP from the program 
directory on the network and select Workstation Install. The 
Workstation Install option will create a T2W.INI in the 
workstation's local Windows directory with the proper file 
paths. This will let the users customize settings (such as 
the path to their data).


Sharing A T2W.INI
-----------------

In many offices, you may want users to have a local copy of the 
corporate program but share common data and file path information 
normally contained in the T2W.INI file. You can insert the Redirect 
keyname in the [Config] section of each user's local T2W.INI file 
and have it point to a common INI file. When the corporate program 
starts, if it detects the Redirect keyname, it will ignore any other 
settings in the local T2W.INI file and read in the information from 
the indicated INI file. Ideally, each user's local T2W.INI file 
should only be two lines long. One line should be the [Config] 
section header and the second line should be the Redirect keyname.

Sharing a common INI file allows you to set up the information once 
and when changes to data or file path information that affect all 
users have to be made, you only need to make the changes to one 
file.

T2W.INI Format:

Redirect=<file path><file name>

Sample:

[Config]
Redirect=N:\PROGRAM\TAX\COMMON\T2COM.INI

Alternative Startup INI
-----------------------

Some users might, at times, need different T2W.INI file setups. For 
example, a laptop user might need both a "networked" version at the 
office and a non-networked version on the road. By adding the INI 
Prompt keyname in the [Config] section, you can have the program 
prompt the user to select which INI file the program should load up 
under. Alternative INI files are indicated in the T2W.INI by 
creating a [INI Files] header and adding the keynames 
Description<number> and File<number>, where <number> is a number 
between 1 and 100. Everytime you add a Description and File keyname 
you must increment the <number> portion by exactly one.

Note, when the corporate program starts, if it will ignore any other 
settings in the local T2W.INI file in favor of the user-selected INI 
file.

T2W.INI Format:

INI Prompt=1 (1 turns on prompting)
INI Prompt=0 (0 turns off prompting)
File<number>=<file path><file name>
Description<number>=<text to describe the use of the INI file>

Sample:

[Config]
INI Prompt=1
[INI Files]
File1=C:\T2W\T2LOCAL.INI
Description1=Non-network setup
File2=N:\PROGRAMS\T2W\T2NET.INI
Description2=Network setup

Rights
------

The program will run if the component files are marked as read-only, 
or if the user has limited access rights (such as 'RF' on a Novell 
network).  Note that users will need Create and Write rights to 
create or modify the Print Format or Preparer Profile files.

Sharing Windows Operating System
--------------------------------

If the Windows operating system is shared over a network, each user 
of the program must have a local directory for their Windows INI and 
GRP files. This local WINDOWS directory must be entered into the 
AUTOEXEC.BAT PATH setting BEFORE the path to the network copy of 
Windows that is being shared.

Format:

PATH <local Windows directory>;<network Windows directory>

Sample:

PATH C:\WINDOWS;N:\CLIENT\DOS50;N:\CLIENT\WINDOWS

Sharing RES Files
-----------------

In order to conserve space, network administrators may wish users of 
the program to share a single set of resource files (files ending in 
*.RES), even though they have the program itself installed locally. 
To facilitate this, the network administrator may use special 
T2W.INI file settings. Except as noted, the program will look for 
the resources in the path specified by the [Path Info] section of 
T2W.INI, using the keyname ResPath. If no ResPath keyname is 
specified, the program's working directory will be used. Please note 
that the master resource file, T2W.RES, must remain in the program's 
working directory. You may delete the other *.RES files, however.

T2W.INI Format:

ResPath=<file path>

Sample:

[Path Info]
ResPath=N:\CLIENT\PROGRAMS\T2W

Print Format Files
------------------

Sharing 

The program looks for *.FMT files in the same directory as the 
resource files. If the resources are shared between users, the Print 
Format files must also be shared. No adjustment to your T2W.INI file 
is necessary as long as the ResPath keyname has been properly set.

Preventing Users from Changing Files

You can prevent users from overwriting Print Format  files by 
marking them as "Read Only". Users can still modify the print format 
and save them under  different names.

Users can have restricted rights in the resource directory, 
preventing all Print Format files from being saved.

Sharing Help (*.HLP) Files
--------------------------

In order to conserve space, network administrators may wish users of 
the program to share a single set of help files (files ending in 
*.HLP), even though they have the program itself installed locally. 
To facilitate this, the network administrator may use special 
T2W.INI file settings. The program will look for the help files in 
the path specified by the [Path Info] section of T2W.INI, using the 
keyname Help Directory. If no Help Directory keyname is specified, 
the program's working directory will be used.

T2W.INI Format:

Help Directory=<file path>

Sample:

[Path Info]
Help Directory=N:\CLIENT\PROGRAMS\T2W

Tax Preparer Profile
--------------------

The Tax Preparer Profile configuration file is named T2W.DTT. If you 
wish to prevent user from changing the Tax Preparer Profile, you can 
mark it as read only or restrict network rights.

Network supervisors can specify a separate path to the Tax Preparer 
Profile configuration file by adding an entry to the [Path Info] 
section in the T2W.INI, using the keyname Preparer Path. If 
necessary, the name of the Tax Preparer Profile configuration file 
can also be changed by using the keyname Preparer Name in the 
[Config] section of T2W.INI. This would allow several different Tax 
Preparer Profiles to be maintained for different users.

Note: the program cannot use or share the program for DOS' Tax 
Preparer Profile configuration file.

T2W.INI Format:

Preparer Name=<file name>
Preparer Path=<file path>

Sample:

[Config]
Preparer Name=USER1.DTT
[Path Info]
Preparer Path=N:\CLIENT\PROGRAMS\T2W

Model Return
------------

If you wish to prevent user from changing the model return, you can 
mark it as read only or restrict network rights. The model return 
name and path can be set in a similar manner to the Tax Preparer 
Profile data file. There is, however, no way to prevent a user from 
changing these setting using the Configure / Model Return menu 
option.

T2W.INI Format:


Model Name=<file name>
Model Path=<file path>

Sample:

[Config]
Model Name=MODEL1.TT
[Path Info]
Model Path=N:\CLIENT\PROGRAMS\T2W\MODELS

EFILE Directory
---------------

If you wish to change where the CT23 EFILE files are created, you 
can change the Efile Directory keyname in the [Path Info] Section.

T2W.INI Format:

Efile Directory=<file path>

Sample:

[Path Info]
Efile Directory=N:\CLIENT\PROGRAMS\T2W\EFILE

TEMP Directory
--------------

By default the program creates temporary files in the program 
directory. If users do not have create/write rights to the program 
directory, you need to change where the temporary files are created 
by changing the TempPath keyname in the [Path Info] Section.

T2W.INI Format:

TempPath=<file path>

Sample:

[Path Info]
TempPath=N:\CLIENT\TEMP

Batch Printing on a Network

If more than one user does batch printing on your network at the
same time, you should set the temporary file path to a directory 
other than the program directory.

This will ensure that there is no conflict between the lists of 
files being batch printed by different users.


AutoText
--------

If you want the program to read its AutoText entries from another 
INI file instead of T2W.INI, add a Auto Text keyname in the T2W.INI 
under the [Redirect] section.

T2W.INI Format:

Auto Text=<file path><file name>

Sample:

[Redirect]
Auto Text=N:\CLIENT\PROGRAMS\T2W\ATEXT2.INI

Launching A Different Calculator 
---------------------------------

If you want the program to launch a calculator application other 
than the Windows calc.exe, you can insert the CalcName keyname into 
the [Utils] section of your T2W.INI file.

T2W.INI Format:

CalcName=<file path><exe name>

Sample:

[Utils]
CalcName=N:\PROGRAMS\ACCUTIL\ACCALC.EXE


Launching A Different NotePad
-----------------------------

If you want the program to launch a text editor application other 
than the Windows notepad.exe, you can insert the PadName keyname 
into the [Utils] section of your T2W.INI file.

T2W.INI Format:

PadName=<file path><exe name>

Sample:

[Utils]
PadName=N:\PROGRAMS\ACCUTIL\TEXT32.EXE


*********************************************
* Lantastic and other Peer to Peer Networks *
* (without a dedicated file server)         *
*********************************************

If you are running the program on Lantastic or another peer to 
peer network, you must flag the *.EXE, the *.RES files, and 
the *.DLL files as shareable read-only after installing. Do 
this using the DOS Attribute command:

ATTRIB *.EXE +R
ATTRIB *.RES +R
ATTRIB *.DLL +R

If you need to re-install the program for any reason, be 
sure to remove the read-only restriction before re-installing 
by typing:

ATTRIB *.EXE -R
ATTRIB TT*.RES -R
ATTRIB *.DLL -R


*******************
* Novell Networks *
*******************

Unless specified otherwise, Novell networks default the number of 
network file handles to 40 regardless of what appears in the 
CONFIG.SYS file on the workstation. If you are running the program 
from a network drive, you may therefore have insufficient file 
handles to open more than one or two returns.

To increase the number of network file handles, you need to have 
(or create) a file called SHELL.CFG. This file should be located 
on your network boot disk or, if you boot from a hard disk, in the 
same directory as the IPX.COM and the NETX.COM files. The 
SHELL.CFG file should contain the following line:

FILE HANDLES=99

