CompuServe Messages

Don, I've discovered that if you use WriteProfileString while WIN.INI is also an open file in an app, a lost chain is created on the disk drive. When you look at this lost chain, it will always start with whatever data WriteProfileString was writing to win.ini. Perhaps there needs to be a warning somewhere that win.ini cannot be an open file whenever this api call is used. Along these lines, is there any way to prevent WriteProfileString from completely re-writing win.ini to disk and re-reading it after every WriteProfileString call? In my case, I manipulate the softfont section of postscript ports in win.ini and this can entail adding as many as 175 lines per port to win.ini. Using WriteProfileString to do this takes an eternity so I've had to resort to reading win.ini as a binary string and doing my own parsing/manipulation with a single call to WriteProfileString at the end. –dennis There is 1 Reply.