Mark, indeed I had hoped that you might somehow know what "magic" ;) is being put in place starting with Vista and know how to "counter-spell" it!
Thanks for your answer and interesting insights ! --- Currently, I am contemplating of creating two branches of installations within the script, such that by supplying an argument to the install scripts the "runAs"-branch is executed within, which will then ask the user for the local machine Administrator's password and execute the installation script under the credentials of that user. If anyone knows/thinks of an alternate, maybe better solution, please explain. ---rony On 17.02.2010 16:38, Mark Miesfeld wrote: > Rony, > > My short answer is I don't know of anything that will help you here. > > Longer answer: It's been awhile since I tried very hard on Vista to > set up something to make this easier, but I got to the point where I > just don't think there is any good solution on Vista. I think things > like this are why people don't use Vista. Now, maybe in Windows 7, > but I haven't had a chance to use it much. > > What I did on Vista was create a command prompt icon that was > permanently run as Administrator. (Actually two icons, left and right > screen.) I do all my work from the command prompt(s) But, this is > how I work on every Windows system. For people that don't always work > from a command prompt on Windows, which I'm sure is most people, this > doesn't help them. > > Plus, you still have to supply the password when you open the command > prompt window(s). Since I always open them when I boot up the system > and don't close them, ever, that is not that bad for me. But, there > are other problems (for me.) If I mount a shared drive as miesfeld > through the GUI, then that drive is not seen from the command prompt, > etc., etc.. > > -- > Mark Miesfeld > > On Wed, Feb 17, 2010 at 3:48 AM, Rony G. Flatscher > <[email protected]> wrote: > >> On Vista and Win7 (Rexx) installation scripts sometimes need to change >> the registry which may be prohibited by the operating system, unless one >> executes the installation scripts with administrator rights. >> >> To achieve this, one could use the Windows "runAs" program from the >> commandline supplying as user "Administrator" and the local machine >> name. [This is actually what I have been experimenting with for the >> BSF4ooRexx and OOo installation scripts in the past days.] >> >> Another possibility seems to be the context menu "runAs", which >> unfortunately may or may not be avaible on the user's installation. How >> would one be able to define this context-menu to rex-scripts? Are there >> any reg-files that one can use as a sample (rex-files need to be >> executed by rexx.exe, which usually is already defined by the ooRexx >> installation) ? >> >> Is there another possibility which can make this simple for the Vista >> and W7 users? A manifest kind of file, and if so, how should it look to >> allow scripts to be executed with the Administrator credentials or where >> can one learn about it)? >> >> Any pointers/opinions highly appreciated! >> >> ---rony >> >> ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
