Posted by Justin Reynolds on May 30, 2007 at 06:58:40: Uploaded files: 1
In Reply to: Re: COSW.INI Corruption posted by Justin Reynolds on May 30, 2007 at 06:28:48:
maybe this'll help: per microsoft, "WritePrivateProfileString" (i assume the api call you're using) isn't thread safe, and is vulnerable to race conditions.
here's some discussion:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=673461&SiteID=1
http://groups.google.com/group/bit.listserv.toolb-l/browse_frm/thread/a36e01d3da2902de/2bdbd52537e6a715?lnk=st&q=WritePrivateProfileString+corruption&rnum=1&hl=en#2bdbd52537e6a715
attached is the log from sysinternal's "filemon". i was monitoring any activity to "cosw.ini". i opened 3 comet sessions/windows, moved the toolbar to different places in each one. closed the 3rd (last) session at 9:49:45; pid 5976 updates the ini.
closed the 1st session at 9:50:08, which in turn closes the 2nd session. pids 904 & 1336 argue over who's got the most accurate ini.
reproduce this enough scenario enough times, and you'll corrupt the ini.