The program is most likely still running fine, just taking a long time to complete.
The Windows Task manager will display that a program is not responding, even though it is still running perfectly fine. I see this on other programs as well. Perhaps a more informed expert on windows can explain, but I believe it has to do with the program not accepting input interupts from windows while processing.
The white screen is well known to me. It occurs when a very large transaction is taking place and you pop up a different program window then go back to the Rbase session. The screen does not repaint for some reason. If you leave it on that screen long enough, the program will eventually repaint and you will see all is well. Do not take the Task Manager as being correct when it says the program is not RESPONDING! This does not mean it is not RUNNING! Check your CPU usage meter instead.
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
-------------- Original message --------------
> Hi R:Base Users:
>
> Have any of you had your R:Base for Windows (version 7 or 6.5++) go 'white'
> and when you check windows it says the program is not responding? This
> happens when I am running a process (eg. a large append operation) and
> switch to another windows program. This does NOT happen with DOS R:Base,
> just Windows versions. I try to keep with with the lastest updates, but
> this seems to happen regardless of the update.
>
> Scott Stanfield
>
