Setting to change when windows thinks a program is not responding?

[Compman55]

When using a program over an RDP connection, the windows are slow to render due to bandwidth and latency that cannot be corrected due to the distance from our main server.

So the operating system (windows 7) thinks it is not responding, but it really is.

Is there a setting that can change how the OS determines when the application / window / session is not responding?

 

[razel]

I assume you already have your Remote Desktop client settings to the lower resolutions, performance set to modem speeds, no local devices in use. Other than that there are the RDP timeout polices buried in the Group Policy (gpedit.msc).

Local computer policy>Computer configuration>Administritive Templates>Windows Components>Remote Desktop Services>RD Session Host>Session Time Limits

 

[Compman55]

Not sesssion timeout. I am talking about when windows thinks a program or a window has become unresponisve. Not when the "session" becomes unresponsive.

 

[cabri]

Unless the OS is killing the application for you; what difference does it make as long as the application eventually responds back to the user.

 

[StinkyPinky]

Until the program becomes responsive you can't use it anyway, so the term "not responding" seems apt. It's not saying it's crashed. This all seems like trying to find a solution to a problem that doesn't exist.