Thanks, I was able to reproduce this issue. It was due to the file writing routine not propagating one of the write error checks back to calling routines correctly. As far as I can tell, it would only have occurred in a disk full context. This fix will affect a number of features. For example, in older versions of mIRC, if you use /write on a full disk, it will not report an error. In the next version, it will. This also resolves the mirc.ini file becoming empty in a disk full context.
