Nils �stbjerg <[EMAIL PROTECTED]> writes:
> On Sat, Feb 14, 2004 at 10:32:11, Patrick J. LoPresti wrote:
>
> > So what happens if you set the "Policies" key in the registry, and
> > then the user tries to change the settings with the GUI?
>
> Well that one is easy to answer. The user cant change the
> setting. It is greyed out.
Even if the user is a local administrator?
Which Policies sub-key(s) causes the greying out, exactly?
> The way Im doing the script it could be made backwards compatible
> with the old key, for the ppl that want that, while provinding
> support for the new key as well.
Here is how I think this should work.
1) Add an "--admin" switch which says to modify the Policies key
instead of the CurrentVersion key.
2) If "--admin" is not provided, unset the relevant Policies
subkey(s) to un-grey-out the Control Panel gadget.
3) Die with usage instructions if the user tries to configure one of
the new settings without providing the "--admin" key.
Or maybe we should call it "--policy" instead of "--admin".
> My biggest problem is that I havent really got any experience with
> perl. I'll try to fiddle with it this weekend.
If you want to learn some Perl, go for it! Otherwise, if you will
tell me the exact interaction between the keys (in particular, how I
can do the "un-grey-out" part), I would be glad to update the script.
- Pat
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info
