You can use the Application Compatibility flags, described here:
186499 - Terminal Server Registry Settings for Applications
http://support.microsoft.com/?kbid=186499
and if the applications pushes the CPU to 100%, you can try a 3th
party utility called TameDOS, from
http://www.tamedos.com/
Already on NT 4.0 TSE, some DOS applications (but not all) use
100% of the CPU because of continuous keyboard polling. If your
application doesn't do that now, it might not give you this
specific problem on Windows 2000 or 2003 either (but no
guarantees!).
We have also encountered the problem with certain DOS applications
which simply don't run on modern hardware.
The bottomline: you'll have to do some extensive testing, with
both hardware and OS.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"=?Utf-8?B?UmFtYw==?=" <(E-Mail Removed)> wrote in
news:F4F1C9E7-5470-4CB5-9E0F-(E-Mail Removed):
> We have a DOS app written in an old version of Dataflex. We are
> currently running it with difficulty in an older version of Term
> server ( Win NT 4 ). We need to upgrade our server and would
> like to move forward to Windows 2000 / 2003. We have heard
> conflicting reports about the ability to run old DOS apps under
> the newer versions of MS term server. Specifically, that the
> first terminal session running the DOS app will peg the CPU
> utilization. Other reports vary from printing problems to who
> knows what. We're even hearing now that this app has a slow
> response problem with Pentium 4 and Xeon based servers. Is
> there anything we can do in WIndows term server 2000 to address
> any of these potential compatibility issues? Any help is
> appreciated.
>
> Bob McIntire