WILSON@UKCC.BITNET (Randy Wilson) (02/05/90)
I am using a 386/16 with the 4 meg board for a workstation with a WD8003E ethernet card and ran into the same troubles with Zenith's ems.sys. Zenith tech support told me that ems.sys uses D000 as the address to set up expanded memory. Unfortunately that is the same address that we use for the shared memory in the 8003 shell. I haven't gotten around to trying to gen another shell using a different address to see if that would work. Randy Wilson (wilson@ukcc.uky.edu) analyst/programmer Dept of Physiology University of Kentucky
JRD@USU.BITNET (Joe Doupnik) (02/06/90)
Zenith 386's w/extra memory. There have been a number of messages
on this topic so I hope Zenith users have been keeping notes. A common
thread is comms trouble when one version or another of Zenith's emm.sys
program is operated. I would expect similar/worse trouble when 16 bit
VGA boards are used in 16 bit mode.
Some network boards use shareable memory, and of those some allow
the memory address to be placed in segment E000h. That segment is normally
free on 386 machines but not free on regular ATs. Thus, the network board
can be moved up there in many cases. 16bit VGA boards are also memory hogs
and the best solution seems to be tell them to use 8-bit mode; there is
little loss of performance and a huge loss of system conflicts.
Quarterdeck's expanded memory manager, QEMM, lets the user divide
up the space needed for expanded memory tables to hop over network boards
and similar.
Norton's System Index is a handy way of discovering free space and
probably conflicts, without becoming a guru.
Joe D.