
Applications Compatibility Scripts for Windows NT Server, Terminal
Server Edition
Multi-User Object Manager not to decorate objects created by this application. An
example is SNASRV, the executable for SNA Server. All its objects need to be
registered as system globals (non-decorated) so the flag value is set to 0x200.
Return systemroot, not user's WINDOWS directory 0x00000400
This is the most commonly used application flag aside from the version flags.
Normally, in Execute mode applications are told that the user's Windows directory in
the user's home directory is the systemroot. This will cause some applications to
fail because they need to find something in the real systemroot. An example is
CINMANIA, the executable for Cinemania.
Limit the reported physical memory (GlobalMemoryStatus) 0x00000800
Some applications fail if they are told that the default 32 megabytes (MB) of physical
memory is available. Setting a value of 0x800 causes the system to report a
smaller amount of available physical memory. An example is MSACCESS, which
has a flag value of 0x80c (limit reported memory and 32-bit app).
Log object creation to file 0x00001000
When troubleshooting application problems concerning objects, it may be useful to
create a log file of created named objects. Creation of semaphores, mutexes,
events and sections will be recorded. You must also set a system environment
variable called CITRIX_COMPAT_LOGPATH to a valid directory, and the log file
will be written there. This value is not set for any application by default. A further
example is located in the APPENDIX.
Don't put app to sleep on unsuccessful keyboard polling (WIN16 only)
0x20000000
Some 16-bit apps (and many DOS apps) rely on keyboard polling to discover
keyboard activity. This continual keyboard check can greatly impact CPU
utilization. Normally, the system limits this polling. However, some apps will fail if
they are limited. None of the default applications use this setting.
Kommentare zu diesen Handbüchern