Microsoft foxpro 26 for ms dos install#
Microsoft foxpro 26 for ms dos manual#

Microsoft foxpro 26 for ms dos manual#

The manual method described in second link should work, but is there a way to do that for already running tasks via command line as well ? The WINAPI calls AFAIR work only the own process ? I guess for some processes you could fix up the start line in msconfig similar to the link example, but that would not encompass everything seen in task manager. Going on the assumption, that I have tasks where core restriction gives better performance due to less switching, restricting the already running tasks (with the default 'all cpu') from trying to run on the core allocated to the high perf tasks should eek out a bit more, even if in reality they should always run on the other cores - but it might make perf measurements more consistent -)) If you limit ntvdm.exe to run on 1 core only, it will go away. >The problem is not CPU speed but multiple CPU cores. Anyway, processor speed probably isn't the issue here - the app runs fine on other recent PCs with fast processors (>3.0 GHz). >Thanks for the suggestion, but I believe that patch is for FoxPro for Windows, not DOS. Dw15.exe, vfpoledb.exe, VFPDOCS.EXE, vfp9.exe or vfp8.exe are the frequent file names to indicate this program's installer. Microsoft OLE DB Provider for Visual FoxPro is included in Development Tools. This free software is a product of Microsoft. This unlimited upgrade applies ONLY to Microsoft FoxPro 2.5 for MS-DOS and Microsoft FoxPro 2.5. The following versions: 9.0 and 8.0 are the most frequently downloaded ones by the program users.

Microsoft foxpro 26 for ms dos install#

>You already running the 2.6 patch for fast processors? If not, you may have to install a FoxPro 2.6 runtime. >We realize this problem could be due to something else but at the moment we're focusing on the hardware because the network guys can't identify any other differences between these new workstations and the slightly older ones on which the app runs as expected in the same environment.

The task manager shows ntvdm.exe running at 25% CPU - 100% CPU on the one core that ntvdm.exe is using and nominal CPU % on the other three cores. Symptoms are that the ntvdm.exe process starts up as expected but then hangs with nothing visible happening in the command window it's running from. >Our old FoxPro 2.6 for DOS app has run happily on 32-bit Windows 7 workstation machines for a long time, but fails to run on the newest replacement workstations that have i3-6100 Skylake processor.

>Is anyone successfully running a FoxPro for DOS app on a machine with the new i3-6100 Skylake CPU?