>>>>>>>>>>>>>
>That's correct - VSI uses one of four possible CSLIDs for the target directory, and provides no method that I've seen, even ORCA, to override this. You can use a third party installer that supports Windows Installer technology like InstallShield Express 3.0, InstallShield Pro for the Windows Installer, or Wise to create a custom action that would permit this - VSI 1.1 does not permit you to create custom actions.
>>>>>>>>>>>>>
>
>Thank you for the response. I do use InstallShield Express and I love it and I will go back to it because not every install target contains a "Program Files" directory.

While it may not have a 'Program Files' folder, the OS does map a folder to the CSLID normally associated with 'Program Files' - depending on hpow the system administrator implements the system policies, it could be almost anywhere. In the .NET and Win2K/Whistler environments, the user id will tell the OS where individual CSLIDs reside - in your office, your 'My Documents' folder is assigned properly when you log in, Desktop and Start Menu items might be resolvable with enterprise-wide metadata for managed code.