Hi All
Does anyone know how I tell the P&D Wizard to install so that all logged on users can use the program?
Currently the wiz works, but only the user who installed the program can see it in their program list.
Thanks
Printable View
Hi All
Does anyone know how I tell the P&D Wizard to install so that all logged on users can use the program?
Currently the wiz works, but only the user who installed the program can see it in their program list.
Thanks
The P&D Wizard doesn't have an option to do this. Not sure about Inno. You'd need to copy the Start Menu items to "Documents and Settings\All Users\Start Menu"
Thanks SBD, but there are also a couple of dll that the other users need access to and this would not give it to them. I'll keep looking>
FW
I didn't mean to copy/install the whole app to "All users" :lol:, just the shortcuts that would normally appear after installation. The P&D wizard's installer (Setup1) can be customised to run other exes etc (which you'd have to write) to copy the shortcuts. It might be easier to use a different installer though.
EDIT: Come to that, you'll probably be able to customise the installer to put the shortcuts directly into "All Users".
Yes, I knew what you meant. The shortcuts not really a problem. It seems that the Setup is not giving permission for other users to use the custom controls that the main exe uses.
Hmmm, not sure about that. Is the "Install location" right ? (Clicking on "$(WinSysPath)" etc gives more options.)
Moved to Application Deployment
You can easily set the Start Menu shortcuts to be installed for All Users in the PDW. When you're on the Shortcuts panel of the Wizard just select (click on) the shortcut folder, then click on the properties button, then choose "Common" there.
As far as your components go though... what OS is this? I.e. is this Vista?
If not Vista, was the setup run by an admin user or a standard user?
The OS is XP, and the setup was run by an admin user.
Any admin user can use the application, they all seem to have access to the ocx. But any standard user does not have access to the ocx, and that's the real problem.
FW
Well geeze. Can we assume the component libraries were installed into System32? The program's TARGETDIR under Program Files?
And in any case, what do the Permissions on these files say for Users? Execute at least I hope.