                        CHANGE  TRACKER
                         (ReadMe file)

Contents:

I.    Introduction
II.   Installing CHANGE TRACKER
III.  Things you should know before you install (or re-install) Windows
IV.   Things you should know concerning Windows 3.xx (beforehand)
V.    Setting up CHANGE TRACKER as a DOS Application under Windows
VI.   Instructions for running CHANGE TRACKER
VII.  What gets recorded in the *.RPT files
VIII. What you should know before modifying your files yourself
IX.   Future plans for CHANGE TRACKER
X.    Registration Info, etc.






I.    Introduction

           "My system has never been the same since I installed `BRANDX,
           multi-purpose, best thing to ever hit the market,' software
           package."

      Have you ever made a similar statement?  If you're exceptionally
      blessed, you didn't completely crash, requiring the reformatting
      of your Hard drive, creating the need to start all over again from
      square one.

      Well, I got tired of making that statement over and over.  Not to
      mention the few times I DID have to start all over again from square
      one, re-installing Windows and ALL my Windows applications.  So, I
      decided to build a program that would keep me informed of what the
      creator of these applications were taking the liberty to do to my
      system, as I installed their glorious applications.  Some of them
      seemed to be assuming that I'd been reading "Windows for dummies" and
      resolved myself perpetually to the status of being a "dummy", never
      to understand my woes.  Then along comes these un-install programs
      which seemed to treat me with the same disrespect, leaving me, not
      only, never to know whatever it was that caused my problems, but
      also, never to know what fixed it after it was all over (if indeed it
      did get fixed).

      Thus, the creation of the CHANGE TRACKER program.  A program designed
      for the user who would like to graduate beyond the status of being a
      "dummy."  I hope it will help you out as well.  I believe you will be
      a better informed user in a short period of time.



II.   Installing CHANGE TRACKER

      Installing CHANGE TRACKER is a simple procedure.  You will need about
      1 1/2 meg of disk space for the program files (including the room
      CHANGE TRACKER needs to do certain file copying procedures).  Just
      place your CHANGE TRACKER diskette in the appropriate floppy drive
      and type  INSTALL  at the prompt.

        For example:

          If the copy of CHANGE TRACKER you possess is on a 5 1/4" diskette
          and the 5 1/4" floppy drive on your system is drive `A', then put
          the floppy diskette into drive `A'.  If you are not at the `A:\>'
          prompt, then type in  A:  and press Enter.  When you are at the
          `A:\>' prompt, type  INSTALL  and press Enter.

       (NOTE: CHANGE TRACKER must be installed from a floppy drive.  See
        the README.1ST file for more information.)

      Follow the on screen instructions for copying the files onto your
      Hard Drive.  If you've recently installed Windows 3.xx, and have Hard
      Disk space to spare, you may want to backup certain of your original
      WINDOWS and WINDOWS\SYSTEM files immediately following your
      installation.  You will find an option under the UTILITIES sections
      on CHANGE TRACKER's main menu that will do this for you.  (See
      section(s) below concerning WINDOWS for further information about
      backing up the original files)



III.  Things you should know before you install (or re-install) Windows

      Most everyone that uses Windows 3.xx, eventually comes to the point
      in time when something goes wrong.  Sometimes, even to the point of
      needing to Start over from square one.  If you're either just now
      installing Windows, or if your system is in such a mess that you find
      it prudent to start over from the beginning, then there's a few
      things that would be good for you to know before you begin to use the
      CHANGE TRACKER program.

      If you haven't installed Windows yet, Great!  You'll be able to start
      out fresh and monitor everything you'll be doing from the very
      beginning.  If your Windows just crashed, not so Great, but at least
      you can take advantage of the position you're now in, to take the
      precautions which may avoid that tragedy from ever happening to you
      again.  At either rate, here's a few things you'll need to know.

      If you've been previously using CHANGE TRACKER, you should also re-
      install CHANGE TRACKER.  It would be a good idea to save your old
      *.RPT files before you start.  If it becomes clear to you that you
      will not need the information contained in them later, you can always
      delete them then.

      IMPORTANT:  The first thing you need to do is to make a backup of all
      your important files.  This should include any documents you've
      saved; drawings; stylesheets; financial management files; database
      files; etc.  Any of your work!  If in doubt--back it up.

      If you're re-installing over a previous version of Windows, delete
      the old version;  Custom install the new version;  Do not allow
      Windows to search for applications on your Hard Disk.  Yes, you will
      loose your old configurations.  Also, you won't be able to access
      your Windows applications existing on your Hard Drive.  The idea is
      to re-install all of them so you can see what each installation will
      be doing to your Windows and system files.  Each application should
      likewise be completely deleted and re-installed.

      IMPORTANT: Again, Backup your files!

      When installing (or re-installing) Windows, install it as simply as
      you can.  You can do this by using the `Custom' install for Windows.

      Here's some recommended things not to do:

      Do not install your printer drivers
      Do not allow Windows to search for applications
      Do not install your video drivers (use VGA to get Windows running)
      ...etc.

      In other words:  Install Windows as `Plain Jane' as you can.  You can
      come back and add the frills later, monitoring the changes each
      project is making by running CHANGE TRACKER before and after each of
      them.

      As soon as you have a `Plain Jane' version of Windows installed, that
      would be the time to execute the ORIGINAL file copying procedure
      under the UTILITIES choice in CHANGE TRACKER's main menu.  This may
      not serve any immediate purpose, but could serve as a reference in
      the future, showing your initial Windows status before you began
      installing any programs.  Also, future version of CHANGE TRACKER may
      take advantage of these files in other comparison procedures.  So if
      you're not cramped for Hard Drive space, you should let CHANGE
      TRACKER's utility copy the original files at this point.  Backing up
      the originals should only require about another 300k if you let
      CHANGE TRACKER's utility copy them for you (CHANGE TRACKER will make
      a record of the original structure and will select and backup certain
      files which are subject to being changed).



