Hamilton C shell(tm) Installation 2.2.106 for OS/2.
Copyright (c) 1988-1996 by Hamilton Laboratories.  All rights reserved.


This file describes how to install Hamilton C shell on your system.  We
suggest a basic installation initially but once you've gained some
familiarity with the C shell, you may want to set it up as the default
command processor for OS/2, completely replacing cmd.exe.  (The advantage
to be gained by installing it as the default command processor is that
the C shell will then be able to change its title bar and icon.)

If you have problems, please contact us for help.  We can be reached as
follows:

         phone:   508-440-8307
         FAX:     508-440-8308
         Email:   hamilton@hamiltonlabs.com
         Web:     http://www.hamiltonlabs.com


When you've finished the installation, please mail in or FAX the registration
form.  This lets us know who you are so we can send updates and your feedback
helps us to better meet your needs in the future.

Please refer to the file readme.too for additional release notes.


System Requirements:

   Installation requires a 286, 386 or 486 or greater AT(R) or
   PS/2(R) or compatible, running OS/2 1.1 (Presentation Manager)
   or Microsoft SDK 1.06 or later.  Roughly 1.6 MB of disk space
   is used.

   Hamilton C shell and the utilities supplied with it fully
   support HPFS and long filenames when running under OS/2 1.2
   or later. They will work properly in a Presentation Manager
   text window or full-screen and with networks such as LAN
   Manager or IBM LAN Server.  If you're using OS/2 2.0 or 2.1,
   it knows how to run 32-bit applications and start up Multiple
   Virtual Dos machines.  The product is not copy protected.


Installation on OS/2:

   The first few steps, copying files from diskette to your
   hard disk and modifying your config.sys, are the same on all
   releases of OS/2.  The remaining steps -- those associated
   with actually installing Hamilton C shell on your OS/2
   desktop -- depend on which release of OS/2 you're running.
   We suggest a "vanilla" installation initially, but later
   you may want to customize it to your own tastes.  For help
   with that, read the chapter on "Customizing the Shell"
   in the manual.

   Once you've gained familiarity with both OS/2 and with the C
   shell, you may want to set up the C shell as the  default
   command processor for OS/2, completely replacing cmd.exe.
   The advantage to be gained (except under the 6.167 Beta and
   LA builds of 2.0) is that the C shell will then be able to
   change its own title bar and icon when you run an external
   command.


