<snip>
> I never said they didn't. But you were arguing that the OP couldn't
> possibly be seeing what he was experiencing, when I know from personal
> experience that it *is* possible.
>
> Regards,
>
> Dave
>
>
I am not arguing over what the OP is seeing.
I am just saying that the problem he is experiencing can only be
resolved by the authors of the program, and is most likely caused by the
program itself asking for admin power, although it could be a
setup-detection issue like you said.
I hadn't thought about the scenario you described, either... that would
cause problems
.
In any case, the issue here is not that the program is failing to run as
a standard user, it is that it is demanding to be ran by only an
administrator.
However, continuing on our side-conversation about application
compatibility with standard users in Vista...
AFAIK, the file/registry security settings really haven't changed all
that much from XP.
Things like you can't write to program files or modify keys in
HKEY_LOCAL_MACHINE - these are the big ones - have always been that way
in XP as a standard user.
That is why I called the apps stubborn, because it has never been
acceptable to do those things in a non-admin app, even though a lot of
developers did them anyway because they didn't know better or could get
away with it
I find it highly unlikely that a program that would run as a standard
user in XP would not in Vista, although I am certainly not saying it is
impossible, and would be interested in learning about specific instances
of this happening.
As far as the rules on automatic setup recognition, you can find a
summary of what is looked for here:
http://technet2.microsoft.com/Window....mspx?mfr=true
I am not aware of any exhaustive list that details exactly what is done.
--
-JB
Microsoft MVP - Windows Shell/User
Windows Vista Support FAQ -
http://www.jimmah.com/vista/