I/O Operation Failure 2

[hceonetman]

Attempting to update a project, I get the msg 'I/O operation failure', when doing the build project, build app or create exe. It does not create an exe file. The message gives NO details (Help says MS-DOS failed to perform a file or hardware operation). It is possible that some file locations have changed, but the error does not specify what is missing. I have tried to rebuild the project from scratch, starting with the main calling program, and locating all supporting files as they are requested. This does not work. For obvious reasons, I'd like to avoid giving users the source code and Mfoxpro.
Thanks for any suggestions.

 

[rgbean]

It would help to know what version (and type of) FoxPro you are working with. (FP 1.0 -> VFP 6.0 SP5 ?) Additionally, the OS you are working under might provide some clues as to the real problem. Did it ever build correctly on this system, or did you move the project (and it's files) from a different system?

Rick

 

[hceonetman]

Sorry, first post. First of all, thanks for your quick reply.
I'm running Foxpro 2.6 with the 'a' patch on Win98SE. It's running on a PIII, approx 500MHz. Have also patched for running on a faster processor with Microsoft's Patch26. The files HAVE been moved - I hoped that creating a new project starting with the main calling program would either find all necessary files or tell me which ones weren't found. Doesn't seem to work that way.
I took over this position from previous programmer. Foxpro apps are only part of the job, and my prev. Foxpro experience ended in early 90's with 2.6 for Win. I'm just trying to keep existing apps running.

 

[rgbean]

No problem, I understand that when you have a problem, it's easy to forget not everyone knows all the "background" details.

Well based on what you've given, I still haven't a clue. I've build FPW 2.6a projects with files both completely on a local drive and also on a Novell server on systems up to 733Mhz (so far), without problems. I'd check the project .ERR file or carefully watch the project compile messages to see if there are any additional hints on what file it's dying on (it may be missing, in a different directory structure that expected, or actually corrupted).

Any chance you are using GENSCRNX to create 3D effects, etc.? If yes, then there is a "speed" patch necessary to that program also - it's at our user group page

http://mmfudg.lansing.com/tips_etc.htm

- Files - GENSCRNX.ZIP.

Rick

 

[ChrisCarroll]

I know this is a bit laborious, but my next steps would be:

1) try copying everything to a different machine and see if that builds (I wonder if it's caused by Win98's FAT32?)

2) try opening each and every file in the project manually (i.e. modi screen XXX, modi prog YYY, modi etc etc) until you find the one that doesn't open normally, or gives an error message or turns out to be corrupt

 

[thesweeper]

You may have a code line pointing to a drive which does not exist or an empty cdrom/zip drive. CD in, Zip cartridge in or hunt down that code!

 

[hceonetman]

Most of our PCs were partitioned with C,D,E,F drives, with apps on F:. This was pre-FAT32. I'm upgrading all to Win98 with a single C: drive, but many Foxpro apps were hard-coded pointing to F:. I've gotten the same I/O error trying to re-compile several apps. I'm hoping I can use a drive map to create an F: to point to the user's own C:, and this should work, at least until I need to make any other changes. I will attempt to search all components of the project to make sure all files are found and see if that helps. It would be nice if the error messages were a bit more specific, but I get used to that with MS products.
All that aside, I thank the forum members for their quick responses.

 

[rgbean]

After "reflecting" a bit more, you may want to check out the free FixDrive utility on

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

. While this really applies to the executables produced rather than the compile itself, it may provide some more insight into the problem.

Rick

 

[hceonetman]

Thanks. Fixdrive looks interesting - I'll give it a try.

 

[ramani]

Just check if your FoxUser.* is not having a right attribute. Also any other componet of the project doesnt have the right attribute set.

You can safely issue ATTRIB -r myproject\*.* /s

Again, if you doubt having used specific drive letters in software, you can imitate the same with subst command

subst f: c:\mydir
subst g: c:\mydir
..
etc.

This will help to idetify or exclude the probable error cause.

Hope this is of some help to you

ramani