jmorriso@fs0.ee.ubc.ca (John Paul Morrison) (07/15/90)
I'd like to know just how robust standard and enhanced modes are. They are protected mode rite?? SO a program shouldn't be able to write outside its memory space, and do other nasty things? And shouldn't the kernel be able to step in if a program gets out of hand. What is actually hapenning when you get an internal appli- cation error message? Most of the time, the program gets nicely shut down by windows, but sometimes the whole system get brought down in a nice freeze. Is the offending program causing this, (which seems strange in protected mode) or is the kernel locking up because it doesn't know how to handle a situation. Now for the bug or anomaly: I was using a non windows 3 program (an hp calculator) when I noticed how it handled domaim and range errors etc. If I type 0 log or -1 sqrt for example, you get a range error popping up in the top left of your screen: log10: SING error or sqrt: DOMAIN error, pretty standard for normal C programs, but then you shouldn't be able to do a direct write to the screen! This is protected mode right?? Tell me how a program can just bypass all the windows output routines, unless this is some standard debugging procedure for Windows to pass these error messages through. The error message actually scroll down the screen like a tty, in the regular dos character set. The only ex- plantion I can think of is analogous to X windwos: all weird mes- sages get echoed to the console in X WIndows, and if you don't have a console, they just pass through to the screen and overwrite windows. Obviously, WIndows has no console, so this might be what's happening. Just Curious... John Paul