>Yeah, this one's a curse!
>If a module, app, exe etc has been developed, compiled etc on a developers D: drive then Fox will try to validate the D: drive on the run-time machine. Sometimes this is a CD ROM and you must have a CD in the drive to prevent the error.

Perhaps. But recently I've discovered a problem with I/O operation failure. I mapped our development directory from our network to D: long ago and so a lot of my code refers to this D:. One of my coworks D: is an internal ZIP drive. When she tried to open my project or form that referenced D: she'd get the I/O operation failure (as opposed to the "Drive D not ready" as happens with CD-ROMS a lot). I bet that if she had a ZIP disk in the drive it would have given a more meaningful message like ("File not found"). It appears that it just depends on what type of error you'll receive. It just boils down to fox trying to access something inaccessable (whether what's there is relevant or not). I've experience both errors and you just have to be creative when it comes down to addressing it. One measure I was forced to take years ago (as If I'm so old!) was to use a Hex Editor and change all D: references to C:. I felt that was OK because I knew that none of my code existed on any drive other than C:. Needless to say, it fixed the problem and as far as I know no side effect occured due to that solution...