Some of the VFP runtimes may have been inadvertantly removed. I recently uninstalled a demo for a VFP 6 project (I think it was a WYSE installer) . The uninstall broke my VFP. Or - I could of ended up my mistake in the runtime folder and did an "ERASE *.EXE" from the command window.

At anyrate, I re-installed VFP 6. Try to unistall. The reinstall VFP and the service pack.


>Yep, when i get a moment I'll check all the config related items.
>Thanks
>
>>If your problem still persists, you can try to add one of the following command line switches:
>>
>>-C ignores config.fpw (vfp -C)
>>-Cc:\vfp7\config.fpw where you must change c:\vfp7\config.fpw to point to your vfp7 config.fpw
>>-A which ignores all configuration file and windows registry settings.
>>
>>If -A does the trick, you probably have a reference to D: in one of the tools\options settings.
>>
>>>Ok, will double chack that. Don't remember putting any reference to D: in Config.fpw but will certainly check it when I can ...
>>>
>>>>Hi Bill
>>>>
>>>>Check CONFIG.FPW for references to D:
>>>>
>>>>>I have VFP6 (SP5) on a Windows XP Home PC and when I start it up I get an error dialog from VFP stating something like "There is no disk in the D: drive ...". Don't remember the exact text. D: drive on this machine is the CD-ROM. I also Have VFP7 (SP1) on this machine and get no error on startup. Any idea what causes this?
>>>>>
>>>>>Thanks,
>>>>>Bill