Caché Upgrade Checklists - InterSystems Documentation

Administrators11.1.24.1 WindowsHelp Format ChangeThe usage information for the commands css.exe and ccontrol.exe is now provided in HTML. Executing either commandwith a first argument of “help” will now invoke the default browser to display the help file.New Japanese LocaleThere is now a new Japanese locale for Windows (jpww). It is like the standard jpnw locale except that the default forTelnet Terminals is UTF8 instead of SJIS. This new locale is now installed by default for new Japanese installs on Windows.Upgrades to Caché maintain the previous locale.Changes to %path% Environment VariableTo improve system security and the uniformity of locating Caché components, version 5.1 adds the file system directoryname\Program Files\Common Files\InterSystems\Cacheto the %path% system environment variable on Windows systems. It is added to the HKEY_LOCAL_MACHINE hive sothat it applies to all users of this machine.Visual Studio 7.1On Microsoft Windows, Caché is now compiled with Visual Studio 7.1. User applications communicating with Caché (forexample, those using the CALLIN or CALLOUT interfaces) must be upgraded to this version of Visual Studio.11.1.24.2 Windows XP ProfessionalMicrosoft Mapped Network DrivesMapped drives are not supported on Windows XP Professional — Due to security improvements in Windows XP Professional,Microsoft discourages users from using mapped drives; using them results in different behavior than in the past.We recommend that XP Professional users follow these procedures to access mapped drives from the GUI tools or fromtelnet sessions:• For remote mapped drives, enter the user name and password in your configuration as before. In addition, edit theZSTU startup routine and add this line for each drive you have mapped.Set x=$zf(-1,"net use z: \\someshare")• For virtually mapped drives, add this line for each drive mapped with the subst command:Set x=$zf(-1,"subst q: c:\somedir\someotherdir")You cannot add more mappings after startup.Important:The above procedure is meant for development situations where only one user is expected to log on toWindows, and the user name entered in your configuration is the same user. In any other situation, suchas a Terminal Server environment, the results are unpredictable.The following notice from Microsoft refers to this problem:[Redirected Drives on Windows XP Professional: On Windows XP Professional, drive letters are not globalto the system. Each logon session receives its own set of drive letters A-Z. Thus, redirected drives cannotbe shared between processes running under different user accounts. Moreover, a service (or any processrunning within its own logon session) cannot access the drive letters established within a different logonsession.]Another approach to using the mapped drives is to start Caché like this:Caché Upgrade Checklists 243