A few months ago I had an intermittent file creation problem related to the HD spinning down after a certain period of idle time. I corrected it by first (before trying to save) getting the 'detailed files' in the target directory. That forced the HD to spin up and then the write would succeed. That was on XP but the principle still applies.

Don't know if your symptom could have a similar cause, but I thought it was worth sharing.

Phil Davis



J. Landman Gay wrote:
I have a client with a problem I can't figure out, and am hoping someone here may know the answer.

A standalone creates a text file in the same folder as the application. This works fine almost all the time on all platforms. However, very rarely, we get an error message on Win98 "can't open that file". If the handler is repeated immediately, the file does get created. This has happened only twice out of hundreds of successful attempts. The machine is not networked, so no one else could have had the file open.

The script basically just calculates a file path, then does "open file <path> for write". That's when the error occurs.

Anyone know what would cause this failure, which corrects itself on a second attempt? We have only seen it on Win98.

_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to