Kontron speedMOPSlcdCE, Руководство пользователя

Страница: 60 / 99

KONTRON
Appendix A: System Resource Allocations 52 speedMOPSlcdCE User’s Guide
23.3.1.
Using Expanded Memory Managers
speedMOPSlcdCE extension BIOSes can be mapped to an upper memory area. (See the previous
table.) Some add-on boards also have optional ROMs or use drivers that communicate with their
corresponding devices via memory mapped I/O such as dual-ported RAM. These boards have to
share the upper memory area with the Expanded Memory Manager’s EMS frame. This often causes
several problems in the system.
Most EMMs scan the upper memory area for extension BIOSes (optional ROMs) and choose a free
memory area for their frame if it is not explicitly set. Normally, they are not always capable of
detecting special memory-mapped I/O areas. You need to tell the EMM which memory areas are not
available for the EMS frames, which is most of the time done by using special exclusion parameters.
If the Expanded Memory Manager you use cannot detect extension BIOSes (optional ROMs), make
sure you excluded all areas in the upper memory, which are used by extension BIOSes, too. Your
instruction in the CONFIG.SYS concerning the Expanded Memory Manager should look like this:
(question marks for location of extension BIOS).
MS-DOS Example
DEVICE=EMM386.EXE X=????-???? X=E000-FFFF
Note : When booting up your system using this configuration under MS-DOS, the
exclusion of area F000 to FFFF causes a warning. Microsoft reports that this
message will always appear when the F000 segment lies in the shadow RAM.
This is a bug of EMM386, not the speedMOPSlcdCE.
Please read the technical manuals of add-on cards used with the speedMOPSlcdCE for the memory
areas they use. If necessary, also exclude their memory locations to avoid a conflict with EMM386.