READTHIS  


            H Y P E R D I S K     V E R S I O N      4.10

                               BY

                        H Y P E R W A R E


  Welcome to HyperWare's Shareware HyperDisk Version 4.1

  The fastest utilities East, West, North and South of the Pecos!

 Be sure to check the *** W A R N I N G *** notes during the INSTALL operation!

 You can stop at any time by striking <Esc>.

  Try the handy Reader INDEX function "F2"

     ___________ Release Contents______________

CONTENTS:

READTHIS BAT     Calls READER.EXE to view this file
READTHIS         This file
READTHIS IDX     READER.EXE Index file
ID       BAT     dummy file
INST_DSK BAT     Batch installation of HyperDisk
READ_DSK BAT     Online Document Reader
ORDERFRM DOC     Order/Registeration Form
HYPER286 EXE     HyperDisk for 80286 Extended Memory
HYPER386 EXE     HyperDisk for 80386 Extended Memory
HYPERDK  EXE     Post-Install Command Processor
HYPERDK  PIF     WINDOWS 3.0 PIF control file
HYPERDKC EXE     HyperDisk for Conventional Memory
HYPERDKE EXE     HyperDisk for EMS memory
HYPERDKX EXE     HyperDisk for Generic Extended Memory
INST_DSK EXE     HyperDisk installer
READER   EXE     File Reader
HYPERDSK IDX     Popup index for HyperDisk Reader
HYPERDK  PIF     HyperDisk Windows 3.0 PIF file
HYPERDSK TXT     Condensed HyperDisk manual
PRODUCTS TXT     HypweWare Product brief
UPGRADES TXT     Upgrade policy 
WIN3NOTE TXT     Special instructions for Windows 3.0 users.


_________________________________________________________________

                   Packed File Corrupt Error!

If you encounter this error you should obtain a copy of LZEXE to unpack 
from Microsoft file format. There is a long standing bug in EXEPACK that
seems to defy Microsoft's efforts. If you can not find a copy you can down
load a copy from HyperWare's BBS at (408)-683-4988. Look for ENGLZEXE.ZIP
it is a great FREEWARE program by Fabrice Bellard (Grabels, France), (et. al.).


  ___________ Release Changes______________

  8/20/90  HyperDisk 4.10 release

  Windows 3.0/386 aware version:  

* Now HyperDisk releases memory in the same manner as SmartDrv, use CW:nnn
  to set the size of cache to use while in Windows. You must be using XMS
  memory. The XMS-A20 gate is closed automaticlly (OG:+), Floppy interrupts
  are disabled (XIF:-). Upon exit from Windows the original conditions are
  fully restored. Examples:

  HYPERDK  C:2048:512   ; Set Cache size 2048 in DOS,512 in Windows 3.0
  HYPERDK  CW:512       ; Set Windows 3.0 Cache size to 512 
  HYPERDK  CW:0         ; No Cache while in Windows 3.0
  HYPERDK  CW           ; No size change when running Windows 3.0, Default

* Report panel displays CW active parameter: Cache Size   : 2048:512

* Extended the Override Gate Exit (OG) function, now the A20 gate may
  may be closed on exit for any gate method. 

* Restored all HotKey functions in Shareware version.

* Restored Shadow Ram High Memory loader in Shareware version.

 
  ------------------------------------------------------------------

  8/2/90  HyperDisk 4.03 release

* Fixed problem with SpeedStor et.al. when hard disk drive(s) is greater than
  1024 cylinders. 

  7/28/90  HyperDisk 4.02 release

* Added report of user selected HotKey shift state values. Look on the
  report panel for:

   Cache Memory Size        : 1024       Caching Function (aclr) : ON

   Here a=<Alt>, c=<Ctrl>, l=<L-Shift> and r=<R-Shift> ----||||


  For Staged Write users:

* Added automatic timed retry for write updates errors, normally,
  HyperDisk will retry a disk write twice before issuing an error
  and prompting the user for:

    HyperDisk Error ........... Retry, Skip, Abort?

  This message has been changed to support both keystrokes and Shift
  State Hotkeys. Shift state hotkeys allow entry of commands even when
  the foreground application has taken normal keyboard control (i.e.
  Microsoft Windows 3.0, SmartCom, et. al.). The new error message is
  proceeded by three beeps and the following message:

    HyperDisk Error......... RShft: Retry=LShft Skip=Ctrl Abort=Alt?

  You can enter: R or <RShift><LShift> for RETRY; S or <LShift><Ctrl>
  for SKIP; A or <RShift><Alt> for ABORT.  If no response is entered 
  within four seconds a RETRY is automaticlly entered for you.

