TIME LINE for Windows Version 1.0
March 1992

README.TXT CONTENTS:

- Time Line for Windows Program Files
- Hard Disk Space Requirements
- Installing on a Local Area Network
- Tips for Using the Tutorial
- International Tips
- Notes on Printer and Plotter Setup
- Using the Windows Clipboard
- Import and Export Notes
- Time Line for DOS
- On Target
- Object Linking and Embedding (OLE) Attachments
- Important Note for Microsoft Word 2.0 Users
- Windows 3.0 versus 3.1


TIME LINE FOR WINDOWS PROGRAM FILES
===================================
When you receive Time Line for Windows, the disks 
contain compressed files.  You must first run the 
INSTALLATION PROGRAM to transfer Time Line for Windows 
to your computer system.  The DOS copy command cannot 
be used to install Time Line for Windows.

The installation procedure is detailed on the Quick 
Reference Card, and is repeated in the "Getting Started" 
section of the User Manual.

IMPORTANT:  We recommend using Windows 3.1.  For more 
information refer to the section on Windows at the end 
of this readme.

Here is a list of program files as they appear BEFORE 
and AFTER installation.

BEFORE installation:

INSTALL.EX$.......Compressed Install program
INSTALL.EXE.......Start Up Install program
START.EXE.........Install program launcher
INSTALL2.EXE......Start Up Install program backup
INSTALL.INS.......Install Script
README.TXT........This "readme" file
*.TXT.............Install messages
TLW_INS.DLL.......Installation support functions
TLW_INS.LI$.......Installation support functions
SAMPLES.LI$.......Compressed Time Line for Windows 
                  sample files
TLW_SUPP.LI$......Compressed Time Line for Windows DLLs
                  and MSP Importer
TLWIN.SER.........Serial number file for LAN install
TLWIN.NSR.........LAN support file
TLW_EXE.LI$.......Compressed Time Line for Windows 
                  application
TLW_HELP.LI$......Compressed Time Line for Windows 
                  Help file
LANLIB.LI$........Compressed LAN application
TOUR1.LI$.........Compressed Tutorial files
TOUR2.LI$.........Compressed Tutorial files
TOUR3.LI$.........Compressed Tutorial files
TOUR4.LI$.........Compressed Tutorial files

AFTER installation:

TLWIN.EXE.........Time Line for Windows program
TLW_LINK.DLL......Time Line for Windows DLL
TLWIN.HLP.........Time Line for Windows help system
*.TLL.............Sample Window Library files
SETATTR.BAT.......Batch file for peer-to-peer LANs
README.TXT........This "readme" file

AFTER installation, the following DLL files will be
updated in your Windows system directory if necessary:

COMMDLG.DLL
OLECLI.DLL
SHELL.DLL

If you choose to install on a local area network (LAN), 
in addition the following files will be copied to your 
hard drive AFTER installation:

LANUSER.EXE......LAN usage management program
TLWIN.NSR........LAN support file

AFTER installation, the following tutorial files 
appear:

TUTORIAL.BRD     Tutorial script
EGATAPE.BRT      EGA Tutorial playback file
VGATAPE.BRT      VGA Tutorial file
SVGATAPE.BRT     SVGA Tutorial file
BRTAPET.EXE      Tutorial program
BRTAPET.DLL      Tutorial DLL
BRTUTOR.EXE      Tutorial program
BRDYNT.DLL       Tutorial DLL
TL_TUTOR.INI     Tutorial INI file
*.TUT            Tutorial schedule files
*.BAK            Tutorial schedule file backups
*.BMP            Tutorial bitmaps
DELTUTOR.BAT     Batch file to remove the tutorial

The tutorial runs "live" in Time Line for Windows and 
is comprised of a special macro program, bit mapped 
graphic images, and samples. Refer to the section 
"Tips for Using the Tutorial" later in this README 
document for more information.


