Hello,

I'm trying to get a FoxPro 16-bit DOS application called Bookease to run faster in Windows 2000. We load the program using a batch file:

net use LPT1: \\lawbook_server\optra_r /yes
set foxprocfg=c:\be5\config.fp
cd be5
foxprort f:\db5\bookfox
net use LPT1: /delete /yes
cd\

I tried to look up WOWEXEC.EXE on Google and read how it optimizes
applications running under NTVDM.EXE, such as Bookease. This is the
best page I found: http://www.altf1.co.uk/Technical/DfWTech/Windows_Settings/WinSetWOW/body_winsetwow.html
I tried running WOWEXEC.EXE in command prompt in Win 2000 and it loads
under NTVDM as a child process. Then I ran our batch file, but
Bookease ran in it's own NTVDM process.

Question 1: Will running WOWEXEC.EXE in the same NTVDM process that
Bookease uses to run speed up the application?

Question 2: When we move the mouse cursor over the VDM window that
Bookease is open in, the CPU usage for that NTVDM process flies to
100% (by the way, we need mouse support otherwise I'd just run the
shortcut in QuickEdit mode and it stops the 100% issue) ... is there
anything to keep that from happening other than telling it to run at a
lower priority which would just slow the application even more?

Question 3: Is there any other way to run this 16-bit FoxPro-DOS app
in Win2K in order to speed up the response time AND lower the CPU
usage?

Question 4: Would I see faster results using any other version of
Windows NT 3.51 or 4.0 or XP or …??

Your assistance is much appreciated,
Sincerely,
JohnKaz

NT family uses emulated DOS and I ascertain that XP loathes 16bit software, W2K may have same problem!

Either use pure DOS or look at this NT4 article which may give some tips as NT5 (W2K)is similar at a base level;

http://www.windowsitlibrary.com/Content/226/03/1.html