All,
I also have the same "problem" (Windows mis-behavior ) most often when I'm executing a long running Oracle SQLPlus window. Since I usually know when I'm about to launch such a process, my work around typically is to shrink the window to as small as possible and drag it to a corner of the screen before I hit Enter to actually begin the task. Oftentimes, I'll place the mouse cursor over the minimize-to-the-taskbar button and then left click on it immediately after hitting Enter. The whole goal is to get the long running window out of the way of any other window(s). I've found that not getting this window out of the way of other windows that I might switch to can sometimes prevent a timely switch to the other window(s), especially on a slower PC. If you will be leaving the offending window on screen but shrunken, it helps to resize and/or move the other window(s) to not intrude on the offending window's screen space.
Alan Steward
At 11:42 12/15/2004 -0500, you wrote:
In a message dated 12/15/2004 11:06:01 Eastern Standard Time, [EMAIL PROTECTED] writes:
I am not sure if it is possible, but I agree in that the "white screen" scenario is very problematic. I have users constantly calling me stating that the PC is locked up when it is not. The problem is only that the Rbase session does not repaint the window. Again, perhaps someone with more insight can address this as well. (This does not happen on DOS, because it does not have window sessions to repaint!)
Bob,
I run into this on any number of windows programs. The problem appears to be with windows, and the CPU usage. When it's running at 100%, and the program running has not given a refresh screen, it will stay white for a LONG time, until the task completes, and generates a new screen. It's a little disconcerting, but once you know why, it's just a pain in the neck <g>
Damon
Damon D. Kaufman
