Timer Causes Dropped File Output

[kkleinfelter]

It appears that if a timer fires while a FileAppend is writing to a file on a network shared folder, the I/O does not complete.

How can I ensure the file write gets resumed and run to completion? Do I need to wrap all my calls to FileAppend with "Critical On" and "Critical Off"?

I don't know for CERTAIN it is the timer event causing the FileAppend to intermittently not write the output. What I know for certain is:
* I use timers.
* I use FileAppend to a network shared file.
* Something like 0.01% of my FileAppend don't have any effect.

[boiler]

One thing you can do it set a global flag (let's call it Busy) equal to 1 at the beginning of your FileAppend process and set it to 0 at the end. Then have all of your subroutines/functions that are launched by timers check to see if the Busy flag is set, and to not do anything (return from the subroutine or the function) if it is busy.

[swagfag]

barring ahk bugs, how would a timer subroutine interrupt a fileappend? the fileappend blocks until finished.

post code

[just me]

FileAppend -> Error Handling

[v1.1.04+]: This command is able to throw an exception on failure. For more information, see Runtime Errors.

ErrorLevel is set to 1 if there was a problem or 0 otherwise.

A_LastError is set to the result of the operating system's GetLastError() function.