Included on this disk is the new version of the device driver that enables
utilize the fat file system to format both 512 and 1024 media fat.

AN IMPORTANT NOTE FOR ALL USERS OF HPOFS20.IFS version 2.0-2.44nt--If you intend
to transport cartridges to a machine with a previous version of HPOFS you
will need to issue a chkdsk before you demount the cartridge.  This is due
to the new atomic directory update--you will need to this before migrating
a cartridge to a machine with an older version of HPOFS--if you do not issue
a chkdsk the cartridge may become logically write protected and you will
be unable to write to the cartridge.  If this should happen you may reformat
the cartridge.

Also be aware that occasional hangs conditions in OS2/2.1 can leave an hpofs
disk in a unwanted state if this happens to occur while the file system is
updating the freefile--on previous versions this occurance resulted in the user
getting back a message -unable to access disk.  Then in order for the user
to be able to retrieve his files he was required to send his cartridge to us
and with the use of some internal tools we recovered his files.  We now
(from version 2.21nt on) check for this condition and if it exists, we will
logically write protect the cartridge and set freespace available to 0 bytes.
This allows the user to have access to his files, copy them to another disk,
then reformat the media to remove the logical write protect.

Also the first time a cartridge is migrated to a machine with the new HPOFS20
you will notice that a dir or chkdsk will indicate you have less freespace
on the cartridge.  For 5.25" media 1 meg is allocated for the atomic directory
structure, for the 3.5" 128 K is allocated.  This is in addition to the 1% of
the media size that is allocated initially for the system area of the disk.


*******************************IMPORTANT******************************
1) If you are using OS2/2.1 (the first version of 2.1)please change to your
OS2 directory and check the date of FORMAT.COM -- if it is before 6-1-93 6:44am
please back it up by renaming it to FORMAT.ORI and copy FORMAT.COM from this
disk.  If your version is a later date do not use the format.com from this
disk.  If you should have any problems with formatting please read and install
the proper dll's as outlined in the Guide to Operations High Performance Optical
File System document.  If you continue to have problems and have checked to
see that all necessary DLL's have been installed and are listed in the LIBPATH
statement of your CONFIG.SYS, call the OS2 hot line at 1-800-992-4777.
************************************************************************


2) The FORMAT and CHKDSK pulldowns in the Drives icon from the OS/2 Work Place
Shell are not currently supported for HPOFS.  You may also notice that the
icon for the optical drive is not correct and this problem has been reported to
OS2.

3) Since accessing optical media is slower than accessing hard disks, you may
want to perform long xcopy operations (such as copying a harddisk) at a time
when you are not utilizing your system for other operations.

4) When verifying that files have been copied, it is recommended that you remove
the media from the drive and then reinsert the media before doing a dir of the
disk--this is to make sure that we read the directory entries from the media and
not from the cache.  It also verifies that the cartridge has not been corrupted
as described above.



This file is for those who don't want or care to read the HPOFS script file.
It is intended to get you up and running with minimum work.

The files sent are:
                   mo.sys         (for MO drives current version 2.38c)
                   mo001.msg      (message file for mo.sys)
                   hpofs20.ifs    (IFS for OS2 version 2.1)
                   uhpofs.dll     (Format and chkdsk code for hpofs)
                   dbcs3395.dll   (support for DBCS code pages)
                   fmt001.msg     (message file for uhpofs.dll ENGLISH)
                   fmtenu.msg     (message file for uhpofs.dll ENGLISH)
                   fmtesp.msg     (message file for uhpofs.dll SPANISH)
                   fmtita.msg     (message file for uhpofs.dll ITALIAN)
                   fmtfra.msg     (message file for uhpofs.dll FRENCH)
                   fmtdeu.msg     (message file for uhpofs.dll GERMAN)
                   fmtjpn.msg     (message file for uhpofs.dll JANANESE)
                   readme.txt     (this file you are reading)
                   fixes.doc      (list of fixes since start of beta)
                   certifyf.exe   (utility for formatting fat on 5 1/4 drives)
                   optfmt.exe     (format for optical drives for fat format)
                   format.com     (for OS/2 2.1, see note above)
                   mo.ddp         (used by DDINSTAL during installation)
                   rwopt.dgs      (Diagnostics for IBM Reference diskette)
                   readme.txt     (this file you are reading)
                   oldmo.sys      (older version mo.sys 2.35)