Basic Installation, Part I  (All releases of OS/2):

   1. Copy the bin and samples directories and other files on these
      diskettes to your hard disk, putting them anywhere you like.
      Most customers create a directory in the root of one of their
      drives called "hamilton" to hold everything.


   2. Copy the login.csh and startup.csh files into any directory you care
      to designate as your "home" directory.  The significance of a home
      directory is principally that it will be convenient to specify
      pathnames relative to this directory.  Most users treat the home
      directory as a place for all their personal files and subdirectories
      and give it their own first name, e.g., C:\DOUG.


   3. Edit config.sys:
   
      a. Add the ".", bin and samples directories to the beginning
         of your search path.
         

      b. Add statements to define the HOME directory you've chosen
         and to ensure you're configured for a sufficient number of
         threads.  (The default number of threads is too small
         if you expect to have lots of windows open.  Also, be
         sure your PATH explicitly lists ".", the current
         directory.

      c. You may also want to include definitions for TABS and
         COLORS.  more.exe and some of the other utilities look
         for TABS to see if you want them to display text with
         tabs expanded out to something other than the default
         of every 8 characters.

         By default, the C shell displays white characters on a
         black background.  The COLORS variable lets you choose
         something different from this set:  black, red, green,
         yellow, blue, magenta (or blue red), cyan (or blue
         green) and white.  Foreground colors may also be
         bright, dim, blink or reverse.  The keyword "on"
         introduces background colors.  (Blink only causes true
         blinking full-screen; in a text window, it just makes
         the background brighter.  Also, yellow is a true yellow
         only if it's bright.  These are OS/2 limitations not
         related to the C shell.)  For more information on setting
         screen colors, please refer to the customization chapter
         or to the colors.csh file in the samples directory.
         
         Here's an example of what you might add to config.sys:
         
            SET PATH=.;C:\HAMILTON\BIN;C:\HAMILTON\SAMPLES;C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;
            THREADS=255
            SET HOME=D:\DOUG
            SET TABS=3
            SET COLORS=WHITE ON BLUE
            
         (Please be sure your config.sys file contains only
         upper-case alphabetics, no lower-case, if you're using
         OS/2 1.  1. Lower-case alphabetics were known to cause
         random OS/2 system failures in that release of OS/2.
         This was a known bug in the OS/2 kernel and was not
         application dependent.)


   4. Edit the login.csh and startup.csh files, customizing them to
      meet your needs.  If you're new to the C shell, you'll probably
      want to get started by just accepting them the way they came,
      but experienced users may want to add their own aliases, etc.

      Unless you're convinced that you've set all your environmental
      variables in your config.sys (and that your PATH explicitly
      lists ".", the current directory), use the dumpenv utility
      to paste a series of setenv statements into the login.csh file
      to recreate the environment you've been using with cmd.exe:

         dumpenv >>login.csh

      (To see what dumpenv does, look at the source code in
      the samples directory or simply run dumpenv without
      redirecting the output.)

      The remaining steps depend on which release of OS/2
      you're running.


Basic Installation, Part II  (OS/2 1.1):

   5. Add csh.exe with the title "Hamilton C shell" to the
      "Start Programs" menu.  To do this, pull-down
      "Program" and select "Add..." from the menu bar.

      Fill in:

            Program title....   Hamilton C shell
            Path and file name  ....as appropriate....\csh.exe
            Parameters....      -L

      The "-L" part tells csh.exe when it starts up that
      it's a "login" shell, which means it should look for
      a login.csh file. (Refer to page (?) for additional
      information on other options.)

   6. You will likely want to create a second entry for
      running full-screen. It's more convenient if you're
      mostly working with applications that only run full-
      screen or if you want faster text display, especially
      scrolling.  To do that, from the "Start Programs"
      menu, pull-down "Program" and select "Copy..." from
      the menu bar.  In the Copy Programs popup, fill in the
      following and push the "Copy" button:

            Change Title to:    Hamilton C shell -- Full
            Screen

      Back in the "Start Programs" window, select the new
      full screen title, pull-down "Program" and select
      "Change...".  In the Change Program Information
      popup, push the "Change" button.  This brings up the
      How to Run the Program popup; select "Run the program
      full-screen" and "Enter".

   7. Reboot your system before starting Hamilton C shell for
      the first time.  This causes the new statements in
      config.sys to take effect.


Basic Installation, Part II  (OS/2 1.2 or 1.3):

   5. Add csh.exe with the title "Hamilton C shell" to the
      "Group - Main" menu.  To do this, pull-down
      "Program" and select "New..." from the menu bar.

      Fill in:

            Program title:      Hamilton C shell
            Path and file name: ....as appropriate....\csh.exe
            Parameters:         -L

      The "-L" part tells csh.exe when it starts up that
      it's a "login" shell, which means it should look for
      a login.csh file. (Refer to page (?) for additional
      information on other options.)

   6. You will likely want to create a second entry for
      running full-screen. It's more convenient if you're
      mostly working with applications that only run full-
      screen or if you want faster text display, especially
      scrolling.  To do that, from the "Group - Main" menu,
      pull-down "Program" and select "Copy..." from the
      menu bar.  In the Copy Programs popup, fill in the
      following and push the "Copy" button:

            Change Title to:    Hamilton C shell -- Full Screen

      Back in the "Group - Main" window, select the new
      full screen title, pull-down "Program" and select
      "Properties..." .  In the Properties popup, push the
      down arrow next to the "Program Type:" box and select
      "OS/2 Full Screen" on the list that will appear and
      then push the "Change" button.

   7. Reboot your system before starting Hamilton C shell for
      the first time.  This causes the new statements in
      config.sys to take effect.


Basic Installation, Part II  (OS/2 2.x):

   5. Open the Templates folder and drag a program object to
      the desktop (or another folder) by pressing and holding
      the right mouse button as you drag.  On the Program
      page of the "Program - Settings" window that will
      appear, fill in:

            Path and file name: ....as appropriate....\csh.exe
            Parameters:         -L

      The "-L" part tells csh.exe when it starts up that
      it's a "login" shell, which means it should look for
      a login.csh file. (Refer to page (?) for additional
      information on other options.)

   6. On the Window page of the Settings, you will probably
      want to set

            Minimized button behavior:  Minimize window to
            desktop

            Object open behavior:  Create new window

      Doing this will let you conveniently open up lots of
      copies of the C shell as needed.

   7. On the General page of the Settings, set

            Title:              Hamilton C shell

      Close the Settings by pressing Alt-F4.

   8. You will likely want to create a second entry for
      running full-screen. It's more convenient if you're
      mostly working with applications that only run full-
      screen or if you want faster text display, especially
      scrolling.  To do that, copy the C shell icon you just
      created by right-clicking on it and selecting
      "Copy..." and then choosing an appropriate
      destination folder (probably the desktop) for the copy.
      You can also copy the icon by pressing and holding the
      Ctrl key while dragging with the right mouse button.

   9. Once you've made the copy, right-click on it and select
      "Open" and then "Settings".  On the "Session"
      page, select "OS/2 full screen".  Then go to the
      "General" page and type a new title:

            Title:              Hamilton C shell
            Full Screen

      Close the Settings window for the copy by pressing Alt-F4.

  10. Reboot your system before starting Hamilton C shell for
      the first time.  This causes the new statements in
      config.sys to take effect.


Installation as the Default Command Processor:

   The C shell can also be installed as the default command
   processor OS/2 protected mode, meaning you specify it, not
   cmd.exe in your config.sys.  The principal advantage is that
   when the when the C shell is run as the default command
   processor, PM allows the C shell to change its own title bar
   and, under OS/2 1.3 or 2.0 (but not the 6.167 Beta or LA
   builds), its own icon to show what it's running.  This can
   be quite helpful if you have lots of copies of the shell
   running minimized and would like to know what each one is
   doing.

   The disadvantage is that the installation is slightly messy
   and it does disable cmd.exe's ability to change its title
   bar and icon.  For these reasons, most users will want to
   wait until they've gained some familiarity with the C shell
   and with OS/2 before installing it this way.

   To install the C shell as the default command processor,
   follow the instructions for the basic installation but then
   make these changes, as appropriate for your system:



Default Command Processor Installation Procedure  (OS/2 1.2 or 1.3):

   1. Edit the PROTSHELL line in your config.sys, replacing
      the pathname and any parameters for cmd.exe
      (remembering what they were) with the pathname for the
      C shell and a -L (login) parameter.  The resulting line
      should look something like this:

         PROTSHELL=C:\OS2\PMSHELL.EXE C:\OS2\OS2.INI C:\OS2\OS2SYS.INI C:\OS2\BIN\CSH.EXE -L

   2. Change the pathname you specify for the C shell in
      Start Programs or Group-Main to * (an asterisk).  Also,
      change the parameters line to be either blank (1.1 or
      1.2) or (1.3):

            /K "%*"

   3. Change the entries (probably named "OS/2 Window" or
      "OS/2 Full Screen") in Group-Main or Start Programs
      for cmd.exe to fill in the complete pathname for
      cmd.exe instead of an asterisk.  Set the parameters to
      whatever you had specified following the pathname for
      cmd.exe (if anything) in your config.sys before
      changing it in step 1.

   4. Change any entries in any of your program groups which
      invoke .cmd scripts to run them via cmd.exe explicitly.
      For example, if you had an entry that specified the
      program "c:\myapp\foo.cmd", change that to:

            Path and file name:  c:\os2\cmd.exe
            Parameters: /C c:\myapp\foo.cmd ...any additional
            parameters...

   5. Reboot.


Default Command Processor Installation Procedure  (OS/2 2.x):

   1. Edit your config.sys to set OS2_SHELL to point to the C
      shell, specifying the -L (login) option, e.g.,

            set  OS2_SHELL=c:\hamilton\bin\csh.exe -L

   2. Modify the Settings for the OS/2 Window and OS/2 Full
      Screen icons to show the full path for cmd.exe (e.g.,
      "c:\os2\cmd.exe") rather than an asterisk on the
      Program page.

   3. Modify the Settings for the Hamilton C shell icons to
      specify an asterisk pathname (meaning the default
      shell), deleting any mention of any startup parameters
      and explicitly specifying the C shell icon rather than
      the default icon:

      a. Right-click on the icon and open the Settings.

      b. On the Program page, set

               Path and file name: *
               Parameters:

      c. Select "Find..." next to the icon display.

      d. Select "Locate" on the Find screen.

      e. Select the "Path" page on the Locate Folder
         screen.

      f. Type the pathname of the directory containing the
         C shell's csh.ico icon file.  (E.g., "c:\hamilton\bin".)

      g. Press the "OK" button on the Locate Folder
         screen.

      h. Type "csh.ico" in the Name field on the Find
         screen.

      i. Press the "Find" button.

      j. The Find Results screen should appear with the C
         shell icon highlighted.  Press the "OK" button.

      k. Back in the General Settings screen, you should
         now see the C shell's icon.  Press Alt-F4 to close
         the screen.

   4. When you reboot, the C shell will be the default shell
      and it will appear with its correct icon both for
      starting and when you minimize it.
