I/O operation failure 1

[theripper]

Hello -
Some of my staff work with an older program, written in FoxPro. One of the users constantly receives the following error: I/O operation failure Ignore or Cancel.

I have found that having any CD inserted into the PC eliminates this error. This is a good work around, but I would still like to understand why this happens.

Any feedback would be appreciated! Thanks ~ [sig][/sig]

 

[foxdev]

Oooh oooh! I just read about this a couple of months ago, and now (of course) I can't remember where. One of InfoWorld's columnists, I believe.

IIRC, there is an OS setting that you can change to affect how it handles checking for removable media.

I know this answer is completely worthless, but I'll bet Dave has encountered this. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br> [/sig]

 

[dgrewe]

I have normally found this to be the result of computer upgrades. (For Example) I just upgraded my computerlast year to one with five-2gig SCSI drives to two 30gig drives and this exact same thing happened to some of my older programs I wrote &quot;A long, long, long time ago&quot; when I was young(er) and knew everything. I found programs hard coded to drive &quot;F:&quot; and &quot;G:&quot;. I had the five SCSI drives in the system to simulate the drive system of a file server in my home.

Your application may have been written on a computer that had 2 hard drives (C: and D. The application is told to look on D: for a file that may or may not exist. The computer is upgraded to one with one large hard drive and a CD rom. The computer can no longer access drive D: untill a CD is placed in the drive.

I suggest you start FP Filer and look for a hard coded drive letter &quot;D:&quot; in any programs, screens, forms, reports, and/or menus. If found replace it with a memvar.

Also FP has a config file that tells it where to index files, create temps files and cursors etc. See if there is a config.fp-FPD or config.fpw-FPW on the computer with the problem and see if that file points to drive D:.
[sig]<p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br>[/sig]

 

[theripper]

Thanks for the feedback ~ I found and reviewed the config.fpw file locally. Everything looked fine. After reading your response, I'm pretty sure it has to do with the mappings of drives.

This particular PC has many devices. Also, due to all the network drives, I had to push the CD ROM to the R:\ drive.

Thanks again ~ [sig][/sig]

 

[BRB]

I/O Operation Failure is caused by drive maping issues. Mapping the users CD Rom Drive to any letter other than D: will eliminate the problem

 

[yorkie]

You can download a utility to fix this problem on the following site:

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

[sig][/sig]

 

[dgrewe]

FoxPro Applications causing I/O errors just because the CD-ROM is not maped to drive D: is A Wild Story (I would say somehing else but there may be children present). I have a computer beside me right now with 2 IDE Hard Drives (C:, D, 7 SCSI Hard Disks (E: - K, A copule of Network Drive Letter connections(L: - P, A SCSI Tape Dirve, a SCSI CDROM and a SCSI CD-ROM Writer. The CD's are drive R: and S: I do not have a program loaded to fake the system into thinking the CD-Rom is a Hard Drive. It constantly runs 4 FoxPro applications that run 24hours a day / 6 days a week. It has Yet to crash because of a CD-ROM drive mapping. -P)
[sig]<p>David W. Grewe<br><a href=mailtoave@internationalbid.net>Dave@internationalbid.net</a><br>[/sig]