paul@crash.UUCP (12/04/87)
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