This happens to me from time to time (mirc.ini getting lost/corrupted, but not related to sleep mode), usually because I get mIRC to crash in some ways (if you just run an infinite loop and force mIRC to shutdown, it will almost never corrupt/replace/whatever mirc.ini (I don't know for the others INI files, I don't use them much)).
Well, yesterday, somehow, I got very low on space on C:\ (explorer was reporting 0 mb free, mIRC is running with an old install type on C:\mIRC). I was testing some stuff (7.39), I manually disconnected from a server and reconnected, mIRC froze for 3mins+ after the reconnection.
In the meantime I was eventually trying to free some spaces on C:\, knowing mIRC wasn't really in an infinite loop state and knowing it would eventually get back to a normal state, which happened. Well then I noticed mIRC was using 400 mb in ram which is very unusual for me (mIRC usually stay between 20-50 MB max) and I decided to reboot with /exit -nr.
After mIRC reboot, I saw that my font setting was gone, otherwise everything was there. I was still a bit low on C:\ at this point, I /exit'd -nr once again, this time the whole mirc.ini was gone.
Well if mIRC makes sure the temporary file is created without any problem, how come it's even possible to see that kind of stuff happening? Shouldn't mIRC ran into a situation where the user requested an exit of the application and mIRC is recieving an error of some kind when trying to save the INI file (either for the temp file, or maybe just for the renaming of the temp file to mirc.ini)? Wouldn't that mean mIRC is exiting anyway, without saving properly?
While I think the saving of INI files could be handled better, I agree that mIRC should back up mirc.ini (and eventually others INI files) before renaming the temp file, at least if anything goes wrong, we would still have a back up "~mirc.ini" we can rename manually.
Last edited by Wims; 02/02/15 11:26 PM.