IV.   Things you should know concerning Windows 3.xx (beforehand)

      CHANGE TRACKER is designed to monitor and keep track of the changes
      made by ANY procedure that may change your \WINDOWS files (3.xx);
      \WINDOWS\SYSTEM\ files; and your AUTOEXEC.BAT and CONFIG.SYS files.

      While it's obvious--the greatest benefit will be obtained while
      tracking the installation of your new Windows programs, it's also
      important to run the BEFORE and AFTER procedure when doing seemingly
      less significant procedures.  Don't be reserved about it--thinking
      you're saving a lot of Hard Drive space.  Once CHANGE TRACKER's
      initial 1 1/2 meg or so of Hard Drive space is taken up, running the
      BEFORE and AFTER procedure to monitor a procedure only takes an
      average of about 6k for the single file in which that particular
      project's changes are stored.  Keep in mind, once you do a procedure,
      and you don't know what it did to your system, reversing the
      procedure can sometimes be very difficult.  Even the expensive un-
      install utilities will not undo everything you do to your system, and
      many of them do not report to you what they've done.  So you don't
      know what broke it, and you don't know what fixed it (if it indeed
      does get fixed).

      At the risk of sounding like a broken record--please keep in mind
      when running CHANGE TRACKER, it's VERY IMPORTANT to run the BEFORE
      file copying procedure IMMEDIATELY Before, and to run the AFTER file
      copying procedure IMMEDIATELY After, the procedure being monitored.
      I recommend running the AFTER file copying procedure (the final step
      of monitoring a project) prior to exiting Windows, rebooting, running
      the program you've just installed, or doing anything else for that
      matter.

         Again:  This time at the risk of sounding sarcastic, let me give
         you Webster's definition of IMMEDIATELY:  "without interval of
         time : without delay : without the intervention of another
         object."

         ...There! Now that I've risk our friendship, please keep in
         mind who the beneficiary is:  IT'S YOU!  It's your system!
         It's your time!

      Now let me explain a little further.  Let's say you run the BEFORE
      file copying procedure.  Then you install this certain very special
      program you've been saving for six month to buy.  After your done
      installing it, you can hardly wait to see what it's gonna do.  So,
      your mind is diverted and you involve yourself with two hours of
      reading the manual, learning the new program, getting all the good
      ole hands on, etc.  Alas, since the hairy monster was just about to
      discover you in the cave, you decided to save it where it was, sleep
      on it, and make your attack at some later date.  So, to make this
      long story short, you forgot to run the AFTER file copying procedure.
      Three days later you remember, so you run the AFTER file copying
      procedure.  Meanwhile: your brother tried out a different video
      driver; your wife installed her new recipe program; and who knows
      what else went down.  Well, there you have it!  Running the AFTER
      file copying procedure now will record for you ALL the various
      changes of each one of these events.  It's up to you now to figure
      out what changed what.  However, don't take what I've just said as a
      reason not to run the AFTER file copying procedure at this point.
      Not at all!  Run it!  You're still much better off than you normally
      would have been without CHANGE TRACKER's Report file.  And besides,
      you'll need to run the AFTER file copying procedure before you can
      run your next BEFORE file copying procedure anyhow.



