[comp.windows.ms] problems using EMS with WIN3/enh

RBYAML@ROHVM1.BITNET (Aengus Lawlor) (01/14/91)

We use PCSA (DECs PC-Lan product) here. The major problem with it is that it's
a memory hog, so DEC provide a method for loading aprts of it into EMS.
Unfortunately, when I try and run WINDOWS in enhanced mode, it locks up (I
usually get the Windows banner, and then a C:\ in the top left. I have to
reboot.)

I have tried this with QEMM 5.11, ASTEMM (the machine is an AST 386/16, w/4meg)
and EMM386. The parts of PCSA that use XMS don't have any problems.

I've checked it on 3 or 4 machines, and all exhibit the same problem. All are
equipped with 3Com 3C503 cards.

Does anyone have any ideas? Are there known problems with drivers that use EMS
before Windows is loaded. Is anyone getting this to work using different h/w?

I have a similiar problem using ver 2.15 of NET3 (novell). I know Windows
requires the 3.0 drivers, but if I try to use novell AFTER a windows session
I get a server not found message. If I load NET3 before windows, windows won't
load.

I'd be interested to hear if anyone has had similiar problems, and how they
resolved them.
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)

dcc@hpopd.pwd.hp.com (Daniel Creswell) (01/15/91)

Have you checked that you and windows agree about what Lan sox you're using?

run setup and find out - Windows has to load a driver for each network.
Wrong driver = crash!

I've also had roblems using EMM386 with Lan sox and smart drive running in
extended memory (under real mode usually but interesting huh!)