"immi" <(E-Mail Removed)> wrote in message
news:c84931ba-d529-4d97-98e2-(E-Mail Removed)...
> Suppose abc.txt file is used by different programs (say Prog1, Prog2,
> Prog3). abc.txt is placed in local application's folders of Prog1,
> Prog2 and Prog3. On copy of abc.txt is found in system32 folder as
> well. I have observer that if OS find a file in system32 then it
> ignores the file present in application local folders. To access
> abc.txt locally I used Prog1.exe.local file and place the path of
> abc.txt in Environment Variables path. Even then it always go for
> system32 path.
This looks like a defect in programming
1. If PROG1 is configured to load ABC.TXT from
filepath#1 and write it to the same filepath, and it
(instead or additionally) writes a copy to /Win/System32
that is a defect in PROG1.
2. In general, we do not expect any data.txt files to be
written anywhere in c:/Windows (usually reserved for
OS files including configuration instructions.)
> Is there any way through which system32 path can be ignored and
> abc.txt can be accessed locally? Infect abc.txt is copied in system32
> folder by some other mean which I can’t restrict. Also these files
> have different configuration settings.
This is not sufficiently clear. E.g. data files usually have
no "configuration settings:" these are configurations of the
installed program that reads/writes the data file.
--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)
|