🚀 go-pugleaf

For the ones who are interested in the problem:
 I've found 2 solutions:
1) Starting the process with CreateProcess instead of CreateProcessAsUser,
with the CREATE_SUSPENDED flag, then I use its handle to give it the
privileges required to access the registry and finally I resume its main
thread!
2) I call CreateProcess from a SYSTEM user (from a service program!) setting
the process desktop to "WinSta0\\Default" but this fails if onother user
logged on in the same machine before!!

Note that both solutions requires a service to run the "external exe" as a
normal program running in the same non administrator account of the
"external exe" has not the privileges to change the "external exe" process
privileges.
It sounds like a great bug...please follow me: I am the administrator, and a
programmer ( even if not so great :( ), there are other accounts on my
machine who are not administrators... I have an external application
(written by somebody, but I only have the exe), and its developer wrote it
without considering WinXP rights stuff, so that application fails to load in
the non administrative accounts, but I want my other accounts to be able to
run it, so I would like to write down a simple application that log on with
my administrative account given my user and password, and run the external
application with my privileges ... well it sounds that it's not possible ...
I must write a service to accomplish this trivial work!!!! Is not a big
limitation????

See You all!!
Stefano B.

"Stefano Bonifazi" <stefboombastic@libero.it> ha scritto nel messaggio
news:40a5055b@newsgroups.borland.com...
> Hello Everybody!:-)
>  I have an external application (that is a exe without its code) that
fails
> to execute under a WinXP OS with accounts that do not have administrative
> rights. Its problem is that it tries to access the HKEY_LOCAL_MACHINE key
> with write rights (that it does not own!!)
> I thought to write a my application that launches it with
> CreateProcessAsUser cause I know both User and password of an
> Administrator...
> First I use the LogonUser API to get the Administrator token handle:
>