On 2/23/2012 9:42 AM, Anders Hannus wrote: > C:\>path > PATH=C:\oracleinstantclient;C:\Windows\system32;C:\Windows;C:\Windows\System32\W > bem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program > Files\MIT\Kerberos\bi > n;C:\Program Files\OpenAFS\Common;C:\Program Files > (x86)\OpenAFS\Common;C:\Progr > am Files (x86)\Microsoft Application Virtualization Client;C:\Program Files > (x86 > )\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations > MP4\;C:\Progra > m Files (x86)\OpenAFS\Client\Program;C:\Program Files\OpenAFS\Client\Program > > Thus the 32-bit version are used. > > Why are the path this way? > We found that ugrading the afs klient (with msiexec /i newversion.msi /q > TRANSFORMS=LTUcustom.mst) was not successful for 32-bit tools if they was > ugraded after the 64-bit client. Running the installation in the other order > fixed the upgrade problem but left us with a path where the 32-bit files are > found first. > > /anders hannus
The PATH is a result of the order of installation. What is the failure that you are receiving during the install of the 32-bit tools? Note that one of the benefits of the Heimdal package is that it includes both 64-bit and 32-bit components in the same installation. The OpenAFS installation requires a substantial rewrite to turn libraries into assemblies and perform 64-bit and 32-bit installation from the same MSI. Jeffrey Altman
signature.asc
Description: OpenPGP digital signature