Note: If you are currently using an IBM 3 1/2 optical using FAT
for a file system. You can continue using FAT after installing MO.SYS.
When using MO.SYS make sure that you add the /D1 parameter.

Note: The documentation specifies a file called MOOPT.DGS; this file has been
renamed RWOPT.DGS.

MANUAL INSTALL OF MO.SYS on OS2 2.1

Copy the above files into a directory of your choice.

Make sure the Message file MO001.MSG is in your DPATH.

FOR MO DRIVES:

Make sure you have the two following lines in your config.sys:
           BASEDEV=IBM2SCSI.ADD /LED
           BASEDEV=OS2SCSI.DMD
(Note: The IBM2SCSI.ADD line may be different if you are using a different
SCSI card.  If you install the SCSI Support from the OS/2 Selective Install,
the BASEDEV=xxxxxxxx.ADD line for your card will already be in your CONFIG.SYS
file; however, the BASEDEV=OS2SCSI.DMD may need to be added.)

In CONFIG.SYS, replace any statement DEVICE=OPTICAL.SYS by MO.SYS /D1
MO.SYS replaces OPTICAL.SYS.  If you have no such statement please add
the line DEVICE=drive\path\MO.SYS /D1.

Note: If you have some other device driver for the drive installed it must
be removed.

Restart your system and note what drive letter(s) is/are assigned
to the optical drive(s) in your system. You need to know this to
format a new disk.

Note: If you are swapping media from other systems and encounter a sector not
found error, this is usually caused by the other system's format code not
certifying the media (ie, not writing every sector).  The way to fix this is to
copy all the data off the cartridge, low level format the cartridge (OPTFMT),
high level format the cartridge (format or OPTFMT), and then copy all the data
back onto the cartridge.


NEW PARAMETERS ADDED FOR MO.SYS

5) Two new parameters have been added since the documentation:
     /1 -- defaults the 3431 drives to be using 1024 byte per sector media
           (instead of the normal default of 512 byte per sector media).
           As always, the type of the media in the drive at boot time will
           override the default setting.
     /C -- enables write caching on the IBM drives that support this feature.
           The default for write caching is disabled (see note below).

*******************************************************************************
NOTE: Write cache is used to improve performance of some drives by returning a
      write complete status when the data to be written has been loaded into
      the buffer memory of the drive.  there is a small risk of the data being
      lost due to a power loss or drive failure with write caching enabled.
      The user should choose either performance improvment (use write cache
      enabled (/c switch)) or fail-safe data integrity (use write cache
      disabled (no switch, this is the default)).
*******************************************************************************

Manual install of HPOFS on OS2 2.1

Copy the above files into a directory of your choice. Make sure that
files UHPOFS.DLL and DBCS3395.dll are in a directory that can be found
in the libpath statement in CONFIG.SYS.

Make sure the Message files FMT001.MSG and MO001.MSG are in your DPATH.
If you want format and chkdsk to use another language other than English,
overlay FMT001.MSG with the message file you desire.
EXAMPLE for German...   copy FMTDEU.MSG FMT001.MSG. If you need to revert
to English the FMTENU.MSG is the English version.

FOR MO DRIVES:
In CONFIG.SYS, replace any statement DEVICE=OPTICAL.SYS by MO.SYS /D1
MO.SYS replaces OPTICAL.SYS so don't try and have both.

Note: If you have some other device driver for the drive installed it must
most likely be removed.

Add the line IFS=drive\path\HPOFS20.IFS.

Restart your system and note what drive letter(s) is/are assigned
to the optical drive(s) in your system. You need to know this to
format a new disk.

If you are currently using the FAT file system with a 3 1/2 inch
optical drive, MO.SYS will continue to support disks formatted with FAT.

New disks can now be formatted either using FAT or HPOFS. To format a
disk using HPOFS instead of FAT use the format parameter /FS:
to denote the file system desired.

EXAMPLE...            FORMAT E: /FS:HPOFS  (DEFAULT MO IFS no mixed case /r:2)
To reformat for FAT   FORMAT E: /FS:FAT

To format HPOFS (MO IFS)   FORMAT E: /FS:HPOFS /R:266
with mixed case support    This will format an mo disk and allow
                           mixed case abilities. Recommended for backing
                           up pc's running hpfs file system.

