Discussion Locked

16 bit app running slow on Win2K server

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 16 bit apps that are currently running on an NT 4.0 box. If I run an App on the 4.0 box it takes approximately 57 seconds to run. Yet, on a Win2K box (with dual 800 MHz Zeon processors & 1 GB of RAM - basically doubled of what is on the NT 4.0 box)) the same app takes almost 5 minutes to complete. I have tweaked the performance settings on the 2000 server, but it didn't seem to make a difference.

Does anyone have any ideas?

Thanks!

5 replies

by rkelly

Your 16 Bit apps will run more slowly on a Windows 2000 Machine than on an NT 4 box due to the number of extra threads that are utilised in Win2K. It doesn't matter that you have 2 CPUs as 16 bit apps only use a single thread of execution so they donot support multi tasking (only cooperative multitasking - time slicing in a single CPU).

The easiest way to increase the speed is to raise the priority of the application when it is executed. You can use TaskManager to do this providing you have administrative rights. Select the Processes Tab and select WOWEXEC from the list right click and choose set priority - try using AboveNormal first, if that doesn't make much difference then try high (do NOT try realtime as it will increase the priority of the app to such a level that you will have to restart the machine). Alternatively you can create a desktop shortcut for your application and change the properties through the MISC tab so that your application has more resourses allocated.

by stephen mynhier

Windows NT and 2000 both run 16 bit apps in an NTVDM (NT Virtual Dos Machine), but they do handle them a bit differently, which can obviously result in a performance difference between NT and W2K. Try running the 16 bit apps in their own separate (and unshared) NTVDM for help optimize their performance. To do this, type at the command prompt:
start /separate exeFileName

If that doesn't resolve the performance difference, then
1) modify the properties of the *.pif file and change the "Usage in the Screen" to "Full-screen"
2) modify the properties of the *.pif file and click Windows NT and clear the "Compatible Timer Hardware Emulation"
or
3) modify the *.pif properties by sliding the "Idle Sensitivity" to the left under "Misc"

This discussion is closed to new replies.