NOVELL TECHNICAL INFORMATION DOCUMENT

DOCUMENT PROCESSING INFO:  FAX, REPLACES FYI.M.1202
TITLE:  LOADING SUPERSTOR INTO UPPER MEMORY
DOCUMENT ID:  TID800025
DOCUMENT REVISION:  A
DATE:  16AUG94
AUTHOR:  SBASSIR;KBANTA
ALERT STATUS:  Yellow
DISTRIBUTION:  Public
INFORMATION TYPE:  Issue
README FOR:  NA
NOVELL PRODUCT CLASS:

Desktop Products

NOVELL PRODUCT and VERSION:

DR DOS 6.0

CATEGORY:

Compression

ABSTRACT:

N/A

-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL 
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE 
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL 
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------

ISSUE

SYMPTOM:  TRYING TO HIGH LOAD SSTORDRV.SYS

ISSUE/PROBLEM:  Using Third Party XMS UMB providers with SSTORDRV.SYS is not 
as straight forward as loading SSTORDRV.SYS with the DR DOS memory manager. 

SOLUTION:  Users of QEMM and 386MAX (and other Third Party XMS UMB
providers) should only load SSTORDRV.SYS with the DEVICE=C:\SSTORDRV.SYS 
syntax.

The device driver which loads SuperStor, SSTORDRV.SYS, is designed to load 
portions of its code into upper memory when that memory has been made 
available via an XMS (eXtended Memory Specification) compatible UMB (Upper 
Memory Block) provider, like EMM386.SYS.

When using EMM386.SYS, loading SSTORDRV.SYS is made simple, that is,
DEVICE=C:\SSTORDRV.SYS or HIDEVICE=C:\SSTORDRV.SYS will load the driver
properly.  This is because SSTORDRV.SYS has been altered to load the same 
with either command.  It knows when HIDEVICE is used, but loads like it does 
with DEVICE anyway.

Because a portion of SSTORDRV.SYS must remain in conventional memory there 
will be approximately 22K less conventional memory. If the driver cannot be 
loaded into upper memory users will see about a 48K loss of conventional 
memory.
Problems have been seen with 386MAX's 386MAX.SYS driver and QEMM's QEMM386.SYS
driver.  The problem occurs when users (or the Memory Manager's "optimize" 
program) try to load ALL of SSTORDRV.SYS into upper memory with their own 
"HIDEVICE" equivalent.  The SuperStor driver is unable to tell when it has 
been loaded with "HIDEVICE" equivalent commands.  

Loading SSTORDRV.SYS with the following commands may cause
problems:
          DEVICE=C:\QEMM\LOADHI.SYS C:\SSTORDRV.SYS
          DEVICE=C:\386MAX\386LOAD.SYS PROG=C:\SSTORDRV.SYS
Use :
     DEVICE=C:\SSTORDRV.SYS instead.

-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their 
respective owners.  Consult your product manuals for complete trademark 
information.
-----------------------------------------------------------------