* Staged write error handling has been enhanced. If a disk write 
  update fails, each sector is written and verified one-by-one. This 
  insures the minimum loss of data if the disk surface has developed 
  a bad spot. Hard errors are then helt in the cache until all of the
  writable updates are completed; then the errors are retried and if
  still failing the error is displayed and the user is prompted for 
  the appropriate action.

*  Fixed Advanced Update problem with Phoenix 1.10 13 BIOS (et. al.) 

*  Add new parameter to control XMS transfer mode control:
   
   XT   Selects XMS transfer mode in both Real and Protected mode.
   XTR  Selects XMS transfer mode in Real mode.
   XTP  Selects XMS transfer mode in Protected mode.
 
   Example: hyperdk XTR:- XTP:+ 

   Used to avoid Microsoft HIMEM.SYS problems. 

   Windows 3.0 enhanced mode no DOS use, install: HYPERDKX XT:+
   Windows 3.0 real/enhanced or DOS use, install: HYPER386 XTR:- XTP:+

   386Max all extended models:    HYPERDKX XT:- or HYPER386 XT:-

   Add special handling for XF command to prompt for console I/O: XF:CON
   Use for Windows 3.0 PIF default command line parameters

   Some cosmetic changes to display logic:

   OX   Disable report display unless OR override applied.
        OX or OX:+ disables report panel.
        OX:- restores report panel display.
        OR:- may be used to override OX setting.
        
   ___________________________________________________________________

Version 4.01 07/12/90

* Fix for problem with second hard disk not being cached. Some systems are
  configured with only one extended partition and no primary partition on
  the second (ID Hex: 81) hard drive.

   ___________________________________________________________________

Version 4.00  6/17/90

Late additions to HyperDisk, HyperKey and HyperScreen:

   All HyperWare products now support Shadow Ram loading!
   If you are currently using 386 Max, QEMM 5.0 or have a machine
   based on Chip & Technologies NEAT 210 or 300 Series chip sets
   you may load the entire SpeedKit package in upper memory (above 640K)!

   Just add: XS to the installation command line.

   Follow the same instructions as outlined for HyperDisk.

   If you are using a Chips & Technologies 210 or 300 series 
   chip set you will need to inform the first loaded product
   to allocate the initial Shadow Ram block for all of the
   following HyperWare products.

   Example:  device=C:\HyperKey.exe  r:18 d:200 xs:48

   The XS:48 command will cause HyperKey to allocate a 48K block of
   Shadow Ram. Then HyperDisk and HyperScreen may be loaded in the
   same block by adding XS to each of their respective installation 
   command lines.

   Chips and Technologies Shadow Ram users:

   If you are using an EMS system that does not support XMS's Upper Memory
   Blocks (UMBs) such as EMMSYS, Windows 3.0 Intel 4.0 EMS, AST EEMS, etc.
   You will need to EXCLUDE the last part of the E000 segment of memory.
   Load HyperDisk first with the XS option set, examine the report panel
   to (second section of the report panel) find where HyperDisk is loaded.
   Next, edit your EMS device installation command line and exclude the
   area from use by your EMS manager. See your EMS product installation
   guide for details on excluding areas from EMS use.

   Note: Qualitas' 386MAX 4.04+ and Quarterdeck's QEMM 5.0+ directly 
   support XMS UMB's and require no special procedures when installing
   HyperDisk with these products.

  ________________________________________________________________

  HyperDisk: 6/17/90 

   A new program module HYPERSTB.EXE has been added to the HyperDisk
   package.  This program allows you to install and later uninstall
   HyperDisk easily and without conflict with other resident programs.
   Install HYPERSTB.EXE in either your CONFIG.SYS or AUTOEXEC.BAT
   files (normally in the same place as you would place the HyperDisk 
   install statement). Later, either near the end of the AUTOEXEC.BAT
   or from the command line you may install HyperDisk. HYPERSTB's function
   is to reserve the resources for HyperDisk, preventing other resident
   programs installed later from conflicting with HyperDisk. HYPERSTB
   requires approximately 400 bytes!

   
   Example: 

   device=c:hyperstb.exe


   No parameters are needed!

 
  ________________________________________________________________

  Once again, Thank You for purchasing HyperWare's products.

                                 Roger Cross, HyperWare, dBa