HARD DISK SPACE REQUIREMENTS
============================
Time Line for Windows, with all files installed, uses 
approximately 4.5 megabytes of space on your hard 
disk.  If you do not have enough space to install all 
of the Time Line files, you may choose not to install 
the tutorial.  If you omit the tutorial, Time Line for 
Windows will use approximately 2.0 megabytes of space 
on your hard disk.

CONSERVING DISK SPACE:

If you need to conserve hard disk storage space, 
you can delete the tutorial files by running the 
DELTUTOR.BAT batch file.  You can also delete the 
sample Window Library files (*.TLL).

Because these files are in compressed format on the 
original Time Line for Windows diskettes, you must 
first run the installation program to uncompress them.

It is not recommended that you delete the Help file; 
however, if you are severely restricted for disk 
space, you may run Time Line for Windows without Help.


INSTALLING ON A LOCAL AREA (LAN) NETWORK
========================================
If you choose to install Time Line for Windows on a 
local area network, the following files appear 
in a subdirectory named \LANDIR.

LANUSER.EXE...LAN usage management program
TLWIN.NSR.....LAN support file
README.TXT....This "readme" file

During the installation procedure, you will be 
prompted to choose one of three install 
options:  1) Local Hard Disk, 2) Network Server, or 
3) Add a Node to Network Server.

NOTE:  The LAN Node product can ONLY be installed on a 
full Time Line for Windows product that has been 
installed as a LAN server.

The LAN files are installed ONLY if you choose to 
install Time Line for Windows as a LAN file server.  
They are placed in a \LANDIR subdirectory.  The LAN 
files allow users to run Time Line "one-at-a-time."  
If more than one user tries to run the program 
concurrently, a warning appears advising that all 
available copies of Time Line are in use.

You can convert full copies of Time Line to 
LAN Nodes by deleting local copies and 
re-installing them as LAN Nodes.  Also, you can 
purchase additional LAN Node packages to add as many 
concurrent user slots to your LAN as you need.

For Time Line to run properly \LANDIR must be located 
beneath \TLWIN.  The \LANDIR subdirectory must have 
CREATE\READ\WRITE\MODIFY and DELETE network access 
privileges for all concurrent users.

PEER-TO-PEER NETWORKS:

If your LAN is a peer-to-peer type, such as LanTastic
or Phonenet Talk, run the SETATTR.BAT batch file.  This 
batch file will automatically configure Time Line to run
on a peer-to-peer network.

COMMON LOCAL AREA NETWORK ERROR MESSAGES:

Following are common error messages you may encounter 
when running on a LAN.

1) MESSAGE #1:  The .NSR file is missing.

   SOLUTION:  Make sure the .NSR file is in the 
   \LANDIR subdirectory.  Also, make sure the \LANDIR 
    subdirectory is located under the \TLWIN directory.

   If the .NSR file is missing from the \LANDIR
   subdirectory, re-install Time Line on the LAN file
   server.  You will also need to re-install any LAN
   Node versions of Time Line you had previously 
   installed.

2) MESSAGES #150 and #151:  Time Line cannot locate
   the \TEMP directory.

   SOLUTION:  Make certain the \TEMP directory has been
   set up and that the user has READ/WRITE access to it.

3) MESSAGE #206:  Time Line cannot locate the \LANDIR 
   subdirectory.

   SOLUTION:  Click on the TLW icon and select
   "Properties" from the Windows Program Manager
   or Norton Desktop for Windows menu.  Verify 
   that the path is correct.

   Use File Manager or Norton Desktop for Windows to
   make sure the \LANDIR surbdirectory is under \TLWIN.
   Click \LANDIR and choose Properties on the 
   File Manager menu to verify that READ ONLY and 
   ARCHIVE are deselected.

4) MESSAGE:  Sharing violation on [DRIVE].

   This is a Windows error message that may display
   on a peer-to-peer network.

   SOLUTION:  Run the SETATTR.BAT batch file, which is
   located in the \TLWIN directory.  This batch file 
   sets certain Time Line files as READ ONLY, which
   permits it to run on the peer-to-peer LAN.

   If for some reason you need to erase the Time Line
   LAN files after you've run SETATTR.BAT, you will 
   need to make them READ/WRITE.  Use the File Manager
   Properties command to do this.


