>>>>>>>>>>>>>>
>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.
>>>>>>>>>>>>>>>
>
>I noticed that once you run the install, you have to option to cahnge the directory for the install, I wonder if it will change only for the exe and install the dll in the proper place (ie: windows/system)

It alters the .EXE and associated app files; the Windows and System folders normally will be at standard locations, but it's adjustable; for example, the boot disk on this machine is F:, so my Windows directory is F:\WinNT and the System directory is F:\WinNT\System32. My ME boxuses c:\WinME as its Windows directory. Fixed names don't help. The OS resolves them; especially important in WTS and cluster environments.

In the long run, using the locations that be retrieved from the OS makes sense - if we move items under some CSLID, we only have to change one entry; finding where it goes will be easy