HPFS386 INSTALLATION UTILITY

  This program allows you to install the HPFS386 feature of OS/2 Warp Server
  for e-business without first having to install the IBM Network Products 
  Installer, or perform a manual CID installation.

  This is particularly useful on eComStation systems, where the IBM installer
  is not present on the system.

  To install HPFS386:

    1. Insert the OS/2 WSeB '386 HPFS Upgrade' CD into your CD/DVD drive.

    2. Place HFSINST.* into some temporary directory.

    3. Run HFSINST.EXE (you must have VROBJ.DLL installed on your system).

    4. Select the desired options (see the online help for details) and 
       then select 'Install'.

    5. (Recommended) Edit CONFIG.SYS and add a call to CACHE386.EXE (see
       note under 'LIMITATIONS', below).

    6. Reboot.  CHKDSK may run on your HPFS drives; this is normal.


LIMITATIONS

  The configuration options offered by the installation GUI are somewhat 
  limited.  You may want to adjust the configuration to your satisfaction by 
  editing the HPFS386.INI configuration file after installation.

  In particular, both the cache and heap size settings are limited to 64 MB 
  by the GUI.  This was done because the development environment used (VX-REXX)
  provides no method of querying the amount of installed memory, and thus there
  is no way to set these limits intelligently.  In addition, I have observed 
  problems on some systems when setting the cache size in particular to a larger
  value.  Again, you can edit HPFS386.INI after installation to change the cache
  and heap sizes.

  This program simply calls the HPFS386 CID install process, and therefore it 
  does not perform any configuration beyond what that installer allows.  In
  particular, the CACHE386.EXE program will not get added to your CONFIG.SYS 
  file automatically.  

  -=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-
  I STRONGLY RECOMMEND that you add this line to CONFIG.SYS after installation:

      CALL=C:\IBMLAN\NETPROG\CACHE386.EXE

  where C: is your boot drive.  This should generally be the first CALL 
  statement in the file.
  -=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=--=-=-=-=-=-


CAVEATS

  In my experience, very few people can agree on what constitutes 'good' 
  settings for cache and heap size.  Personally, I prefer a cache size of
  64 MB (on a system with 256 MB or more), and no limit on heap size.

  I once read a suggestion that setting the heap size limit to the same as
  (or less than) the cache size can avoid some vaguely-specified problem(s).  
  I've never seen any evidence that this is necessary, but I'm not an expert.

  I have experienced problems in setting the cache size larger than 64 MB.  In
  particular, when trying it on my AMD Athlon64 box (1 GB of RAM), I got a
  strange error claiming that the system was out of memory.

  Another problem (also on the Athlon64), was that the system trapped on boot
  if I failed to run CACHE386.EXE from CONFIG.SYS.  Maybe this was a one-time
  fluke, but the problem has not reappeared since I added the CALL statement.


LICENSE

  This program is (C) 2005 Alex Taylor.

  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions are met:

   1. Redistributions of source code must retain the above copyright notice,
      this list of conditions and the following disclaimer.
   2. Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
   3. The name of the author may not be used to endorse or promote products
      derived from this software without specific prior written permission.

  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
  BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
  IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
  POSSIBILITY OF SUCH DAMAGE.

