🚀 go-pugleaf

(Continued from the previous message)

    because OPTIMIZE makes not attempt to load them high.  DR-DOS can load 
    them high itself

        3)  HIBUFFERS is the DR-DOS command to load buffers into the 
    HMA.  It will use the HMA even if the kernel is not loaded in the 
    HMA.  The BUFFERS command of DR-DOS causes the buffers to be loaded 
    into UMBs (If HIDOS=ON is set.)  Each buffer takes an individual 
    UMB.  The BUFFERS.COM program from Quarterdeck works with DR-DOS; 
    using the LOADHI.COM program with BUFFERS.COM will cause the buffers 
    to be loaded into a single UMB.  Use HIBUFFERS only if you are 
    loading the DR-DOS kernel into the HMA, otherwise the HMA will be 
    used for nothing but buffers.  

        4)  HILOAD, HIDEVICE, and HINSTALL are the DR-DOS internal 
    commands that load TSRs and device drivers high.  They do not work 
    with QEMM-386, QEMM-50/60, or QRAM.  LOADHI.COM, LOADHI.SYS, and 
    INSTALL=LOADHI.COM/TSR, which, respectively, perform the same 
    functions, should be used instead. 

        5)  SSTORDRV.SYS is a disk-compression utility that DR bundles 
    with DR-DOS.  It loads part of itself high.  The remainder cannot be 
    loaded high, either with QEMM-386, QEMM-50/60, QRAM, or DR-DOS's 
    EMM386.SYS.  If you use EMM386.SYS it merely loads low without 
    notification; if you use QEMM-386 and LOADHI.SYS it does not load at 
    all.  OPTIMIZE will try to load it high, this must be reversed, or 
    as an alternative, SSTORDRV.SYS may be entered in the file 
    OPTIMIZE.EXC, keeping OPTIMIZE from trying to load it high.
     
       6)  There are other DR-DOS utilities that load themselves high, 
    such as SUPER PC-KWIK and DELWATCH.  They are polite enough to allow 
    LOADHI.COM to load them high in the same manner as they themselves 
    would load themselves high; this allows them to be included by 
    OPTIMIZE in its calculations.  This is done automatically and does 
    not require any attention from the user.  

OPTIMIZE
     Brilliant Quarterdeck technicians have discovered an easier method for 
using OPTIMIZE with SUPERSTORE.  See below.     
          
        1)  There is a new command, CHAIN, in DR-DOS.  This command 
    allows the CONFIG.SYS to pass control to another CONFIG.SYS-like 
    file.  DR-DOS uses it on installation if you choose to install 
    SUPERSTORE.  OPTIMIZE does not follow this passing of control to 
    another file.  If you are using CHAIN you must combine the two (or 
    more) CONFIG.SYS (or CONFIG.SYS-like) files into one for the 
    duration of the OPTIMIZation process.

        2)  The kernel of DR-DOS, sstordrv.sys, and buffers load 
    themselves high.  OPTIMIZE does not take the High RAM used by self-
    loaders high into consideration in its calculations so this can 
    throw it off making the best configuration.  See the READ.ME file 
    for information on how best to accommodate self-high-loaders.  
    Quarterdeck's BUFFERS.COM program works with DR-DOS 6 and OPTIMIZE 
    will automatically try to use it to load BUFFERS high.  This is 
    preferable because the memory used by BUFFERS will be included in 
    OPTIMIZE's calculations.     

        3)  SUPERSTORE does work with OPTIMIZE, but SUPERSTORE adds a 
    device driver to your CONFIG.SYS called DEVSWAP.COM.  The line 
    typically reads: 

                     DEVICE=C:\DRDOS\DEVSWAP.COM 

         DEVSWAP.COM is a non-resident program that switches the drive 
    designations. This is a convenience if you installed SUPERSTORE on a 
    drive that already had programs so you don't have to re-write your 
    batch files and reconfigure your software to run from a different 
    drive.  See your DR-DOS manual for information on the use of 
    DEVSWAP.COM.  Most commonly your hard disk originally was drive C:.  
    SUPERSTORE creates a new, compressed drive, to which the letter D: 
    is assigned.  DEVSWAP.COM switches these assignments.  This will be 
    presumed for the rest of this section of this explanation of how to 
    use OPTIMIZE with SUPERSTORE.   If you are compressing more than one 
    physical drive you must modify this information in consideration of 
    the compressed drives created and designations swapped.   
         When running OPTIMIZE, DEVSWAP.COM must be remarked out or 
    removed from the CONFIG.SYS.  Also all references to drives C: in 
    the AUTOEXEC.BAT and in the CONFIG.SYS after the DEVSWAP.COM line 
    need to be changed to drive D:.  Conversely, all references to drive 
    D: should be changed to drive C:. 

         The next step is to create a QEMM sub-directory on the 
    uncompressed drive.  This is typically drive D: when the DEVSWAP.COM 
    device driver is loaded in your CONFIG.SYS.  The following files 
    need to be in the QEMM sub-directory in order to run OPTIMIZE 
    properly:  QEMM386.SYS (or QEMM.SYS if you are running QEMM-50/60 or 
    QEMM-386 version 5.0, or QRAM.SYS if you are loading QRAM), 
    OPTIMIZE.COM, LOADHI.SYS, LOADHI.COM, LOGOPT.COM, BUFFERS.COM (if 
    you are using DOS 2.x or 3.x), RSTRCFG.SYS, MCA.ADL (if you are 
    running on a Microchannel machine), and WINHIRAM.VXD if you are 
    planning on running Windows 3.0 in enhanced mode.
          Once you have done this, you should reboot before running 
    OPTIMIZE so that the drives are set up correctly.  Now you will be 
    able to run OPTIMIZE normally.  After OPTIMIZE has run, you may edit 

(Continued in the next message)
---
 þ DeLuxeý 1.25 #6922 þ DESQview 386: Why buy new apps?
--
Canada Remote Systems  - Toronto, Ontario
World's Largest PCBOARD System - 416-629-7000/629-7044