Getting I/O Error on win 2K machines & not win xp

[TonyScarpelli]

I am updating and compiling my FPW2.6 application on a Windows 2K machine and then putting it on my company's network. My last .exe update was 9/2005.

My current version is giving me an I/O error on Win2k workstations but not on WinXP workstations, without even getting into the program since I am putting "Wait's" into the first part of the app.

The previous version of the .exe application (9/2005) is not giving me any errors on the Win2K machines, nor do I get any errors on my Win2K development machine from my new version.

Seems like when my IS people updated the system with their unending patches, something was lost or replaced on the Win2K machines.

Are there any .dll files in the WINNT directory that would affect FoxPro 2.6?

Any other ideas about this?

Thanks.

Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102

 

[TonyScarpelli]

After doing a search I found the reason for the error in many places. And this error used to occur many years ago. I used to program and compile my apps on my E: drive and then when I changed my work to the C: drive, that got rid of the error.

However, sometime between my last build and my current build I had a reference to my E: drive, and because some of my users had a CD ROM drive as E:, and because there was no disk in the drive, my user's got an error.

Although one solution is to put a CD into the drive, that wasn't the best solution.

There was actually a solution in this forum, and if you search on "I/O Operation Falure" you'll get the post.

If you go to

http://www.abri.com/foxpro.html

and download the free "FixDrive.zip" file with the FixDrive.prg program in it, the program will remove references to any drive above C: in your .app or .exe file. However, since my app is on a network and references drives above E:, you might want to change the program to limit it to just the D: and E: drives.

Anyway this fixed the problem, but didn't solve it completely. So somewhere, my program is still referencing files on my E: drive; and the problem didn't occur in Windows XP workstations, what's with that?

So, hope this helps someone who still programs in FPW 2.6.

CU


Tony Scarpelli
Clinical Engineering Dept.
Maine Medical Center
Portland, Maine 04102