Re: Some users can't write to ini file.
From: Anders Isaksson (anders.isaksson_at_REMOVEcej.se)
Date: 01/19/04
- Next message: Pete Watts: "Re: Passing component as parameter"
- Previous message: Arnau Font: "Re: Getting a patch for the differences between two executables"
- In reply to: Perry Way: "Re: Some users can't write to ini file."
- Next in thread: John Herbster \(TeamB\): "Re: Some users can't write to ini file."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 19 Jan 2004 09:03:32 +0100
On Thu, 15 Jan 2004 13:34:57 -0800, "Perry Way"
<no.delphipro.spam@no.spam.earthlink.net> wrote:
>> >I didn't know Windows 9x buffered ini files.
>>
>> Cached or buffered? Windows has always cached the file.
>
>Really? That's not what someone's lead to believe by reviewing the SDK help
>file.
Well, in my experience Win 9x does cache *all* .ini files. Just try
modifying any .ini in Notepad, save the file and *immediately* start an
application that reads the .ini through the API. You may well get the
old values read by the app.
Also, try changing the .ini by running the app., close the app., open
the .ini in Notepad - you may well see the .ini as it was before the
app. ran.
Total mayhem can be guaranteed by letting an app access the .ini both
through the API, and through standard file operations, at the same time
:-)
Counting to three, and waiting for the blink on the disk activity LED
usually works around the 'problem' with external text editing of .ini
files.
-- Anders Isaksson, Sweden BlockCAD: http://user.tninet.se/~hbh828t/proglego.htm Gallery: http://user.tninet.se/~hbh828t/gallery/index.htm
- Next message: Pete Watts: "Re: Passing component as parameter"
- Previous message: Arnau Font: "Re: Getting a patch for the differences between two executables"
- In reply to: Perry Way: "Re: Some users can't write to ini file."
- Next in thread: John Herbster \(TeamB\): "Re: Some users can't write to ini file."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
