Please refrain from top-posting. I find it very confusing.
>I want to advise the user to log in as administrator so that my updater
>works.
Well put. That clarifies much.
> I cannot get the updater (a downloaded install.exe file) to install to
>the Program Files install folder from a standard Vista account.
[quoted text clipped - 3 lines]
>but it pops up a dialog saying it cannot write for each file to be
>updated.(Maybe its because it doesnt want to overwrite these files.dunno.)
When you say 'it' do you mean the OS or the installer
software? What installer are you using? I am only (a
little) familiar with NSIS.
Doesn't the *installer* offer some way to check if the
operations will be allowed, and if not, pop a dialog to
warn the user (to log in as administrator)?
>Putting up an option pane question is possible ok, but not nice.People might
>not even know their account type.
That is true, best find some way to test it programmatically,
and only ever bother the user with 'account types' if it fails.

Signature
Andrew Thompson
http://www.physci.org/
patrick - 09 Jan 2008 09:16 GMT
>> I cannot get the updater (a downloaded install.exe file) to install to
>>the Program Files install folder from a standard Vista account.
[quoted text clipped - 7 lines]
> software? What installer are you using? I am only (a
> little) familiar with NSIS.
Using Install4j. think it is install4j pops up the dialog boxes.