ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Windows & Network Issues >> General Windows & Network Issues >> tp5wdba.exe under Terminal Services
http://www.istechforum.com/YaBB.pl?num=1076711912

Message started by rtlond on 02/13/04 at 14:38:32

Title: tp5wdba.exe under Terminal Services
Post by rtlond on 02/13/04 at 14:38:32

When tp5wdba.exe is run in the terminal services and in a data entry menu the processor on the terminal server for the first instance goes to 50% usage. the second person to login to terminal services pushes the cpu to 100% usage.

Any suggestions on how we can reduce the cpu usage using the tp5wdba.exe under terminal services?

windows 2000 sp4
p4 2.4
1g ram
2000i
2002.4

Title: Re: tp5wdba.exe under Terminal Services
Post by aricon on 02/14/04 at 03:32:14

There is no way, but I have been told that this is a false reading. Something to do with how the TAS exe interacts with Windows Kernel 32..... ???

Title: Re: tp5wdba.exe under Terminal Services
Post by alphapkg on 08/16/04 at 11:51:25

Recently, I have been trying to solve this problem with Lynn. Because DBA Classic is using Tas 5.0 it is not a complete Windows compatible language.

The CPU useage goes to 100% when you mount your screen (blue screens) but when you get out of the screen (gray screen) and have nothing open it goes back to 0%.

Our company's solution is to go to Lynn's Evolution product which is built around Tas 6.0, a Winows capitable programming lanuage.

Hope this helps!

Jim

Title: Re: tp5wdba.exe under Terminal Services
Post by thekubrix2 on 11/04/04 at 11:39:33

any resolution regarding this?

Both clients and server (terminal services), jump to 100% CPU usage when a window is up.

Can anyone confirm this is a false reading?

Title: Re: tp5wdba.exe under Terminal Services
Post by aricon on 11/04/04 at 12:05:38

It IS a false reading. Has to do with how TAS (being essentially a DOS application) reports to the OS the amount of CPU cycles and swap file usage.

A way to confirm this is if you try it on a low-end server with limited processor power and then try it on a higher end box, you get the same results.

Now, be aware that although the application is reporting a false reading to the OS, the EXE in fact DOES use a fair bit of power, especially when running through TS. Not 100 but probably spikes up to somewhere in the 65-80% range in reality (depending on just how powerful a box it is being run on).