 ͻ
                                                                          
                  DOS 5.0 and the Intel Inboard 386                       
                                                                          
 ͼ

 DOS 5.0 AND THE INBOARD 386

     Both Microsoft and IBM versions of DOS 5.0 have been tested with the
     Inboard 386 and no compatibility issues were found. They are
     compatible. All DOS 5 functions that work on a 386 machine will also
     work on a system equipped with an Inboard 386. It is necessary to have
     the command line for the Inboard first in the CONFIG.SYS, before
     HIMEM.SYS or any other device driver.

 EMM386.EXE AND THE INBOARD 386

     The EMM386.EXE memory manager supplied with both Microsoft's and IBM's
     version of DOS 5.0 is fully compatible with the Inboard 386.  It is
     necessary to have the command line for the Inboard first in the
     CONFIG.SYS, before HIMEM.SYS or any other device driver. It is not
     possible to load the Inboard 386 device driver high (DEVICEHIGH).

 DOS 5.0 AND ICACHE

     ICACHE.COM, the disk cache utility shipped with the Inboard 386, was
     designed when DOS would not allow hard disk partitions greater than
     32Mb.  DOS 5.0 allows greater than 32Mb partitions.  Also, ICACHE.COM
     puts the cache in Extended memory and DOS 5.0 utilities like DOS=HIGH
     interfere with how ICACHE determines the amount of available memory.
     SMARTDRV.SYS, the disk caching utility supplied with DOS 5.0, is fully
     compatible with the Inboard and should be used instead of ICACHE.

 HIMEM.SYS AND THE INBOARD 386

     The HIMEM.SYS supplied with both Microsoft's and IBM's version
     of DOS 5.0 is fully compatible with the Inboard 386.

 DOS 5.0 AND INBOARD 386

     DOS 5.0 and Intel Inboard 386 Products

     DOS 5.0 appears to be fully compatible with both the Inboard 386/PC and
     Inboard 386,  with the exception of the combination of Inboard 386/PC
     and EMM386.EXE.

     DOS 5.0 is the first DOS version to make significant use of extended
     memory.  It also supports the management of Upper Memory Blocks (UMBs)
     by DOS.  The Inboard has a direct affect on accessing these features of
     DOS 5.0.

     EMM386.EXE Incompatible with Inboard 386/PC

         EMM386.EXE, the 386 control program that is provided with DOS 5.0,
         makes certain assumptions about all i386 family systems.  Because
         386 systems in general were based on AT, not PC, architecture,
         EMM386.EXE assumes that the system it is running on will have the
         BIOS support typical of an AT.  It also assumes the presence of a
         second programmable interrupt controller.

         For that reason, EMM386.EXE will not run on Inboard 386/PC equipped
         systems.  It is not an incompatibility with the Inboard, as much as
         it is an incompatibility with the base PC or XT type system.  To
         get equal memory management, we recommend Inboard 386/PC owners try
         either QEMM386 or 386MAX. Either of these provide the same EMS
         services, UMB support and High Memory Area (HMA) support that
         EMM386.EXE does, without the need to run HIMEM.SYS.  These programs
         actually use less RAM than  the EMM386/HIMEM combination.

 HIMEM.SYS COMPATIBLE WITH BOTH INBOARDS

         HIMEM.SYS is compatible with both Inboard 386/PC and Inboard
         386/AT. In both cases, the Inboard driver (either INBRDPC.SYS or
         INBRDAT.SYS) should be loaded before HIMEM.SYS.  Generally the
         Inboard driver should load before any other drivers in the system.
         Inboard 386/PC systems have very little problem with HIMEM.SYS,
         since the Inboard provides the A20 gating services that HIMEM
         needs.

         Inboard AT installations in some non-IBM machines may experience
         problems with HIMEM if the system provides non-standard A20 gating
         services.  Please check the README file that comes with DOS 5.0
         regarding HIMEM.SYS switches, or refer to the computer
         manufacturer.

     ILIM386.SYS and EMM386.EXE are both 80386 control programs, and are not
     mutually compatible.  If you are running EMM386.EXE, or any other 80386
     control program, you should not also try to run ILIM386.SYS.

     ICACHE, the disk cache provided with Inboard products, should not be
     run with SMARTDRV, or with any other disk cache. Double caching can
     cause data loss on the hard disk.  ICACHE is also not compatible with
     the large partitions (over 32 megabytes) supported by DOS 5.0.  In
     general, if the DOS 5.0 user wants to use a disk cache, they are better
     off using SMARTDRV, which is compatible with Inboards.

     DOS 5.0, and Inboard 386/PC Windows 3.0

         Inboard 386/PC users who are running the Inboard 386/PC specific
         version of Windows 3.0 should use the version of HIMEM and SMARTDRV
         that are provided with DOS 5.0, not those that shipped with
         Windows.  If you are using QEMM386.SYS, you should be running
         version 5.11 or 5.12, if you are running 386MAX, you should be
         running version 5.1 with a file date of 1/10/91 or later.  With
         either 386MAX or QEMM386 do not run HIMEM.SYS.

     For more information, please refer to:
                    Upper Memory Blocks (UMBs)     FaxBACK doc 1158
                    High Memory Area (HMA)         FaxBACK doc 1250



End of file                 Intel FaxBack # 2051          June 25,1992