TIPS FOR USING THE TUTORIAL
===========================
The tutorial is designed to give you an overview of 
the look and feel of Time Line, and to introduce you 
to its main features so you can quickly create and 
present your first plan.

Using a special macro program, the tutorial takes 
control of a "live" copy of Time Line for Windows, and 
takes you step-by-step through each of the three 
modules: The Basics of Planning and Tracking, Managing 
Your Resources, and Customizing Your Presentations.

While demonstrating Time Line for Windows, the 
tutorial prompts you to follow the descriptive 
material.  Relax and let the tutorial do the work of 
actually entering data.

The tutorial macro program makes certain assumptions 
involving the configuration of your hardware and Time 
Line for Windows.  If unexpected conditions are 
encountered, problems may occur where the tutorial is 
out of sync with Time Line for Windows.  The tutorial 
is designed to detect as many computer system 
variations as possible.  We have tried to foresee any 
problems you might encounter.  However, it is possible 
that the tutorial may not catch everything, every 
time.

Troubleshooting Tutorial Problems
---------------------------------
VIDEO DISPLAY:

The tutorial operates in VGA (640 X 480), SVGA (1024 X 
768) and EGA (640 X 350) configurations. It senses 
your screen display and adjusts itself accordingly.  
If other displays, such as CGA or Hercules Graphics 
are detected, the tutorial quits with a message 
explaining the problem.

Because the tutorial is running "live" and uses mouse 
movements in Time Line , it is sensitive to the 
placement of various screen elements.  Certain screen 
conditions can cause these elements to be placed in 
such a manner as to "dodge" the mouse.  This can 
happen under the following conditions:

1) Your Window Border is wider than 3 pixels. You can 
   check this in the Control Panel, inside the "Desktop" 
   section. Or you can look in your WIN.INI file for the 
   parameter "Border Width=3." Be sure that Border Width 
   is set to 3.

2) Certain font managers cause screen characters to be 
   drawn differently. This will change the display enough 
   to throw the tutorial off track. In particular, Adobe 
   Type Manager (ATM) and MoreFonts (r) draw screen 
   characters differently if the option "Use Pre-built 
   or Resident Bitmap Fonts" is not checked. If you are 
   using Adobe Type Manager (r) or MoreFonts (r), go to 
   the ATM or MoreFonts (r) Control Panel and make sure 
   this option is enabled.  As of this writing, ATM and 
   MoreFonts (r) are the only font manager programs known 
   to cause this anomaly.  The tutorial looks for ATM 
   specifically to check this condition.  It does not 
   check for MoreFonts (r), even though the same problem 
   has been reported.  If the tutorial can locate ATM , it 
   automatically checks the ATM.INI file and advises you 
   if there is a problem.

INITIALIZATION VARIABLES:

The tutorial assumes certain start-up conditions so 
that it can build a sample plan with correct durations 
and sample data. When you run the Tutorial, Time Line 
for Windows gets the correct initialization values 
from a file called TL_TUTOR.INI, normally found in 
your Windows main directory.  Please do not alter this 
file. If you are experiencing problems related to the 
mouse not finding a task bar, the TL_TUTOR.INI file has 
probably been altered.

There is a backup copy of this file in your Time Line 
for Windows directory. If you are experiencing 
problems with the tutorial, copy the TL_TUTOR.INI from 
the \TLWIN directory into your Microsoft Windows 
main directory.  Then run the tutorial again; the 
problem should be cleared up.

INTERNATIONAL TIPS
==================
Windows supports a variety of International currency 
and date formats. This includes currency symbols and 
decimal places.  From the Windows control panel select
International. You can change the language, currency, 
decimal and date formats from this screen. When 
exiting Windows make certain to select "Save Changes."

The International default Calendar is "NONE," that is, 
no holidays are selected.

NOTES ON PRINTER AND PLOTTER SETUP
==================================
You can begin printing immediately after installation 
if you already have a printer or plotter configured 
for Windows through the Windows Control Panel.

