   Welcome to the international community of Project
 Scheduler users.  You have joined an extraordinary network
 of management professionals who use Project Scheduler to
 organize their project management activities; from planning
 and tracking to analyzing and reporting. Project Scheduler
 6 for Windows, the latest addition to Scitor Corporation's
 series of award-winning project management software, will
 provide you with a rich array of unique features. Please
 take a moment to fill out your Registration Card.
   The Project Scheduler 6 (PS6) documentation consists of a
 Reference Manual, a User's Guide, and a Tutorial Manual, as
 well as an on-line context-sensitive Help system.  Even if
 you prefer to learn the program without following
 instructions in a book, you may still wish to read through
 the "Orientation" section in the User's Guide.  It provides
 a quick introduction to PS6.
   Thank you for purchasing Project Scheduler 6 as your
 project management software tool.  Please give us a call
 at (415) 570-7700 if you would like more information on any
 of Scitor's products or services.  We look forward to
 hearing from you.

   This file, README.TXT, is copied into your PS6 directory
 when you run the SETUP program.  You may wish to print out
 and read the following technical notes in greater detail
 once you have become more familiar with PS6.  They discuss
 the Windows Program Manager options you can use to
 maintain standard company formats.


               MAINTAINING CONSISTENCY

   If you intend to share PS6 files with other users, you
 will find that consistency across machines can be
 advantageous.  It is quite easy to set up your program
 so that all users start with a consistent set of formats
 for charts, graphs, and reports.  In order to do this
 effectively, you need to understand the roles played by
 configuration and preference files.



               PS6 CONFIGURATION FILES

   PS6 uses several different files to store program setup
 information.  These include calendar (.CAL), preference
 (.INI and .PRF), filter (.FLT), formula (.FRM), report 
 (.RPT), header/footer (.HF), graph (.GRF), and batch 
 processing (.BCH) files.

   These files will typically be loaded and saved
 automatically by PS6, but you will have a considerable
 amount of control over this process, using another type
 of file, the configuration (.CFG) file.

   The PS6.CFG file contains a list of the various files
 that were active when PS6 was last exited, and upon
 startup the program will load each of those files.  If
 you wish, you can override those files by specifying
 different file names on the command line (in the Program
 Item Properties in the Windows Program Manager).

   For instance, you could change a command line of
 "C:\PS6\PS6.EXE" to "C:\PS6\PS6.EXE G:\PS6\COMPANY.CAL",
 ensuring that you always start up with the company
 calendar defined on your network G: drive.  Even if you
 worked with a different calendar file the last time you
 ran PS6, this option will force the retrieval of the
 COMPANY.CAL file. 

   Another option is to create your own configuration
 (.CFG) file that contains a special list of files to
 open upon startup.  If you place this configuration file
 on your network, (for instance, "G:\PS6\COMMON.CFG") and
 change each user's Program Item Properties to refer to
 that file with an '@' sign (for instance, changing
 "C:\PS6\PS6.EXE" to "C:\PS6\PS6.EXE @G:\PS6\COMMON.CFG"),
 you can ensure that everyone will always start up PS6
 with the same set of files.  You can even make these
 files read-only to ensure their security.

   Finally, if you have a large number of projects that
 you typically work on, and find it tedious to open all
 of them using the standard File Open dialog box, you can
 specify the names of those files in the command line or
 configuration file, and they will be automatically
 opened upon startup.  This is in contrast to the "Work
 On Last Project" option in the Welcome Dialog Box (see
 page 2 of the Reference Manual), which will only open the
 most recently used project.  If you have retrieved one or
 more projects in this way, the Welcome Dialog Box will
 not appear.


                PS6 PREFERENCE FILES

   PS6 uses three types of preference files: binary user
 preference (PS6.INI), text user preference (any other
 .INI), and company preference (.PRF) files.

   Any file named "PS6.INI" is a binary user preference
 file.  It is stored in a compact binary format, allowing
 rapid retrieval upon startup and rapid saving upon exit.
 You should NOT try to edit this file.

   Any file with a (.INI) extension that is NOT named
 "PS6.INI" is a text user preference file.  This is slower
 to retrieve and save, but is in a text format, allowing
 you to edit and combine these files for precise control
 over preferences.  You can specify several of these files
 in a configuration file or on the command line (see PS6
 CONFIGURATION FILES above).  For instance, you might
 want to automatically retrieve files called GANTT.INI,
 NETWORK.INI, and PRINTING.INI so that you always start
 with the same format.

   Company preference files, those with a (.PRF) extension,
 are very similar to text user preference files, except
 that they can be password-protected.  If you do not know
 the password, you will not be allowed to save to the .PRF
 file.

   If you wish to provide PS6 consistency across your
 entire organization, you may wish to put a carefully
 created file called COMPANY.PRF (for example) on your
 network, and have everyone load this preference file upon
 startup (see PS6 CONFIGURATION FILES above).  Users
 will be able to make changes to settings while inside the
 program, if they wish to customize their own printouts,
 but PS6 will always contain the company-standard settings
 upon startup.

   If your PS6.INI file resides on the network, you may
 find that opening (upon startup) or saving (upon exit)
 this file takes considerably longer than if it resided on
 your hard drive.  This is due to the delay involved in
 network read/write operations, compounded by the
 incremental nature of preference file operations.  Even
 if all other files reside on the network, you may wish to
 keep your PS6.INI file stored on your hard drive.  You can
 accomplish this by explicitly loading this file in your
 command line or configuration file (see PS6 CONFIGURATION
 FILES above).



 