Hi! I found something interesting on the internet about the "Error locating config file--bad path" (I got the same error), look:

SYMPTOMS
When starting Visual FoxPro, the following error can occur:

"Error locating config file-bad path?"
If starting FoxPro for Windows 2.x, the error will be:
"Invalid path or file name".
After clicking OK, Visual FoxPro starts and runs properly. FoxPro for Windows 2.x will not run, and terminates with a General Protection Fault. When starting an executable file built by any of the FoxPro products listed above, one or more of the following errors can occur:
Error locating config file-bad path?
Invalid path or file name
A DO dialog box appears
If the .exe file was created in FoxPro for Windows 2.x or Visual FoxPro 3.0, a general protection fault can occur after the above errors appear.



CAUSE
This error message is by design. The problem is the contents of the PATH environment variable. The error is most commonly caused by a missing semicolon, which divides the directories that make up the Path statement. Other errors in the PATH may also cause the error.



RESOLUTION
Edit the Path statement and add the semicolon. If the operating system is Windows 3.1, Windows 95 or Windows 98, the Path statement will be found in the Autoexec.bat file. If the operating system is Windows NT, go to the System icon in the Control Panel. In Windows NT 4.0, after you open the System icon, select the Environment tab then check the contents of the Path variable. Windows NT also reads an Autoexec.bat file if one is present. Look for a SET PATH statement in the Autoexec.bat file if the Environment tab Path variable does not contain any visible problems. Other types of batch files or login scripts may also reset the path. You can view the current path by opening a command prompt and typing SET PATH.



STATUS
This behavior is by design.


Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q163801

Hope it helps!

Simon Beaudoin, Diane's helper