weiman@jargon.whoi.edu (Bob Weiman) (01/16/91)
About once a day I get one of those Windows
messages "This application has violated system
integrity..." from one of my DOS windows. This
forces me to close all of my DOS windows, exit
Windows, and reboot my machine.
1) Does anyone know what this message really means?
2) What causes this problem?
I have found that this sometimes happens when I have
several DOS windows open on my machine and it has
been sitting inactive for some time. I then click
on one of the DOS window and as soon as I begin
to type, I get the system error message. This is
not a repeatable problem, because it only happens
occasionally. Also it doesn't seem to matter what
particular application is running in the DOS window
as far as I can tell.
Also, as soon as one DOS window screws up, All DOS
windows become unusable. Window apps still work though.
I am using a Dell 425E, 486 computer with 8 megs of RAM
--
Bob Weiman Internet: bweiman@whoi.edu
Woods Hole Oceanographic Institution
Deep Submergence Lab
Woods Hole, MAjls@hsv3.UUCP (James Seidman) (01/17/91)
In article <1991Jan16.143721.7586@netnews.whoi.edu> weiman@jargon.whoi.edu (Bob Weiman) writes: >About once a day I get one of those Windows >messages "This application has violated system >integrity..." from one of my DOS windows. This >forces me to close all of my DOS windows, exit >Windows, and reboot my machine. > >1) Does anyone know what this message really means? >2) What causes this problem? It usually means that a VM (VM = "virtual machine", the state your computer is in when running a DOS app inside Windows) has suffered stack overflow, executed an illegal instruction, or the like. It generally happens at the same time that your computer would hang if you were not in Windows. >I have found that this sometimes happens when I have >several DOS windows open on my machine and it has >been sitting inactive for some time. I then click >on one of the DOS window and as soon as I begin >to type, I get the system error message. It sounds like you are using a TSR which is getting screwed up. Command-line editing TSRs are especially notorious. Windows tries to save space by having the DOS sessions share the areas used by TSRs. Then when one session's TSR updates its memory, the other sessions' TSRs get screwed up. If this is your problem, one solution is to switch to something designed to work correctly in multitasking environments like 4DOS. Another is to get a memory manager like 386Max from Qualitas which will automatically do "instancing," which means making a separate copy of the TSR for each DOS session. A third is to run the TSR after you start each DOS session, rather than before you load windows. -- Jim Seidman (Drax), the accidental engineer. "It doesn't have to work... they'll be paralyzed just from laughing at me." - Dr. Who, _Shada_ UUCP: ames!vsi1!hsv3!jls INTERNET: hsv3.UUCP!jls@apple.com