Contact Microsoft's technical support or the hardware 
manufacturer of your printer or plotter to make sure 
you have the latest improvements to drivers for your 
particular model.

If you are using Windows 3.0, please read additional 
comments in the Windows section at the end of this 
readme.

RECOMMENDED MARGIN SETTINGS:

The default margin settings are determined by the 
printer and/or plotter you install under Windows.  
There are variations for many printing devices that 
require different margin settings.  For example, some 
printers have non-printable areas as small as 1/8" 
(.5 cm) on each side, while other devices, such as 
large plotters, may have up to a 2 1/2" (5.2 cm) non-
printable area on each edge.  Also, these non-
printable areas may not be equal for top, bottom, left 
and right margins.

Therefore, to ensure optimal margin settings, check 
the documentation for your device to verify specific 
settings.  It is recommended that you give yourself an 
additional 1/4" (.7 cm) of leeway beyond the printer's 
limitations in order to compensate for variances in 
loading paper into the device.

CHANGES TO THE PRINTER SETUP FROM WITHIN THE PROGRAM:

Normally, you make all changes to printer setup from 
the Windows Control Panel.  However, many of the 
latest Windows drivers support changes to printer 
setup from within a Windows application.  These 
drivers allow you to make your initial settings in 
the Windows Control Panel and make additional changes 
in Time Line for Windows once the driver has been 
initialized.

For example, you might want to change page orientation 
after you've previewed a Time Line for Windows report.  
If the Windows driver supports this feature, you can 
make a page orientation change from within Time Line 
for Windows.

Time Line for Windows can automatically detect if the 
driver supports orientation changes.  If the Windows 
printer driver does not support this feature, the 
orientation options will be grayed out in Time Line 
for Windows' page setup.

THE PRINT BLACK & WHITE OPTION:

The Print Black & White option on the Print dialog box 
allows you to automatically print in black and white 
no matter what your on-screen colors are.  This is 
particularly beneficial for users of laser printers 
and PostScript printers, because these printers do not 
always translate on-screen colors to readable shades 
of gray.

In order to take full advantage of the widest 
selection of gray shading, first set up your screen 
colors any way you choose and then print a Time Line 
for Windows report. If your report shows readable 
contrast, then you do not need Print Black & White.  
If the output is not readable (for example, not enough 
contrast between foreground and background), use the 
Print Black & White option, and print again.

With the Print Black & White option all text is 
clearly visible, and fewer shades of gray are used.  
Foreground text is always at least 25% darker than the 
background.

CREATING PRINT FILES:

When producing a FILE output of a schedule and then 
copying the file to an output device, use the /B 
parameter with the DOS COPY command.

PRINTING SPEED VERSUS RESOLUTION:

Higher printer resolutions take longer to print.  Use 
lower resolutions or draft mode (when available) if 
you are concerned about printing speed and a lower 
resolution is acceptable.

IMPORTANT NOTE FOR HP LASERJET SERIES III USERS:

For HP LaserJet Series III printers using printer 
driver version 3.86, there are known problems at 
150 dpi resolution.  If you have selected 150 dpi, 
Time Line automatically switches to 300 dpi, which 
produces higher quality output.  If your HP Series 
III printer has at least 3 megabytes of memory, you 
should not experience noticeable slowdown in printing 
speed.  If you do experience a significant degradation 
in print speed, we recommend using 75 dpi for draft 
printing, and 300 dpi for final output.

Plotter Recommendations
-----------------------
BACKGROUND COLOR:

Time Line for Windows maps all background colors on 
plotters to white in order to conserve pen ink, avoid 
possible pen damage, and save time.  This means that 
white text on a dark background will not be visible on 
plotted output.  Therefore, if you have an Time Line 
for Windows file that was initially created with 
background colors for another printing device, and you 
need to output to a plotter, choose the Print Black & 
White option on the Print dialog box to ensure that 
all your text shows up.

PAPER ORIENTATION:

