Discussion Locked

Dos crashes windows - win95

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

What are the most common reasons why DOS (shell) crashes windows. Sometimes DOS gives the following error: "Program tried to execute and invalid instruction. Fault location E003:0026.

Thank you

11 replies

by goodspeed

Some reasons that DOS crashes in Windows:

1. Memory problem (mismatch memory for your board).
2. Video card problem (Slow video card, wrong driver).
3. Lack of Hard Drive space for your virtual memory.

I hope this helps.

Albert

by goodspeed

Some reasons that DOS crashes in Windows:

1. Memory problem (mismatch memory for your board).
2. Video card problem (Slow video card, wrong driver).
3. Lack of Hard Drive space for your virtual memory.

I hope this helps.

Albert

by goodspeed

Some reasons that DOS crashes in Windows:

1. Memory problem (mismatch memory for your board).
2. Video card problem (Slow video card, wrong driver).
3. Lack of Hard Drive space for your virtual memory.

I hope this helps.

Albert

by hungry cat

1. Memory leak in your DOS program, maybe incorrect work with memory.
2. See first ;-).
In general i don't know, what reason in additional to incorrect using of memory may cause this problem. Of course, that may be NOT a bug of software, this can be hardware problem (RAM / cashe / CPU in decremental order). To test that use any large DOS game, anyway broken hardware will hung your program. To divide cashe / RAM use simple RAM checker, something like Norton Diagnostics from NU 2000.

by tony hogan

There's a whole host of items:
Programs that try to direct access memory, devices, etc. - pretty much anything that tries to "get around" the operating system. This is a Windows no-no.

I've seen programs that try to direct access video memory to"display faster" that cause this error. I've also run into a host of apps that use third party DOS extenders that are incompatible with Microsofts VMM. Two memory managers can con-exist so Windows abruptly slaps it down [if you're lucky - we've had instances where the two collide and Windows gets trashed].

If you are trying to resolve this, I'd try to find a Windows compatible version of a 32 bit command line utility that will do the same thing.

-tony

This discussion is closed to new replies.