Hi,
For the sake of testing the performance of some library I have a suite for which times the functions etc. My test suite is written in Turboc3 hence my suites automatically runs under the DOS(virtual or whatever) on windows 2000
However the results differ to what is actually experienced when using the libraries in windows based applications
Is it because it is running in DOS or else.
In general what are the overheads when we run DOS based applications on Windows 2000

Thanks in advance
~ Nilesh

"Nilesh" <anonymous@discussions.microsoft.com> wrote in
news: 2A9CE1AA-A45F-4823-9933-2DDF97690A3F@microsoft.com

It depends on what other applications are running and what
priorities these have.
There is also a timing/priority difference for running "dos"
commands full screen (ALT-ENTER) or in a "dos" window.
Last but not least, there is no MS-DOS in any NT based Operating
System (NT, W2K, XP), it is a command shell, which has to some
level compatibility with MS-DOS commands. The Windows
environment rules and controls memory access and hardware use.
The only DOS environment exist in a MS-DOS installation, or
W98/98/ME started in DOS mode.

Thanks
So I assume that the full screen (alt+enter) has a higher priority then the window mode.
Also for having performance comparable to windows environment I should run the applications in window mode
Again this is assuming that the dos based application in window is equal in priority to that of any other windows based application
Also does it make a diffrence if the window is kept active

"Nilesh" <anonymous@discussions.microsoft.com> wrote in
news: BB2F75EC-6B67-4BB5-AA19-07639AE633E0@microsoft.com

I do not exactly know what priorities Windows assigns to the
various Command Window options (as active Window, non active
Window or as full screen).
At least I know there are noteable differences.
I guess if time measurement is critical, the solution with a Dos
based program is far from accurate.
You should look into a Windows based program, were you have more
control over how it is handled by Windows.
I'm no programmer, my guess is Visual Basic or Visual C is more
what you need.