It is important to note that many plotters require 
paper to be loaded in a specific orientation.  For 
example, HP 758X B series plotters require that C (as 
well as A2 metric) paper be loaded "length along 
platen," and not "width along platen," the way B and D 
size are loaded.  Refer to your plotter documentation 
for the correct information.

IMPORTANT NOTE FOR HP 758X B SERIES PLOTTER USERS:

At the time of this writing, the Windows driver for 
the HP 758X B series plotters incorrectly reverses the 
orientation for C size paper.  The driver calls for 
the paper to be loaded "width along platen," which the 
device will not allow.  Consequently, when you choose 
Portrait, you get Landscape, and vice versa.

The solution is to change the orientation of your plot 
by using the HPGL command RO, or by using the Rotate 
command on your HP plotter's console.


USING THE WINDOWS CLIPBOARD
===========================
Time Line for Windows uses the Copy Picture command on 
the Edit menu to transfer graphic images between 
Windows applications and the Clipboard.  Both a bitmap 
and a metafile are placed in the Windows clipboard.  
The application into which the graphic image is "pasted" 
reads one of the two formats.  Due to metafile format 
inconsistencies within many Windows applications, the 
bitmap format is recommended for the best results.  
Additionally, some Windows applications do not pick the 
correct format when pasting.

To OMIT the metafile format, add the following line to 
the TLWIN.INI file:

          CopyMetafile=0

If for some reason you need Time Line for Windows to 
OMIT the bitmap format and only store the metafile 
copy to the Clipboard, the following line must be 
added to the TLWIN.INI file located in your Time Line 
for Windows Sub-directory:

          CopyBitmap=0

IMPORT AND EXPORT NOTES
=======================

USING IMPORT:

The Time Line for Windows import feature allows you to 
use data from other programs.  It functions much like 
a typing shortcut, "reading" the data found in a 
spreadsheet, for example, and then "writing" that data 
into the Gantt or Resource spreadsheets.

It reads in data from files in several formats:  Lotus 
123 (.WK1), Comma Separated Variable (CSV), and Tab 
Delimited (text).  The data that is read in from a 
file is treated exactly as if you had typed the 
information into Time Line for Windows.

Therefore:

1)  The order of the data coming in must match the order 
    of the column fields of the Spreadsheet pane of the 
    active window. For example, if you try to import 
    resource names into a date column, you will receive 
    error messages.

    If Time Line for Windows reads a value from the file 
    you are importing that does not match the order of 
    data columns in the active window, it keeps a record 
    in the Import Error Log.  At the end of the import, 
    the Import Error Log box appears and tells you which 
    values were bad.  If you have a lot of these messages, 
    check your column order and try again.

2)  Some fields get recalculated, and, therefore, may be 
    different from the file from which you are importing. 
    For example, if you import a task with a start date 
    of March/15/1993, an end date of March/16/1992, and a 
    duration of 2 weeks, then Time Line for Windows 
    changes those numbers so that they make sense. Some 
    calculations depend on the order in which the data 
    was received.  The import feature always behaves as 
    if you had manually entered the data.

A few other points:

->  Time Line for Windows automatically reads 
    Time Line for DOS files.  Use "File\Open" to read 
    a Time Line file. Import will not accept these files.

->  You cannot import data into fields that you cannot 
    type into.

->  Make sure that the file format you choose matches 
    the file you want to import.

->  If you are importing text (Tab Delimited) or CSV 
    (Comma Separated Values), your Time Line for Windows 
    date format must match the format of any dates you 
    want to import. In other words if a text file has 
    "Jan/31/93" in it, you must choose "Jun/23/93" as 
    your date format in Time Line for Windows.

USING EXPORT:

Export writes data into either Lotus 123, Tab 
Delimited (also known as "text") or Comma Separated 
Variable (CSV) formats. It writes the data that is 
currently the active window's column fields.  That is 
the ONLY data that gets exported.

Therefore:

->  Schedule-wide information, like Schedule Start 
    date, does not get exported.

->  Task dependencies are not exported.

->  Resource assigments can be exported by displaying 
    those columns in the active window.  However, please 
    be aware that Resource Assignments cannot be 
    re-imported.  

