AW: Where to put an ini file on Win with write access for all users?

Tiemo Hollmann TB toolbook at
Mon Feb 16 03:07:43 EST 2009

Hi Jim,
very enlightening, but still some follow up questions :)

I know the word legacy, but am not sure, what is a legacy file?

What makes Vista to recognize my Ini.xml as a legacy file, could I give it
another name or dir (and being accessed by all users) to not being a legacy
file and being virtualized? - Your proposal to use the registry is right now
a too big redesign for me.

What you told about SQLite, happens by the way also with my Valentina db.
Right now, I just need read only, but I wouldn't know what to do with
read/write and virtualization of the db....

Thanks for your valuable coaching!

> -----Ursprüngliche Nachricht-----
> Von: use-revolution-bounces at [mailto:use-revolution-
> bounces at] Im Auftrag von Jim Bufalini
> Gesendet: Sonntag, 15. Februar 2009 23:32
> An: 'How to use Revolution'
> Betreff: RE: Where to put an ini file on Win with write access for all
> users?
> Hi Tiemo
> > I have an ini file, which should be accessed read/write by every user
> > on the
> > machine, so it can't be in the user dir.
> >
> > I choose specialfolderpath("35") & "\" & myFolder which is on XP:
> > C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\myFolder and
> > on
> > Vista C:\ProgramData\myFolder
> >
> > On a XP machine I don't have write access to this ini file with a
> > different
> > user, as having created the file. I could catch the error and tell the
> > user,
> > he should give permissions to that file for all users. Not nice, but a
> > chance. On Vista I don't get an error when trying to write to that file
> > with
> > a different user, Vista just virtualises the ini file in the user dir
> > of the
> > other user and from now on I have an ini file for each user, what is a
> > mess,
> > because there are common options, which should be the same for all
> > users.
> >
> > Any coaching how to handle this correctly very appreciated!
> Ini files are considered a legacy file structure by Vista. Vista
> virtualizes
> anything it considers legacy under an identical directory tree under each
> user's virtualstore directory. Use the registry instead to store ini kind
> of
> information. The registry was originally dreamed up to replace ini files
> and
> then immediately expanded from there.
> This is why it is so, so, so important that Rev gets around to updating
> the
> SQLite engine embedded in the dbsqlite.dll driver. The SQLite engine
> shipped
> with Rev is pre-Vista and not forward compatible. As soon as you create a
> data file, Vista identifies both your app and data file as legacy and
> virtualizes the database file by making a copy of it. Everything seems
> fine
> until you close your app and launch it again and try to read updated data
> from the previous session. It appears to have all disappeared. What has
> actually happened is all the writes went to the virtualized file(s) - one
> for each user, and you have a mess. This virtualization doesn't happen
> with
> later versions of the SQLite engine.
> Jim Bufalini
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list