Re: COSW.INI Corruption


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Brian Levantine on May 31, 2007 at 11:58:50:

In Reply to: Re: COSW.INI Corruption posted by Justin Reynolds on May 30, 2007 at 06:58:40:

Hi Justin. Your point is well taken. I've looked over your filemon log and yes, it looks like there's some confusion. I am a little confused, because while the MS docs do indicate that the API is not thread safe, it does indicate that a FileLock is held by each process. This should protect the file from corruption. Regardless of who is "right" in this matter, we should look for a solution that avoids the use of COSW.INI to store window positions and other often changing information. My solution would be to store this information in the registry (HKCU) along with some other setting we store there. The registry is thread safe.

Comments?


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):






[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]