->  Task dates modified by resource leveling can be 
    exported, but will be ignored upon re-import.

TIME LINE FOR DOS
=================
If you are an experienced Time Line for DOS user, 
see Appendix A, Coming From Time Line For DOS in the 
manual.  Appendix A describes differences between the 
DOS and Windows versions.  For online assistance when 
running the program, choose Time Line for DOS from the 
Help menu.

The following information explains how to use Time 
Line for Windows and Time Line for DOS together.

OPENING A TIME LINE DOS FILE:

You can open Time Line for DOS versions 3.0, 4.0, and 
5.0 files directly with the File Open command.

From the File menu choose Open, and on the Open File 
dialog box select the subdirectory where you keep your 
Time Line for DOS data files.

Specify the file name and choose the correct extension 
from the drop-down list in the Open File dialog box.

Time Line for Windows provides a message box called 
the Time Line Import Error Log that lists any problems 
that may have occurred when reading in the Time Line 
for DOS file.  More information about each message is 
given in the Help system.  To access Time Line for DOS 
specific information in the Help system, choose 
Time Line for DOS from the Help menu.

TO SPEED UP THE FILE OPEN PROCESS:

If a Time Line DOS file has many exceptions to the 
Master Calendar it may take awhile to load.

1) Use the File Open command to open the Time Line for 
   DOS file in Time Line for Windows.

2) Use the File Save As command and give the file a 
   .TLP extension to save the file as a Time Line for 
   Windows file.

3) Use the File New command to open a new file in Time 
   Line for Windows.

4) Use the File Combine command to combine the .TLP 
   file you saved in step 2.  In the Data to Combine 
   group, enable all choices.  In the Master Calendar 
   group, choose "Leave As Is".  By making this choice, 
   you are effectively replacing the Time Line for DOS 
   calendar with the default Time Line for Windows master 
   calendar (individual resource calendars are retained). 
   Click OK.

5) Use the File Save command and give the file a .TLP 
   extension to save the file with an appropriate name.

When you open the file you saved in step 5, the 
process will be much faster, since exceptions to the 
Master Calendar will be minimal.  You may want to do 
some adjustments to your Master Calendar to reflect 
the appropriate nonwork days.

CONSOLIDATING TIME LINE FOR DOS TASKS:

You can consolidate, or link to, a Time Line for DOS 
file from Time Line for Windows.  See Chapter 9, 
Managing Multiple Projects in your Time Line for 
Windows User Manual for more information on 
consolidating files and tasks.

ON TARGET
=========
Time Line for Windows can open and consolidate data 
from On Target files.  It is important for you to 
understand  that once the On Target file has been 
saved as a Time Line for Windows file, it is no longer 
readable by On Target.  Time Line for Windows can 
consolidate data from a file or task in On Target  
without changing the structure of the On Target file.

For more information on using Time Line for Windows 
and On Target together refer to Chapter 10 in the Time 
Line for Windows manual.

OBJECT LINKING AND EMBEDDING (OLE)
==================================
Following are things to look out for when using the OLE
features.

If an icon appears as a "?" in place of a Windows 
application icon, Time Line for Windows cannot locate 
the server application.  To correct this problem, edit 
the [Embedded] section of the Windows WIN.INI file with
the correct path to the application.  This problem
usually occurs with earlier versions of Microsoft Excel.

The following example, taken from the WIN.INI file,
highlights the area that you will probably need
to insert in your own WIN.INI file.

EXAMPLE:

ExcelWorksheet=Worksheet created by Microsoft Excel,
Microsoft Excel Worksheet,C:\excel\Excel.exe, picture 

IMPORTANT NOTES FOR MICROSOFT WORD 2.0 USERS
============================================
There are two known problems with Microsoft Word for 
Windows 2.0 .  Both problems occur with linked OLE 
attachments.  If you use Microsoft Word 2.0, please 
review the following material and use the OLE features 
with caution.

