I think this is just reference to file virtualisation. If you try to
write to a file that you don't have permission to write to, vista will
create a copy of it and give you read/write access to the copy. Things
get very confusing if you have one application with admin rights and one
without, even though your code is looking at the exact same filename -
they may see different contents.
Alister Christie
Computers for People
Ph: 04 471 1849 Fax: 04 471 1266
http://www.salespartner.co.nz
PO Box 13085
Johnsonville
Wellington
John Bird wrote:
A friend of mine said this about Vista
"I understand, without confirmation yet, that Vista is intercepting calls to
the Windows API for INI files. I would like to do INI (config) files as I
want to not as Vista is doing. So I am looking for a self made INI file
replacement that does not use Windows API stuff. My goal is simply to manage
INI files as I expect them to behave, so I can avoid unexpected consequences
of Vista. At present I am using Delphi's built in TINIfile, which I am
guessing calls Windows API code."
I think in my brief tests of Vista there were issues writing to settings
files including .ini files but I thought it was to do with fil permissions -
that is once I allowed full access to the folder where the ini files were
then all seemed to behave.
Anyone have more information on if and how Vista changes access to ini
files? Does D2007 contain changes to Tinifile to cater for this? Any
issues for earlier versions?
I am guessing if Vista has changed the rules is maybe similar to how it
restricts access to certain parts of the registry hives...
John
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