To format (HPOFS MO MEDIA FORMATTED AS WORM) FORMAT E: /FS:HPOFS /R:257 /B:
with mixed case support    This will format an MO disk with our WORM file
                           system and also allow mixed case filenames.
                           Recommended for backing up pc's running hpfs
                           file system.

                   NOTE: /r:257,266 Only support CASE SENSITIVE searches.
                         That means if you have 2 file names or subdirs :

                               SUBDIR1
                               subdir1

                         they are different because of case. You have to
                         type in the same case for an explicit find.

                                 Example: cd SUBdir1 would fail
                                          cd SUBDIR1 would change to SUBDIR1
                                          cd subdir1 would change to subdir1


IMPORTANT NOTE FOR USERS OF MIXED CASE SUPPORT--Although hpofs is aix like
 in it's support of mixed case filenames and directory names OS2 is NOT!!
 OS2 is case preservative and searches in OS2 are not case sensitive.
 Workplace shell utilities such as the Drives Icon and Seek and Scan do
 not provide case sensitive searches--so the user must be very careful
 when using the mixed case support.  In general I have found if you use
 mixed case support it is best to use an OS2 full screen and issue a
 dir or dir /s to see what files/directories you really have on the cartridge.
 Also I would only use mixed case support for backing up hpfs disks as
 you are then guaranteed that you will not be creating filenames/directories
 that you will be unable to access without some work (that may be more that
 a minor annoyance to some).  Be forewarned, if you choose to use mixed case
 HPOFS will allow you to do things that HPFS will not and then when you attempt
 to use OS2 tools you will be disappointed. (Many times files don't appear
 in searches, etc.)  Global searches are especially troublesome so if you need
 to search please include characters other than * or ? in your search. (EX
 dir *.asm)


Other Format parameters:

/?:    No format - just display parameters
/R:1   (DEFAULT ON WORM MEDIA) Format - no upper lower mixed case support.
/R:2   (MO MEDIA) Format with versioning and no upper and lower mixed case support
/R:10  (DEFAULT ON MO MEDIA) Format - no upper lower mixed case support.
/R:257 (WORM MEDIA) Format - upper/lower mixed case support.
/R:266 (MO MEDIA)   Format - upper/lower mixed case support.
/B:    (MO MEDIA)   Format - MO media using WORM IFS  (Implied /R:1)
/B: /R:257 (MO MEDIA) Format - MO media using WORM IFS  upper/lower mixed case.
/H:n   (WORM MEDIA or MO MEDIA using WORM IFS) IF USING FLOPPY FORMATTED AS
       HPOFS and using the WORM IFS this must be set to 1--default = 100.
/CP:#  (DEFAULT CODE PAGE 850) 500=EBCDIC 942=JAPANESE 944=KOREAN 948=CHINESE
/CT:#  (DEFAULT CODE TYPE 1 FOR ALL CODE PAGES BUT 500 WHICH MUST BE 2)
/%F:## (DEFAULT TO (99% VER1.1 & VER2.0) (90% VER 1.0 - 1.04) (use CHKDSK to alter
        already formatted mo disks is not supported currently on worm formatted
        media) ie chkdsk d: /%f:xx.  xx should be 99


       NOTE: In most cases CP and CT defaults are satisfactory.
             for Asian machines use the 900 series code pages. EBCDIC is for
             interchange purposes.

/V:VOLNAME or /NV:VOLNAME  allows volume label on command line instead of being
                           prompted.

/F:filename.ext  Format will read in parameters from the file name passed.
                 You can put one parameter per line in filename.ext. No
                 blank lines or multiple parameters on one line.

                 EXAMPLE:

                 FORMAT D: /FS:HPOFS /F:MYFORMAT.RUN

                 CONTENTS OF MYFORMAT.RUN

                        TOP OF FILE
                   -------------------------------
                   /V:MY_OPTICAL_DISK
                   /R:266
                   -------------------------------
                        BOTTOM OF FILE



Once a disk is formatted you can use it just like any other disk. Using
all the normal DOS commands except RECOVER, SYS, DISKCOMP and DISKCOPY.

Questions or Problems may be sent to
Pamela L. Glenn
c/o IBM  (OPTICAL DEVELOPMENT)
9000 S. Rita Rd
Tucson, Az. 85744
Dept LBRA/031-2 Rm 2784
PGLENN at TUCVM2 tie 321-3143 or 1-520-799-3143
