ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º º º Inboard 386 Software Compatibility: M-N º º º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ MATLAB AND MATLAB 386 Intel has tested this version 3.5d of this program with Inboard 386, and they are compatible. MATLAB 386 uses the Pharlap DOS Extender and is VCPI-compatible. MICROSOFT FLIGHT SIMULATOR Flight Simulator is compatible with Inboard 386. MICROSOFT FORTRAN COMPILER Version 4.0 of this compiler does not work with the 80387. It does work with the 80287. Microsoft is working on a new version to solve this problem. MICROSOFT EXCEL Intel has tested Excel with Inboard 386 using ILIM386.SYS and they were compatible. Intel also tested Inboard 386 with Excel running under Windows 386 and found no problems. Microsoft recommends Windows 386 version 2.02 (or later) for running Excel but states Windows 386 version 2.01 will run. If you use version 2.01, the software displays a Windows upgrade message each time it boots. Excel comes with a runtime version of Windows 2.03 and will not run outside of Windows. MICROTECH RESEARCH COMPILER This program is compatible with Inboard 386, but you must not use ILIM386. A20 errors will occur if ILIM386 is running. MULTIMATE ADVANTAGE When running MultiMate Advantage with Inboard 386 in fast mode, the computer will beep and repeat the last keystroke. You can correct this by entering the Modify Console Defaults menu and changing the keyboard acceleration to OFF. (MultiMate Advantage comes with this set to ON.) MultiMate is reported to be correcting this (it is a problem on all 80386-based computers). Call MultiMate for availability of the correction. MICROSOFT WINDOWS 3.0 INBOARD 386/AT Windows 3 works great in ENHANCED, STANDARD, or REAL mode, using HIMEM.SYS and EMM386.SYS provided by Microsoft. Start Windows with WIN /E command for 386 mode or WIN /R for real mode operation. Do not use Windows 3.0 with Intel's ICACHE or ILIM386. Instead use Microsoft's SMARTDRV disk cache and EMM386 EMS emulator. MICROSOFT WINDOWS 386 (Field report) If you receive a computer video message when using an EGA, try adding the EGASIZE=256 parameter to the INBRADAT.SYS line in your CONFIG.SYS file. One user reports this solved the problem. You can also try using the EGAINIT parameter in the INBRADAT.SYS line. Windows 386 uses its own memory management, so you can't have any other memory manager (such as EMM or ILIM386) installed when you run Windows 386. If you have EMM or ILIM386 installed, the computer will lock up when you invoke WIN386. Windows 386 only uses extended memory, so you must configure any Inboard 386 memory you want to use with WIN386 as extended memory. Also, because Windows 386 can't use expanded memory, don't use the /e parameter in the WIN.INI file. You can find more information in the "Using MS Windows/386" booklet. The subsections are "Converting Expanded Memory to Extended Memory" and "Using SMARTDrive." NOTE: Even though they share the same User's Guide, WIN386 2.03 is not the same as WIN 2.03. You can use EMM or ILIM386 with WIN 2.03. WINDOWS 386 EXPANDED MEMORY NOT AVAILABLE Windows 386 does not completely conform to the LIM EMS spec. It will create expanded memory with less than 4 pages in its page frame. Intel's CHKMEM and VECHECK programs will report expanded memory as usual. However, applications such as PageMaker or Lotus 123 will not recognize or use the expanded memory because of the nonstandard size of the page frame. If you're having problems with expanded memory under WIN386, check for boards that might cause a page frame confict. (Network cards, scanner cards, VGA cards, etc.) After you have resolved the page frame conflict, if a problem persists, you may need to add the following statement to the WIN.INI file: EMMINCLUDE=XXXX-YYYY where XXXX is the starting address of the first page frame and YYYY is the ending address of the last page frame. Legal addresses are between C000 and DFFF. Example: EMMINCLUDE=D000-DFFF MICROSOFT WINDOWS 2.03 Microsoft Windows 2.03 is incompatible with 6-MHz IBM PC AT BIOS version dated 1/10/84. Windows 2.03 works fine with the new 8-MHz BIOS. Intel is currently investigating BIOS upgrade possibilities. For all other computers, Windows doesn't work with the /E parameter in the SWAPDISK= line of the WIN.INI file. This is a problem with Windows. Even though the Windows manual says to use this parameter, remove it and use either the hard disk or a RAM disk drive letter as the SWAPDISK. Also designate a SWAPSIZE= on the next line (for example SWAPSIZE=1024 or SWAPSIZE=2048). Windows 2.03 is not compatible with ILIM386 version 4.07. MICROSOFT WINDOWS 2.0 AND 2.01 Windows version 2.0 and 2.01 are for COMPAQ computers only. Windows version 2.03 is the generic version that works with most other computers. If you are having problems with Inboard 386 and Windows, make sure you have the correct version of Windows by checking the diskette label. RUNTIME VERSION OF WINDOWS The Runtime versions of Windows are NOT memory managers and are generally compatible with 386 control programs. ILIM386 version 4.07 is incompatible with some versions of runtime Windows. The symptom is for the MicroSoft sign-on screen to come on, and then the system locks up. WINDOWS AND EGA Using Windows with an EGA can corrupt part of the screen (usually the lower half). If this happens, add the EGASIZE=256 command to the INBRDAT.SYS line in the CONFIG.SYS file. WINDOWS AND SPEED CHANGES The Inboard speed-change keys won't work inside of Windows to change speeds or to warm boot the computer. (Windows "traps" all commands from the keyboard. To warm boot, you must exit Windows; and to change speeds, you must create a PIF file and run ISPEEDAT.COM. ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ End of file Intel FaxBack # 2058 June 25,1992