ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º Inboard 386/PC and 386 Memory Managers Software Compatibility º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 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 i386- based 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 and the ability to load device drivers high (into the Upper Memory Blocks), 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. 386 EXPANDED MEMORY MANAGERS IN GENERAL There can be only one memory manager in a system at a time. 386 specific memory managers replace any memory manager already present and XMS drivers like HIMEM.SYS. 386 specific memory managers use the system's Extended Memory to provide Expanded memory. The InBoard(TM) 386/PC replaced the Conventional memory of the machine and it is impossible to provide Extended Memory across an 8-bit bus. This means any memory card currently in the system can't be used to provide any memory. The only way to get more Extended memory in the system is to add an InBoard(TM) 386/PC piggy back card, which attaches directly to the InBoard with a 32-bit data path. EMM386.SYS FROM WINDOWS Windows 3.0 for the InBoard 386/PC ships without Microsoft's EMM386.SYS. EMM386.SYS is used to supply Expanded Memory for DOS applications outside of the Windows environment. EMM386.SYS only provides a 64K page frame and does not support loading TSRs out of Conventional Memory. Expanded Memory is automatically provided by Windows for DOS applications running under the Windows environment. A third party Extended Memory Manager must be used to get Expanded Memory outside of the Windows environment or load TSRs out of Conventional Memory. At this time, the only Extended Memory Managers we know of that will work in conjunction with Windows 3.0 for the InBoard 386/PC are QEMM386 version 5.11 (or newer) by QuarterDeck, and 386^Max 5.12 (or newer) by Qualitas. QEMM 5.1X Only QEMM386.SYS ver 5.12 or higher will work with Windows 3.0 for the InBoard 386/PC.QEMM386.SYS ver 5.11 will work fine in the REAL or ENHANCED mode, but not the STANDARD mode. A customer with QEMM386.SYS ver 5.11 can download the upgrade from QOS's BBS (213)396-3904 the file name is WIN300.PAT or WIN300.ZIP. The customer will need to have his QEMM386 serial number to log onto the BBS. *Special Note* To get QEMM386.SYS 5.1X to work, the DEVICE = QEMM386.SYS line had to be heavily modified. The video range had to be excluded with X=A000-, the High Density Floppy Controller ROM should be cached with ROM=, the RAM switch must be used to provide LOADHI support, the U8 (unusual keyboard controller) switch must be used because QEMM386.SYS expects a AT keyboard, and IA (ignore A20) switch must be used because there is no hardware on the motherboard to support A20 switching. The whole line looks like this: Device=QEMM386.SYS X=A000-C7FF ROM=C800-CBFF RAM U8 IA FEATURES: Replaces HIMEM.SYS Allows Windows 3.0 for the InBoard 386/PC to come up in REAL, STANDARD, or ENHANCED mode. Supports loading TSRs out of Conventional Memory (LOADHI). Provides Expanded Memory for DOS applications running outside of the Windows ENHANCED mode, running under Windows in the STANDARD mode, or running under Windows in the REAL mode. QEMM 6.0 QEMM 6.0 has been tested with the InBoard(TM) 386/PC and Windows 3.0 for the InBoard(TM) 386/PC. There are no compatibility issues, they are compatible. The standard installation procedure works flawlessly. Before running OPTIMIZE and using the STEALTH capability of QEMM 6.0, the user must add the command line DEVICE=HOOKROM.SYS as the first line of the CONFIG.SYS (see the README file from QuarterDeck for more information). 386^MAX 386^MAX ver 5.10 and 5.12 have been tested with the InBoard(TM) 386/PC and Windows 3.0 for the InBoard 386/PC and they are semi-compatible. The standard installation procedure for 386^MAX worked flawlessly, as did MAXIMIZE., LOADHI.SYS and LOADHI.COM. Windows came up fine in both REAL and ENHANCED modes, but failed to come up at all in the STANDARD mode. FEATURES: Replaces HIMEM.SYS Allows Windows 3.0 for the InBoard 386/PC to come up in REAL, or ENHANCED mode BUT NOT STANDARD MODE. Supports loading TSRs out of Conventional Memory (LOADHI). Provides Expanded Memory for DOS applications running outside of the Windows ENHANCED mode, or under Windows in the REAL mode. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ End of file Intel FaxBack # 2654 July 17,1992