J
Jon Rusten
At our company we got newly installed servers. One 2-processor server with
Windows 2000 SP3 as file/print and one 2-processor server as
TerminalServices SP3.
We are using a DOS-based application for administrative use. This
application's files resides on the W2k f/p server.
We got a strange behaviour on our server. This is a DOS issue. Then starting
this DOS-application, or starting a dos-session with command or cmd, the
screen is updated slowly. After typing a word or a line the screen is
updated slowly. And the same happens if scrolling in text.
Running the dos-application in full-screen removes the problem and it is
totally ok.
Running the application directly on the w2k server gives the same result.
Running the application on a XP or W2k ws function perfect.
Anyone having any good ideas?
Regards
Jon
Windows 2000 SP3 as file/print and one 2-processor server as
TerminalServices SP3.
We are using a DOS-based application for administrative use. This
application's files resides on the W2k f/p server.
We got a strange behaviour on our server. This is a DOS issue. Then starting
this DOS-application, or starting a dos-session with command or cmd, the
screen is updated slowly. After typing a word or a line the screen is
updated slowly. And the same happens if scrolling in text.
Running the dos-application in full-screen removes the problem and it is
totally ok.
Running the application directly on the w2k server gives the same result.
Running the application on a XP or W2k ws function perfect.
Anyone having any good ideas?
Regards
Jon