What is corrected in the post-Citrix MetaFrame XP FR2/ SP2 hotfix: XE102W012
What is corrected in the post-Citrix MetaFrame XP FR2/ SP2 hotfix: XE102W012 What is corrected in the post-Citrix MetaFrame XP FR2/ SP2 hotfix: XE102W012
1. Some applications, including JavaScript in Internet Explorer and forms in
Microsoft Access, displayed the current time in the server's time zone
rather than converting it to the client's time zone. [#256602]
2. Local time zone and smart card support, which use API hooking, did not work
with some programs. This occurred most frequently with applications created
using Borland development tools. The API hooking mechanism assumes the
existence of data in a specific part of the image. If that data is not
present, local time zone and smart card support fail. With this hotfix, the
API hooking mechanism looks for the required data (when necessary) in an
alternate part of the image and local time zone and smart card support are
successful. [#244817]
3. Some third-party applications became unresponsive or otherwise behaved in
an unpredicatable or undesired manner. This is related to the way these
applications support API hooking. The problem is dependent upon how these
applications are implemented. To prevent problematic programs from using
API hooking, set the following registry value.
WARNING! Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Citrix cannot guarantee
that problems resulting from the incorrect use of Registry Editor can be
solved. Use Registry Editor at your own risk.
Navigate to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook
Value Name: ExcludedImageNames
Type: REG_SZ
Value: Badapp1.exe, Badapp2.exe, Badapp3.exe
[#257394]
This is a fix Incorporated In Citrix MetaFrame XP Feature Release 3 (FR3)/ Service Pack 3.
User login
Who's new
- maczugaher
- locksgydff
- isotheces
- ahundredyears7
- Jacomijntjefu