V.    Setting up CHANGE TRACKER as a DOS Application under Windows

      It makes good sense to set up CHANGE TRACKER to operate as a DOS
      application under Windows, rather than having to run it under the DOS
      window (CHANGE TRACKER is not a Windows application).  If you're a
      new Windows user, the below paragraph is a brief explanation of how you
      may do this.

      Under `Program Manager,' click on the `File' option.  Now click on
      `New.'  Make sure the circle next to `Program item' has a black dot
      in it and click on `OK.'  On the `Description:' line write  CTRACKER.
      Press the tab once to move cursor to the line below.  On the `Command
      Line:' type in your full path to CTRACKER.EXE.  If you used the
      defaults when installing it, it would be: C:\CTRACKER\CTRACKER.EXE.
      Click on `OK.'

      Now when you're monitoring the changes made when installing a Windows
      application, just click on your CTRACKER icon; run the BEFORE file
      copying procedure; Holding the ALT key down, press TAB (to return to
      the Program Manager); install the program; Holding the ALT key down,
      press TAB again (to return to the CHANGE TRACKER program); run the
      AFTER file copying procedure; and you're done.  You can immediately
      view your *.RPT file to see all the changes made.  Instantly, you'll
      discover that, it is much better to be informed?



VI.   Instructions for running CHANGE TRACKER

      The installation procedure of CHANGE TRACKER places a batch file on
      the root of C:\> named  CT.BAT  (unless you already have a batch file
      by that name there.  The INSTALL will not overwrite a pre-existing
      one by the same name).  To run CHANGE TRACKER from the C:\> drive,
      simply press  CT  and Enter.  Or, you may run CHANGE TRACKER the more
      traditional way by changing the current directory to \CTRACKER (or
      whatever you named it when installing CHANGE TRACKER); then typing
      out  CTRACKER  and pressing Enter.  Once CHANGE TRACKER is executed,
      the menus are self evident of what each option will do.

      When monitoring the installation of a Windows Application, it is
      recommended that you run the AFTER file copying procedure immediately
      following the installation  (i.e.-before you exit Windows, reboot, or
      run the program just installed, etc.).

      After you've completed monitoring a project (i.e.-running the BEFORE
      file copying procedure before it, and running the AFTER file copying
      procedure after it), the changes of that particular project will be
      saved in a file which you will have been given the occasion to name
      during the procedure.  You should name each project file something
      easy for you to identify later.  For example:  if you're monitoring
      the changes made which installing a program named "BESTRATE" might
      make, you would probably want to name the file "BESTRATE."  The file
      will be saved on your Hard Drive as \CTRACKER\REPORTS\BESTRATE.RPT.
      For more information on this: read the below section `What gets
      recorded in the *.RPT files.'  (NOTE: \CTRACKER might be a different
      name if you chose to rename the default directory when you installed
      CHANGE TRACKER to your Hard Drive).



VII.  What gets recorded in the *.RPT files

      During your BEFORE and AFTER file copying procedures, you will be
      given the opportunity to name each file in which each of your
      monitored projects will be recorded.  These files will automatically
      be given the extension *.RPT.  You may view (or print) any of your
      *.RPT files under the VIEW / PRINT... option from the main menu.
      Each one of these files will contain the pertinent information
      showing what that particular project changed in your Windows and
      System files.  These will be:

         - A header identifying your project name
         - The date & time both before and after your project
         - New files added to the \WINDOWS directory.
         - New files added to the \WINDOWS\SYSTEM directory.
         - Display of all files that changed in \WINDOWS.
         - Display of all files that changed in \WINDOWS\SYSTEM.
         - Comparing of all *.INI files in \WINDOWS.
         - Comparing of all *.INF files in \WINDOWS\SYSTEM.
         - Comparing AUTOECEC.BAT (before & after)
         - Comparing CONFIG.SYS (before & after)

      You should observe the time and date of your file when viewing (or
      printing) it.  There should only be a matter of a few minutes between
      the time before and the time after.  If not, you may have delayed
      running the AFTER procedure, which would indicate that you may be
      monitoring more that one project event.

      The NEW files added to the \WINDOWS and the \WINDOWS\SYSTEM
      directories are shown (giving their filespecs only).  Even the new
      *.INI and *.INF files have ONLY their filespecs shown (i.e.-not the
      contents).  You may view them in any text editor to see their
      contents.  If any programs later should changes the contents of any
      of these Newer *.INI or *.INF files, any of those CHANGES will then
      be recorded in your *.RPT file at that time (in addition to any of
      the changes made in any of the original *.INI and *.INF files).  Keep
      in mind that some programs, when changing a particular file, make a
      backup of the file(s) they've changed.  For example: if a kind
      hearted programmer is changing a couple of lines in your WIN.INI
      file, he may make a backup of the original WIN.INI renaming it
      something like WIN.I~I.  In which case, CHANGE TRACKER will report
      the newly named file WIN.I~I as a newly added file.

      CHANGE TRACKER will also record in the *.RPT file any existing
      file(s) which have changes of any sort (even if only the date or time
      changes).  For example:  a programmer may simply open a file, check
      to see if that particular file has a line or two configured in such a
      way that he deems important, then save the file unchanged if he is
      satisfied.  This will result in a file which only changed in its
      filespecs and not its contents.  Even these changes (as well as any
      changes in content) are reported as files that changed in your *.RPT
      file.

      When comparing the *.INI and the *.INF files, CHANGE TRACKER will
      record in your *.RPT file, not only the filespecs, but the changes in
      the contents as well.  You will see lines numbers to the left of the
      lines that have changed.  This will better assist you, should you
      need to search the location of the changed lines in the file.  You'll
      notice that the first line and the last line of each comparison
      section do not have any changes in them.  These top and bottom lines
      are only displayed to help your navigation in finding the ones which
      did change.

      Your *.RPT file also shows any changes made in your AUTOEXEC.BAT and
      CONFIG.SYS files.  You should be aware that editing these files
      yourself could result in temporarily crashing your system, preventing
      you from being able to boot up again.  However, don't be afraid,
      running the risk of being labeled a "dummy" by the next book author,
      . . . Jump in!  It is wise, however, to know and take some
      preliminary precautions before beginning to make adjustments to these
      files yourself.  For further information on editing these files: see
      the, "What you should know before modifying your files yourself"
      section below.

      Finally, you may notice a couple of Report files that you didn't
      create in the CHANGES\REPORTS directory named  ~~DLLADD.RPT  and
      ~~DLLUPD.RPT.  These are special files which will be recording all
      your DLL file activity from now on.  If you start all over again
      (i.e.-loading Windows and Windows applications from square one), you
      should also re-install CHANGE TRACKER.  When CHANGE TRACKER is re-
      installed, you will be given the opportunity to write over these
      files, allowing you to start over again anew.  (NOTE: You may want to
      save your old *.RPT files {including ~~DLLADD.RPT and ~~DLLUPD.RPT}
      before you start over anew).



VIII. What you should know before modifying your files yourself

      It is wise take some preliminary precautions before beginning to make
      adjustments to your AUTOEXEC.BAT and CONFIG.SYS files yourself (or
      any other important files).  Here's just a few pointers that may help
      you if you're somewhat of a novice user (isn't "novice" better that
      "dummy?").

      First make a bootable diskette:

       To do this:
        - Place a blank diskette into Floppy drive A:
        - At the C:\> prompt type:
            FORMAT A: /S  (and press Enter)

      Now, in the event that you can't reboot your system from Drive C:\>,
      you can put the bootable floppy into drive A: and reboot.

      You also should make a backup on your Hard Drive, a previously good
      AUTOEXEC.BAT and CONFIG.SYS.  I like to name each with the current
      date so that if I get a few of them on C:\> root, I'll be able to
      distinguish the earlier ones from the last one.  Below would be an
      example of what you may want to do:

         COPY C:\AUTOEXEC.BAT C:\AE052795.BAT
         COPY C:\CONFIG.SYS C:\CF052795.SYS

      (Both the above are, of course, assuming that the current date is May
      27, 1995.  {I thought I'd just mention that incase we're in the
      process of converting a "dummy" into a "novice" here.  Ha!})

      Now, if you get in any trouble, all you have to do is boot up with
      the bootable floppy, then reverse the procedure with:

         COPY C:\AE052795.BAT C:\AUTOEXEC.BAT
         COPY C:\CF052795.SYS C:\CONFIG.SYS

      Substituting, of course, whatever date may apply--Then, reboot from
      your hard drive again.



IX.   Future plans for CHANGE TRACKER

      Intended are the following:

         - Automatic Relocation of Windows application to another Drive
           location (i.e.-from Drive D to Drive E -- useful when you change
           Hard Drives, etc.)

         - A User informing Un-Install (not for "dummies")

         - Comparison of your current Windows condition to the original,
           & certain optional reversal functions.


      Feel free to write, suggesting any other features you would like to
      see in CHANGE TRACKER when you register.



X.    Registration Info, etc. (ShareWare)

      ALL RIGHTS RESERVED!
      Unregistered Copies Require Registration after 30-day Evaluation!

      UNMODIFIED copies of CHANGE TRACKER may be distributed for evaluation
      ONLY provided no payment, commercial benefit or other consideration is 
      received.  This package may NOT be combined with any other product 
      without explicit written permission!

      Registration:  $12.00

      Send check or money order to:

           APEX VISIONS
           1810 Magnolia
           Port Neches, TX. 77651


      Your registration will be stored in a database, and you will be
      informed of any future upgrades.  Be sure to send your name and
      address (printed or type written) when you register your copy.

      Any request concerning problems or questions may be sent in one of 
      the following three ways:

        1.  mail:  the registration address shown above
        2.  fax:  (409)-724-6959
        3.  email:  moseleydp@bigred.lamar.edu

      Be detailed/specific of all aspects of the problem(s) you are having.

      Thank you for using CHANGE TRACKER.








     *** (END OF FILE) ***
