Hi Chris,
Thanks for the reply. I guess that it is a clash between the CloudWatcher app writing to the .dat file at exactly the moment when the ASCOM driver tries to access the .dat file - do you agree?
I am hoping that you are Chris Rowland the developer of the ASCOM driver for the AAG CloudWatcher - is that the case? If so, how complex is it to make the driver try again before throwing an exception?!
Thanks,
Gav.