>Complementing the previous message...
>
>>I still have an issue with COM components. I'm looking for a way to COM components to work on those restricted workstation. The molebox solution seems to fail on this one.
>
>>Any way to get a COM dll to work on a workstation with a read-only registry?
>
>Quite a lot of corporate IT departments now restrict workstation user rights to the bare minimum. It is possible to copy code but regsvr32 dlls or ocx-es will fail miserably, making COM components non grata. I'm looking for a way out of this.
>
>FrançoisOnly solution is to use an Admin install. These restrictive environments have an IT Staff that takes care of it and is the only one allowed to do software installs.
Same happens to me at home for example, where I do not run my laptop and home-net as Admin (you don't either, right?), for security reasons. Every time I need to install something new I have to re-login as Admin. Most of the time the installer will sense this and tell you you do not have sufficient rights and must be admin. Other times it will start the install and fail at some point, having to undo, as you have already found out.
