Epson Equity 386/20 Product Support Bulletin(s) - Page 27
Using the EEMM386.EXE Device Driver
View all Epson Equity 386/20 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 27 highlights
Product Support Bulletin Subject: Using the EEMM386.EXE Device Driver Date: 6/12/89 Page: 1 of 1 PSB No: S - 0 Originator: M The purpose of this bulletin is to explain the installation and usage of the EEMM386.EXE device driver on the Equity 386/20. The Equity 386/20 can be configured with up to 16MB (155MB user accessible) of 32 - bit RAM. This is normally treated by the system as extended or linear memory. This can be used by a specific device driver (such as VDISK.SYS) or by an appropriate operating system - MS OS/2 or Xenix, for example. MS - DOS and MS - DOS applications cannot make direct use of this type of memory. Some MS- DOS applications can take advantage of expanded memory specification (EMS) RAM. This is a memory paging specification developed jointly by Lotus, Intel and Microsoft and is commonly referred to as LIM spec memory. The current specification is 4.0. Epson provides the device driver EEMM386.EXE with the Equity 386/20 that takes extended memory and emulates LIM EMS memory. It is installed at boot- up via a line in the CONFIG.SYS file. The proper syntax is: DEVICE = C:\EEMM386.EXE nnnn where nnnn is the amount of memory in kilobytes to be reserved for EMS emulation. As the system boots and installs the device driver, a message is displayed on the screen while each page (16KB) of memory is tested. Once installed, virtually any MS - DOS application that utilizes EMS memory can be loaded and will access the additional RAM. Only one application tested to date has shown anomalous behavior Microsoft Windows 286. When loaded, it does not recognize the existence of EMS memory. This is due to its extremely strict compliance with the LIM 4.0 specification. However, when an application such as Lotus 1 - 2 - 3 or Excel is loaded from Windows 286, these applications do detect and use the EMS memory. Note that windows/386 does not experience this behavior as it uses extended memory and performs its own EMS memory mapping.