hmmm...

If I am reading you guys a'right, what's happening is this:

The Setup Wizard is calling an API call to determine the system directory and gets the directory 'C:\WINDOWS\SYSTEM'. It then tries to write the VFP300.ESL file to that directory and gets the error 'no such directory'.

Methinks someone's computer is right royally screwed. Interestingly, there are at least 3 computers showing the same symptoms. I presume some bad installation of something has seriously corrupted them. probably an IE beta .

I suspect there is nothing I can do. I could put the ESL file in the same directory as the exe (FPW style), but I suspect I will still get the same problem trying to register the OCXs that ship with the app.

Sadly, it is *my* problem that some computer 1000 miles away that I have never seen or touched is corrupted. I'd really like to find out what it might be so I can safely say "it's your problem - fix it". That will probably never happen.