Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucsdhub!jack!crash!paul From: paul@crash.UUCP Newsgroups: comp.sys.ibm.pc Subject: TSR File I/O Difficulties Message-ID: <2084@crash.cts.com> Date: Fri, 4-Dec-87 14:58:58 EST Article-I.D.: crash.2084 Posted: Fri Dec 4 14:58:58 1987 Date-Received: Wed, 9-Dec-87 01:00:11 EST Reply-To: paul@crash.CTS.COM (Paul Palacios) Organization: Crash TS, El Cajon, CA Lines: 22 Keywords: HELP! Summary: WS4 and suih progs cause DOS critical state I am having a problem with with a TSR doing file i/o. I already am aware of the critical flag in DOS and the DOS Idle interrupt, but still problems exist. The actual functionality of performing file i/o works great. The problem is noticed with such programs as WordStar 4.x. When WS is in operation, my TSR is in belief that every attempt to do file i/o must be postponed because DOS is in a critical state (via the critical flag). This is quite frustrating because a person may sit in WordStar for a very long time and it is not possible to make my file i/o que buffer big enough without taking up rediculous amounts of memory. Getting around this must be possible. Out of curiousity, I tried SideKick under the same conditions to see how the file i/o it performs reacted. It worked fine! If anyone at all has any information regarding this issue, please post or send me mail Any information at all would be greatly appreciated! -- Paul Palacios UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!portnoy!paul POBox 842,(CA) INET: paul@portnoy.cts.com VOICE: wk:(619)458-0230 Bonita, 92002 ARPA: crash!portnoy!paul@nosc.mil hm:(619)420-5776