home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!caen!destroyer!cs.ubc.ca!unixg.ubc.ca!ochealth
- From: ochealth@unixg.ubc.ca (ochealth)
- Newsgroups: comp.os.os2.misc
- Subject: COM driver dies
- Date: 13 Dec 1992 09:36:48 GMT
- Organization: University of British Columbia, Vancouver, B.C., Canada
- Lines: 30
- Message-ID: <1gf07gINNbik@skeena.ucs.ubc.ca>
- References: <1992Dec9.232055.28242@CSD-NewsHost.Stanford.EDU> <1992Dec12.100733.8949@usage.csd.unsw.OZ.AU> <1992Dec13.085031.7034@netcom.com>
- NNTP-Posting-Host: unixg.ubc.ca
-
-
- occaisionally the OS/2 COM port driver dies, and I have to shut down and
- reboot (since device drivers can't be reloaded on the fly, grrrr).
-
- This is in TE/2, and occurs when alot of crap comes in on the port, so
- I suspect the 1000 interrupts thingy.
-
- The help page for the com driver says:
-
- device=c:\os2\com.sys (n,addr,irq,S)
-
- where S = D for DEinstall or I for Ignore. It doesn't explain what these mean!
-
- If I set it to D, and com.sys deinstalls, will it be reloaded?
- If I set it to I, should this annoying com.sys death be happening?
-
- I've got it set to I, but it doesn't seem to be ignoring 1000 consecutive
- interrupts. I'll try D, but I don't know what it'll do.
-
-
- So can anyone give more detail about what the two options do?
-
- jpm
-
-
- --
- ______________________________________________________________________________
- ochealth@unixg.ubc.ca
-
-
-