>>>I've recently observed some odd behavior on my Windows 98 machine.
>>>
>>>Foxpro 2.6a Windows runtime apps no longer seem to work properly.
>>>
>>>If I run the app in the FPW26 folder, the runtime loads but the app doesn't run. If I run the App (with the foxw2600.esl file in the same folder) I get an IO error which upon cancellation displays a Windows dialog that foxprow caused an exception error. I've tested with simple test apps...it seems that there is a problem with the Runtime. Interestingly, if I run the same app from a Windows XP Professional machine which is mapped to the same folder, I have no problems.
>>>
>>>
>>>I recently installed the VFP8 runtime on the Win 98 machine and turned off a few Startup options. Could this have effected Foxpro 2.6a Windows runtime functionality?
>>>
>>>
>>>I'm using the patched foxw2600.esl file.
>>>
>>>The app ran fine for years...I'm stumped.
>>>Anyone else run into this?
>>
>>(My experience similar to this is with EXE files that I built. It may apply to APP files as well.) Was the app built on a drive other than the C: drive? If you build an app on a D: drive then that drive letter is included in your app. If you then run it on a machine without that drive or if that drive is a CD-ROM with no disk then you will get IO errors. You can either rebuild the app from your C: drive or hack the exe file. Search for drive letters other than C: and change them to C:.
>
>The problem is for all apps, including C: drive apps. I did run the machine in safe mode and everything worked fine. I'll have to do some tests to see what's causing the problem. Could be something related to the CD or external DVD drive.

I had a similar problem years ago.... what caused it was having a CD in the CD drive when building the App. The app, when run, required the CD drive to be present and have a CD present also... yikes!! I solved my problem by removing all CD's and rebuilding....

Tommy