home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.apps
- Path: sparky!uunet!cs.utexas.edu!swrinde!gatech!concert!rock!taco!garfield.catt.ncsu.edu!harris
- From: harris@garfield.catt.ncsu.edu (Michael Harris)
- Subject: Re: Problems with Shiftrun, ET4000 Windows Drivers (minor)
- Message-ID: <harris.724194379@garfield.catt.ncsu.edu>
- Sender: news@ncsu.edu (USENET News System)
- Organization: North Carolina State University
- References: <BywHt9.3G9@ns1.nodak.edu> <Byx2Gu.L49@netnews.jhuapl.edu>
- Date: Sat, 12 Dec 1992 21:06:19 GMT
- Lines: 29
-
- hildajk1@netnews.jhuapl.edu (Ken Hildabolt) writes:
-
- >phaniraj@plains.NoDak.edu (V. Phaniraj) writes:
-
- >>I'm having trouble with the IBM EWS utility shiftrun. It works fine
- >>when executed from the command line, but not when invoked using
-
- >I have seen a discussion on Inet somewhere, that says placement of the
- >call statement in Config.Sys is important. Are you running a MODE.COM
- >in Config.Sys, if so, place the call before the CALL or RUN to mode.com.
- >I have mine as next to last, with the RUN=C:\OS2\MODE.COM after it, and
- >all works well.
-
- Someone else on Compuserve had a problem involving RUN=C:\OS2\MODE.COM in
- the CONFIG.SYS. Once it was removed, the problem went away.
-
- I put the CALL line immediately after IFS=C:\OS2\HPFS.IFS...
-
- The problem tends to be that MODE.COM appears to capture the keyboard and
- since it is running asynchronously to the CONFIG.SYS, when SHIFTRUN tries
- to capture the keyboard, it can't do it. (Although you should see an error
- message when this happens.)
-
- Just curious, why do people put a RUN=C:\OS2\MODE.COM statement in CONFIG.SYS?
-
- ______________________________________________________________________________
- Michael Harris - harris@catt.ncsu.edu or harris@carvm3.vnet.ibm.com
- System Administrator, Computer & Technologies Theme Program, NC State Univ.
- (My opinions are my own and do not represent those of NCSU or IBM Corporation)
-