1.) Microsoft Word 2.0 may not exit correctly after 
    an OLE link is created.  This problem occurs when 
    linked attachments are created using the Windows 
    Clipboard and the Paste Attachment command.  This 
    problem does not occur if you create the attachment 
    using the Insert Attachment command, nor does it 
    occur with embedded attachments.

    When exiting Microsoft Word 2.0 (after creating the 
    attachment), you must answer Yes to the Save Changes 
    prompt.  Otherwise, Microsoft Word 2,0 remains in 
    memory, although you cannot see or access it.

2.) It is possible to accidently delete an attached 
    Microsoft Word 2.0 document.  This problem only 
    occurs if the attachment was created using the 
    Insert Attachment command.  This problem does 
    not occur if the attachment is created using the 
    Windows Clipboard and the Paste Attachment command.

    When you edit a Microsoft Word 2.0 attachment, 
    Time Line launches the server application, and 
    Microsoft Word 2.0 erroneously places an Update 
    command on the File Menu.  DO NOT use the Update 
    command -- Microsoft Word 2.0 deletes the file 
    from disk and you may not be able to recover it.

WINDOWS 3.0 AND WINDOWS 3.1
===========================

We recommend using Windows 3.1.  Improvements include 
faster printing, recalc and screen repaint, as well 
as increased stability.  Also, a new True Type feature 
eliminates the need for a font management program.

If you use Windows 3.0, read the following information.

WINDOWS 3.O FONT MANAGEMENT:

For best results when viewing and printing, we 
recommend that you use a font management package such 
as Adobe Type Manager (r) or Bitstream Facelift.  These 
products are easy to install, simple to use, and will 
ensure crisper, cleaner output that looks as close as 
possible to what you've chosen on screen, regardless 
of your printer type.  Also, a Postscript printer 
should provide good results either with or without one 
of these font management packages.

In Time Line for Windows, when printer fonts are 
enabled in the Format Global Defaults dialog box, the 
font list provided is from the currently active 
printer driver.  When printer fonts are disabled the 
font list is based on the Windows fonts and those in 
an active font manager.

(ATM and MoreFonts (r) can cause a problem with the 
tutorial.  Please see the  Tutorial section of this 
README.TXT file for more information.)

WINDOWS 3.O LAN AND/OR POSTSCRIPT PRINTER USERS:

If you use a parallel port on a local area network, or 
if you use a PostScript printer, it may be best to 
choose LPTX.OS2 rather than LPTX.

The reason for this, put simply, is that if you are on 
a network, or if you are using a PostScript device, 
both configurations are especially sensitive to 
unusual or unexpected variations in "handshake" 
transmission.

Selecting LPTX.OS2 allows the driver to go through the 
system BIOS, rather than write directly to the port. 
BIOS level calls are a universal standard in most 
cases, and Windows drivers, as well as Novell's 
Capture utility, or more specifically NETX.COM, are 
more likely to interpret them correctly.

The one disadvantage to using the .OS2 selection is 
that printing will not be as fast.  Therefore, you may 
need to experiment with both LPTX and LPTX.OS2 choices 
to determine which works best.  When using LPTX.OS2 be 
certain to choose LPTX.OS2 in both the printer setup 
and the network connection.

POINTERS FOR IMPROVING YOUR WINDOWS 3.0 ENVIRONMENT:

1) Set FILES=30 in your CONFIG.SYS. Thirty is more 
   than enough in most cases, and additional FILES use
   conventional memory.  Set FILES=40 if you are on a 
   network.

2) If you are running SMARTDrive, reduce the number of 
   BUFFERS to 10. If you decide to not use SMARTDrive, 
   for optimal performance set BUFFERS=32.

3) If you are running DOS version 3.3 or higher, be 
   sure to include in your CONFIG.SYS the line:
   STACKS=0,0.  This allows applications to dynamically 
   allocate STACKS as needed, saving some conventional 
   memory.

4) Don't forget to include HIMEM.SYS in your 
   CONFIG.SYS file.  Windows usually installs it for you 
   automatically.

Refer to your Microsoft Windows User's Guide for 
detailed information on optimization.

- END -
