Microsoft KB Archive/74717

{|
 * width="100%"|

Windows Err Msg: System Integrity Violation

 * }

Q74717

-

The information in this article applies to:


 * Microsoft Windows versions 3.0, 3.0a

-

SUMMARY
There are two major causes of System Integrity Violations:


 * There is a hardware conflict.

-or-
 * An MS-DOS application running under Windows is trying to access memory that it does not have access to in Windows.

MORE INFORMATION
If the System Integrity Violation error message occurs when you run a non- Windows application from Windows in enhanced mode, follow these steps:

  Use a AUTOEXEC.BAT file that looks like:      Path C:\Windows;C:\;C:\DOS Prompt $p$g Set Temp=C:\Windows\Temp This example assumes that Windows is in C:\WINDOWS and that MS-DOS is in C:\DOS.   Use a CONFIG.SYS file that looks like:      Files=60 Buffers=10 Shell=c:\Command.com /p /e:2048 Device=c:\Himem.Sys This example assumes HIMEM.SYS is in the root directory of drive C.  Make sure the MS-DOS application is being called from a program information file (PIF). Check to see if a System Integrity Violation still occurs. If it does, continue with step 5. Otherwise, the application's problem was cleared up in either the AUTOEXEC.BAT, CONFIG.SYS, or the PIF. Try running Windows in standard mode.  If the program runs under Windows in standard mode, add these two lines to the [386Enh] section of SYSTEM.INI and then try running Windows in enhanced mode:      EmmExclude=A000-C7FF EmmExclude=E000-EFFF (for some programs E000-FFFF)  If step 5 does not work and your AUTOEXEC.BAT and CONFIG.SYS files read as above, the application may be incompatible with Windows or you have a hardware conflict of some type.</li></ol>

Additional query words: 3.00 3.0 3.0a 3.00a tshoot

Keywords :

Issue type :

Technology : kbWin3xSearch kbWin300 kbWin300a