.ini files changed to .ctx files
Craig Macholz
using terminal services or citrix. Most of the client software's *.INI
files are keep in %documents and setting\USERNAME\windows directory.
The system will Rename my *.INI files to *.CTX files.
I need to know why it renames these files and when (it doesn't happen
often). Any help is appreciated
Craig Macholz
cmac...@edulog.com
Cláudio Rodrigues
and updates them whenever a difference is seen. There are some application
compatibility flags that you can set to control how these files are updated.
Below is the information from the TSE Books Online. Look at the bold
highlight:
TERMINAL SERVER ADMINISTRATOR'S GUIDE
Chapter 6 Application Installation and Security
Application Compatibility
Files
Application Compatibility Flags
----------------------------------------------------------------------------
----------------------------------------------------------------------------
------
Application compatibility flags are registry entries that provide the system
with information about compatibility issues with certain applications. Some
of these entries are created by default. Administrators can create new
entries or make changes to existing entries to alleviate some application
compatibility issues.
Here is a brief listing of the various compatibility flags that can be
stored under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\
CurrentVersion\Terminal Server\Compatibility\Applications\app_name. The keys
are created using the applications executable name and flag is stored as a
DWORD value.
Value Description
0x00000001 DOS-based application
0x00000002 OS/2-based application
0x00000004 Windows-based 16-bit application
0x00000008 Windows-based 32-bit application
0x0000000C Windows-based 16-bit and 32-bit application
0x0000000F Any version of an application
0x00000010 Return user name instead of computer name for GetComputerName
0x00000020 Return Terminal Server build number instead of Windows NT build
number for GetVersion
0x00000040 Synchroize user .ini file to system version (1)
0x00000080 Do not substitute user \Windows directory (2)
0x00000100 Disable registry mapping for application or registry key
0x00000200 Per-object user/system global mapping
0x00000400 Return system \Windows directory instead of the user's \Windows
directory for GetWindowsDir
0x00000800 Limit the reported physical memory for GlobalMemoryStatus
0x00001000 Log object creation to file
0x20000000 Do not put application to sleep on unsuccessful keyboard polling
(Windows-based 16-bit applications only)
(1) This setting means add new entries from the system version of the .ini
file to the user's version, but do not delete any existing entries in the
user's .ini file. The default is to delete the
user's .ini file when it is out of date with the system version.
(2) This setting means do not substitute the user's \Windows directory for
the system root directory for any paths inside the .ini file when the system
version of the .ini file is copied to the
user's \Windows directory. Normally you want this substitution done so that
the application uses the user's \Windows directory for all of the
modifications it makes to data or .ini files
Another way is to edit the INI files and save it so that it will have a
newer date and time stamp. You do not have to change the content of the
file. What happened was that if the application installation date is newer
than the date of the INI file, metaframe changes the extension of the file
to ctx in the user's window directory at logon time. Like when you had one
app installed (notes is a good example) and the you upgrade it (from 4.6 to
R5 for example). The Notes.ini file will be older than the application and
MetaFrame will do this. Just rename to .INI, open, save and you are all set.
Or follow what is described on the article above.
Hope this helps,
--
Cláudio Rodrigues
Check my website at http://www.terminal-services.NET
for information on Services, Contracts and Free Support.
"Craig Macholz" <cmac...@edulog.com> wrote in message
news:d41c2020.01081...@posting.google.com...