Quote
ust an observation about the possible reason for not stripping $crlf from writeini being that people might have wanted to write 2 items at the same time. If that were happening in the beginning, the change from API to internal routine would have made that more difficult

Yes, there were other issues and compromises to consider as well.

One of the issues with the Windows INI API is that although it interprets/interpreted semi-colon prefixed lines as comments (and at some point may have interpreted trailing semi-colons in lines as comments) when reading an INI file, it does/did not support writing comments to INI files. If the INI API was used to write items beginning with semi-colons, they would then be treated as comments when reading. Since scripters, and some of the default INI files, used semi-colons for comments, these had to be interpreted as such. In addition, since comments are not tied to a section or item, whenever sections or items are/were deleted, re-created, etc. the comments would end up in the wrong place in the INI file.

I have made a change to the next beta that should fix the caching issue you are seeing.