Yeah I don't want to use shared ressource access with INI file, I was merely introducing the shared ressource idea using mIRC scripting
Without a dll, one could probably achieve something with DDE but DDE isn't really the best way to go about it.
If a dll can be made to allow us to create mutex or similar, it could be implemented in mIRC scripting
Clearly not a priority for you but for the rare time one need that, it would be great to have it, note that one might very well understand the mutex concept while still being unable to create that dll.
The tricky part is deciding what the application should do if the resource is currently in use. Should the application freeze until access is granted? Should it store the data elsewhere temporarily and attempt to update the file later? And so on.
As far as mIRC scripters are concerned, that's their problem
but I'm curious, what was mIRC doing before and what is it doing now? aren't INI file in memory anyway, wasn't the problem just flushing to disk?