Skip to main content

Running VFP 9 with Windows NT 4?

Saw a recent note from Woody

You may know, VFP9 (IDE and RT) are not working on NT4 based
systems due to a not resolved API call. This may get fixed in a possible SP, but until then maybe this statement by Rainer Becker (Leader of the German FoxPro Usergroup) may be of interest:

Please inform your readers/customers/users in your next issue / email that a free patch for VFP 9.0 is available to run it on NT 4.0.

The patch has been created by the German FoxPro User Group ( and can be found at the dFPUG document portal in the directory

so VFP-developers do not need to wait any more to buy an update of VFP 9.0 if they or their customers still use NT4.

Some Technical details what the patch program does:

1. vfp90nt4.dll is copied to Windows system directory
2. vfp9r.dll and vfp9t.dll in VFP-Runtime folder at "Shared Files" are
3. vfp9.exe in VFP-program directory is patched.
4. vfp9.exe, vfp9r.dll, vfp9t.dll in same directory are patched.
5. backup copies of all files are made (extension .001, .002 and so on)

A patched VFP9 file will run on any operating system as long as it can find vfp90nt4.dll in the windows system directory or the current directory. The patch program can be forwarded to users if needed but you are not allowed to offer it as an own download - please link to the above mentionend directory instead. Patching executables might cause problems with virus filters and/or licence agreements. No guarantees whatsoever for patch program and results.



David Fung said…
A quick search in Google directed me to this post of yours, which fixed my vfp9 can't run on NT4 problem.

Thanks Andrew (and of course the German User Group).

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…