From: WatsonR@IntelligenCIA.com
Dee Earley wrote:
> Raoul Watson wrote:
>> Dee Earley wrote:
>>
>>>>
>>>
>>> That's normal, Only (elevated) admins have write access to HKLM.
>>> This has been the case for at least 10 years now
>>>
>>>> While the external app being called, does write properly to the HKLM.
>>>
>>> Then it is running elevated.
>>> It will have asked for permission to elevate before running.
>>>
>> >
>>
>> HUH???? If it is not an admin user why would I bring up HKLM???
>>
>> Both replies missed my point COMPLETELY.
>>
>> The two applications have the exact same code. Executed 5 seconds
>> apart, by the same user (an ADMIN USER) -- one exe shell out to
>> another exe).
>>
>> The registry read-write routines are identical.
>>
>> The only difference is the main program reroutes to the virtual store
>> and the called EXE does write into HKLM properly.
>>
>> Again, the only thing I can think is that the first EXE is properly
>> registered as an app (i.e. can be removed through cpl) and the second
>> exe just runs off the same directory but unregistered.
>
> No, the difference is the elevated part as I said.
> I suggest you do some research on UAC.
>
> On Vista, this means that apps run by an admin users do NOT get full
> admin access by default.
> They need to explicitly ask for admin access (via the manifest) before
> they get the full admin access required to write to Program Files and
> HKLM without being virtualised.
>
> Their app has it, yours doesn't.
>
What the %@&$ are you talking about?? "their" app?? Both apps are mine,
I wrote the code and --absolutely NOT-- there is no elevation request in
any of the app.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
