ini files being renamed randomly

[Michael]

Hello,

I am having a problem with .ini files being renamed (randomly) and causing
applications to crash. The ini files are located within each users windows
folder. For example, say I have an ini file within my folder name
mbprog.ini. Randomly this will get renamed to mbprog.ctx, of course, causing
the application to crash due to the fact it can not find the ini file.

Now I have read the documentation concerning this about if a new version of
the ini exists in the %systemroot% directory then this can happen. The
kicker is that this ini file (mbprog.ini) does not exist in the %systemroot%
directory at all. It resides within each users windows directory only.

Any ideas as to why Terminal Services is doing this??

 

[Netwerkz]

Hello,

I am having a problem with .ini files being renamed (randomly) and causing
applications to crash. The ini files are located within each users windows
folder. For example, say I have an ini file within my folder name
mbprog.ini. Randomly this will get renamed to mbprog.ctx, of course, causing
the application to crash due to the fact it can not find the ini file.

Now I have read the documentation concerning this about if a new version of
the ini exists in the %systemroot% directory then this can happen. The
kicker is that this ini file (mbprog.ini) does not exist in the %systemroot%
directory at all. It resides within each users windows directory only.

Any ideas as to why Terminal Services is doing this??

You sure you don't have some sort of virus??

 

[Netwerkz]

Hello,

I am having a problem with .ini files being renamed (randomly) and causing
applications to crash. The ini files are located within each users windows
folder. For example, say I have an ini file within my folder name
mbprog.ini. Randomly this will get renamed to mbprog.ctx, of course, causing
the application to crash due to the fact it can not find the ini file.

Now I have read the documentation concerning this about if a new version of
the ini exists in the %systemroot% directory then this can happen. The
kicker is that this ini file (mbprog.ini) does not exist in the %systemroot%
directory at all. It resides within each users windows directory only.

Any ideas as to why Terminal Services is doing this??

disregard last message.

Your question popped up a few months back ..
link to google:
<http://groups.google.com/groups?q=.ini+.ctx&hl=en&lr=&ie=UTF-8&selm=063701c
3daf7%2442adce90%24a301280a%40phx.gbl&rnum=2>

link will wrap

 

[Netwerkz]

http://tinyurl.com/28dxx

tiny url thingy is kinda cool.

the link above is to another google search
where Claudio Rodrigues answers similar
question (He's know to be an ACE at Terminal Services).

 

[Michael]

No virus.

You sure you don't have some sort of virus??

 

[Michael]

Hello,

Thanks for the links but there is one catch with my issue:

"The kicker is that this ini file (mbprog.ini) --does not exist-- in the
%systemroot% directory at all. It resides within each users windows
directory only."

Since the .ini does not exist it has nothing to compare it to to even give
it a reason to rename the file to a .ctx extension.

Ideas??

Thanks.