From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_00C3_01C75655.5AE870A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Downlevel, no.  ISVs can declare the elevation behavior as long =
documented for Windows Vista without any compatibility issues for =
downlevel releases of Windows.  This is for legacy programs only which = do
not have such a declaration not dowlevel programs which support older =
releases of Windows.

   Beyond that, we are discussing that very small subset of setup =
programs that don't require admin permission because they don't actually =
install anything in Program Files, the Windows or system directories, or =
anywhere else administrator restricted.  I don't think you or anyone has =
actually identified any of these.  For these, allows, of course not.  =
Defaults to prompt for, I believe yes.

Rich
  "John Beckett"  wrote in message =
news:d9hqt2hsiv586d2bv00fo203h3mspp34b2{at}4ax.com...
  OK thanks.

  I infer that for some downlevel setup programs, Vista allows only =
"don't
  run" and "run will full privilege" as was originally claimed.

  John

  "Rich"  wrote in message news::
  >    I don't know anything about the decision process but as I =
mentioned before I suspect it is app compat especially because it is for =
rarely executed setup programs only.  If there were an option to run =
without elevation then it is both more complicated because the user who =
likely has no knowledge of what is required now has three choices.  The =
two choices are simple, run or don't run.  Now even if they trust the =
application they must choose between two different forms of run.  Worse, =
running without elevation may appear to succeed but actually fail =
silently.
  >=20
  >    Also, this is legacy only behavior.  Any new setup program should =
declare its behavior, again as I described before.
  >=20
  > Rich
  >=20
  >   "John Beckett"  wrote
in message =
news:dgunt29k3n9e2jo4scit8eq83tl7066rps{at}4ax.com...
  >=20
  >=20
  >   Anyway, the above is all peripheral. I'm still curious about =
whether Vista
  >   really does allow only "don't run" and "run with
full privilege" =
on an exe
  >   that it determines is a setup program (presumably a downlevel =
setup
  >   program).
  >=20
  >   John

------=_NextPart_000_00C3_01C75655.5AE870A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








  
Downlevel, no.  ISVs =
can declare=20
the elevation behavior as long documented for Windows Vista without any=20
compatibility issues for downlevel releases of Windows.  This is =
for legacy=20
programs only which do not have such a declaration not dowlevel programs = which=20
support older releases of Windows.
 
   Beyond
that, we are =
discussing that=20
very small subset of setup programs that don't require admin permission = because=20
they don't actually install anything in Program Files, the Windows or = system=20
directories, or anywhere else administrator restricted.  I don't =
think you=20
or anyone has actually identified any of these.  For these, allows, = of=20
course not.  Defaults to prompt for, I believe yes.
 
Rich

  "John Beckett" <johnXsecondary{at}tpgXcomXau&g=">mailto:johnXsecondary{at}tpgXcomXau">johnXsecondary{at}tpgXcomXau&g=
t;=20
  wrote in message news:d9hqt2hsiv5=
86d2bv00fo203h3mspp34b2{at}4ax.com...OK=20
  thanks.I infer that for some downlevel setup programs, Vista =
allows=20
  only "don'trun" and "run will full
privilege" as was originally=20
  claimed.John"Rich"
<{at}> wrote in message johnXsecondary{at}tpgXcomXau&g=">mailto:johnXsecondary{at}tpgXcomXau">johnXsecondary{at}tpgXcomXau&g=
t;=20
  wrote in message news:dgunt29k3n9=
e2jo4scit8eq83tl7066rps{at}4ax.com...>=20
  > >   Anyway, the
above is all peripheral. I'm =
still=20
  curious about whether Vista>   really
does allow only =
"don't=20
  run" and "run with full privilege" on an
exe>   that =
it=20
  determines is a setup program (presumably a downlevel=20
  setup>   program).>
>  =20
John

------=_NextPart_000_00C3_01C75655.5AE870A0--

--- BBBS/NT v4.01 Flag-5