 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoo povrayorg> wrote:
> It has always been our intention to 'advertise' (Microsoft term) the module
> that installs the per-user files; this is what gets activated on first run.
> However this is still a Windows Setup module, so it would have the same
> issue. I am sure there is a way to tell Windows not to remove these files;
> it's just a way of working out how. I don't really want to have to write
> code to manually copy and install them, as it kind of defeats the purpose
> of having an installer.
>
> (Of course, as soon as I do that, someone is inevitably going to complain
> that POV-Ray doesn't clean up after itself when it's uninstalled ...)
>
(I made modifications to povray.ini and quickres.ini.)
How about this:
let the installer place the ini-files at the program location (like in version
3.6), and copy them to Documents and Settings on first run, without overwriting
existing files.
That way there's no problem if the installer removes the files created at
install.
There may be a problem when a new version adds new items which won't get copied
to the existing files, however.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 3/08/2010 15:36, stevenvh wrote:
> I'm not going to fight over this, but beta 37 let me *choose* where to install
> the program. And I didn't install it in Program files.
You probably ran it elevated the first time (this does provide the choice).
Or something else changed on your system. Our revision control system
confirms that the only change in the setup project between 37 and 38 were
the text strings related to the beta version.
If elevation or system change doesn't explain the issue, then something is
strange is going on.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> On 3/08/2010 15:36, stevenvh wrote:
> > I'm not going to fight over this, but beta 37 let me *choose* where to install
> > the program. And I didn't install it in Program files.
>
> You probably ran it elevated the first time (this does provide the choice).
What's elevation? (Yes, I should know, but I only went to school 'til I was 25!)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
stevenvh wrote:
> What's elevation? (Yes, I should know, but I only went to school 'til I was 25!)
It refers to elevated privileges. You picked "run as administrator" to run
it, or you logged in as the administrator, or some such.
Basically, you gave it permission to write to Program Files before you
started it.
--
Darren New, San Diego CA, USA (PST)
C# - a language whose greatest drawback
is that its best implementation comes
from a company that doesn't hate Microsoft.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> stevenvh wrote:
> > What's elevation? (Yes, I should know, but I only went to school 'til I was 25!)
> It refers to elevated privileges. You picked "run as administrator" to run
> it, or you logged in as the administrator, or some such.
> Basically, you gave it permission to write to Program Files before you
> started it.
I didn't know there was such a feature in Windows XP (which is what the
OP is using, as far as I can see).
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> I didn't know there was such a feature in Windows XP (which is what the
> OP is using, as far as I can see).
There is. Most people don't know about it because by default the accounts
most people use are administrator accounts. So chances are the OP was
already running it elevated. (I think XP makes it harder to get to, also, so
it's less obvious there's a way to run things with someone else's privilege.)
In any case, that's what "elevated" means in Chris's post, even if the
distinction isn't applicable to the problem being experienced. :-)
--
Darren New, San Diego CA, USA (PST)
C# - a language whose greatest drawback
is that its best implementation comes
from a company that doesn't hate Microsoft.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> Warp wrote:
> > I didn't know there was such a feature in Windows XP (which is what the
> > OP is using, as far as I can see).
> There is. Most people don't know about it because by default the accounts
> most people use are administrator accounts. So chances are the OP was
> already running it elevated. (I think XP makes it harder to get to, also, so
> it's less obvious there's a way to run things with someone else's privilege.)
I installed beta 38 on a WinXP system using an account which as admin
privileges, and it did install it in the application data folder, so at
least I can confirm that part.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Darren New<dne### [at] sanrrcom> wrote:
>> stevenvh wrote:
>>> What's elevation? (Yes, I should know, but I only went to school 'til I was 25!)
>
>> It refers to elevated privileges. You picked "run as administrator" to run
>> it, or you logged in as the administrator, or some such.
>
>> Basically, you gave it permission to write to Program Files before you
>> started it.
>
> I didn't know there was such a feature in Windows XP (which is what the
> OP is using, as far as I can see).
>
When running windows XP, you have administrator provilege by default.
But, yes, you can "run as..." with XP: Just right click some executable
and sellect that option.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/31/2010 4:46 AM, stevenvh wrote:
> 2. The uninstaller (for both beta 37 and 38) deletes the settings from the "My
> Documents" folder. Isn't the whole idea of placing them there to retain them
> when a new version is installed?
What do you mean by "settings"? Do you mean stuff like INI files and
sample scenes?
--
http://isometricland.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 8/5/2010 10:27 PM, SharkD wrote:
> What do you mean by "settings"? Do you mean stuff like INI files and
> sample scenes?
For clarification, other types of settings are things you can't (or
normally shouldn't) modify yourself, such as the last INI file used to
create a rendering, or the last directory in which you opened/saved a
file, or the list of 10 most recently edited files...
--
http://isometricland.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
