![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We get interactive desktop telnet windows on servers at our client sites and in-house when our GUI apps come across a vnav or Non-Numeric abort, etc... We want to see these and do NOT want to turn off the reporting by editing the registry. Our issue is that often the desktop interactive telnet windows will be blank and/or take up resources and holds on to that memory space on the desktop. This means when you attempt to move the window it does not refresh/paint and you can only end the processes. We would like to know if anyone else has come across the latter and know why this happens, etc? Thank you, DD |
#3
| |||
| |||
|
|
Could you fill in some blanks? I'm going to guess that you are on D3/NT? What/how are you achieving your GUI --> that will mprobably be the biggest "key" dalila (AT) dockmaster (DOT) com wrote: We get interactive desktop telnet windows on servers at our client sites and in-house when our GUI apps come across a vnav or Non-Numeric abort, etc... We want to see these and do NOT want to turn off the reporting by editing the registry. Our issue is that often the desktop interactive telnet windows will be blank and/or take up resources and holds on to that memory space on the desktop. This means when you attempt to move the window it does not refresh/paint and you can only end the processes. We would like to know if anyone else has come across the latter and know why this happens, etc? Thank you, DD |
![]() |
| Thread Tools | |
| Display Modes | |
| |