home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.apps
- Subject: Re: Problems with Shiftrun, ET4000 Windows Drivers (minor)
- Message-ID: <1992Dec14.234511.14300@njitgw.njit.edu>
- Date: 14 Dec 92 23:45:11 GMT
- References: <BywHt9.3G9@ns1.nodak.edu> <Byx2Gu.L49@netnews.jhuapl.edu> <harris.724194379@garfield.catt.ncsu.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 30
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <harris.724194379@garfield.catt.ncsu.edu> harris@garfield.catt.ncsu.edu (Michael Harris) writes:
- >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...
-
- Are you using CALL= or RUN=?
-
- >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.)
-
- CALL= does not run the application asynchronously. CONFIG.SYS
- processing will not proceed past the CALL= until the process
- terminates. Perhaps this will help.
-
- >Just curious, why do people put a RUN=C:\OS2\MODE.COM statement in CONFIG.SYS?
-
- MODE does more than just set up baud rates. It also redirects printer
- output and activates buffered UART chips. By placing the statement in
- CONFIG.SYS, the changes affect the entire system instead of just one
- session.
-
-
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-