Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!bloom-beacon!spdcc!ftp!wjr
From: wjr@ftp.COM (Bill Rust)
Newsgroups: comp.sys.ibm.pc
Subject: help on OS/2 error
Message-ID: <725@ftp.COM>
Date: 23 Sep 89 19:41:54 GMT
Reply-To: wjr@ftp.UUCP (Bill Rust)
Distribution: usa
Organization: FTP Software, Inc.
Lines: 23

I have ported a large piece of code to OS/2. It currently is mostly in
a dll with a stub device driver to provide access to a device. There
is an init process that runs to keep the dll loaded and initialized. I
originally had calling processes (other that the init routine) go thru
the library with requests all the way down to the device. Much to my
chagrin, I suddenly realized that this wasn't working because the
device handle was in the init routine's context, not the calling
procedure's. I then changed it so that the init procedure queued
requests on one of its threads. When I tried testing this, programs
that used to get to the point of writing to the device now crash the
system with the following message:

Session Title: TESTP.EXE

SYS2070: The system could not demand load the application's segment.
ETHDRV SYS_... is in error. For additional detailed information also
see message SYS0127.

If someone out there would tell me where this message is documented
and what it means, I would be most appreciative. Please Email directly
to me. Thanks.

Bill Rust (wjr@ftp.com)